Skip to main content
Glama
carlosedp

Redfish MCP Server

by carlosedp
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Related Servers

Alternatives to Redfish MCP Server

No user-submitted related servers found.

    Related Servers

    • mcp-redfish

      fredriksknese
      F
      license
      A
      quality
      C
      maintenance
      Enables AI assistants to monitor and control server hardware (power, thermal, storage, firmware, event logs) via Redfish BMC API on Dell iDRAC, HPE iLO, Lenovo XCC, Supermicro BMC, and others.
      17
      4
      -

    • 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

    • 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
    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

    C2.9/5.0

    Scored across 15 tools

    Disambiguation4/5

    Most tools target distinct Redfish resources (manager, system, chassis, sensors, firmware, power, logs, security, configuration). Minor overlap exists between health status and sensor readings, and between manager/audit logs, but descriptions clarify the intent.

    Naming Consistency3/5

    Tools share a redfish_ prefix, and most read operations use get_*. However, action tools vary: power_control (noun-verb), manage_users, clear_logs, and configure (bare verb), creating an inconsistent verb-noun pattern.

    Tool Count5/5

    15 tools is a well-scoped set for a Redfish management server, covering inventory, health, power, logs, security, and configuration without feeling excessive.

    Completeness4/5

    The tool set covers the core Redfish lifecycle: inventory retrieval, power control, health/sensor monitoring, logs, user management, and configuration. Some gaps exist (e.g., firmware updates, network/storage inventory, BIOS settings), but these are not critical for basic monitoring and control.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources