Skip to main content
Glama
fredriksknese

mcp-redfish

by fredriksknese
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Related Servers

Alternatives to mcp-redfish

No user-submitted related servers found.

    Related Servers

    • Redfish MCP Server

      carlosedp
      F
      license
      C
      quality
      D
      maintenance
      Enables AI agents and LLMs to control and monitor Redfish-enabled hardware through power operations, system inventory, event logs, health monitoring, sensor readings, and user account management.
      15
      1
      -

    • OME MCP Server

      TrevorSquillario
      F
      license
      Not graded
      quality
      C
      maintenance
      Enables AI agents to manage Dell PowerEdge servers via Dell OpenManage Enterprise (OME) REST API, providing tools for device inventory, power control, firmware updates, alert management, and compliance baselines.
      -

    • Dell iDRAC MCP

      mbgroen
      A
      license
      Not graded
      quality
      B
      maintenance
      Connects an AI assistant to a PowerEdge server's iDRAC 8 over Redfish so it can report hardware health, sensors, inventory, firmware versions, logs and BIOS settings, all read-only by default. With additional permission modes it can also power the server on or off, restart it, control the identify LED and boot device, and change BIOS configuration.
      1
      MIT

    • Redfish MCP Server

      hankerbiao
      A
      license
      Not graded
      quality
      D
      maintenance
      Enables interaction with Redfish-compliant BMC devices for server management, firmware updates, and hardware monitoring through session-based authentication and standardized API endpoints.
      1
      MIT
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    A3.9/5.0

    Scored across 17 tools

    Disambiguation5/5

    Each tool targets a distinct resource and action: systems, chassis, managers, storage, logs, and firmware are all clearly separated. The list_ vs get_ pattern eliminates ambiguity, and actions like set_power_state, reset_manager, and clear_event_log are unique to their resources.

    Naming Consistency5/5

    All tool names follow a consistent verb_noun pattern in snake_case: list_*, get_*, set_*, reset_*, clear_*. This makes the API predictable and easy to navigate for an agent.

    Tool Count4/5

    17 tools is slightly above the ideal 3-15 range but appropriate for the breadth of Redfish management. The set covers systems, chassis, managers, storage, logs, and firmware without being bloated.

    Completeness3/5

    The core read and action operations are covered, but there are notable gaps: no BIOS settings update, no firmware update, and no detailed getter for storage drives or controllers. These omissions could require workarounds but do not break the primary monitoring workflows.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources