Skip to main content
Glama
mirastacklabs-ai

MIRASTACK Redfish MCP Server

Official
by mirastacklabs-ai
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Related Servers

Alternatives to MIRASTACK Redfish MCP Server

No user-submitted related servers found.

    Related Servers

    • 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

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

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

    • dokku-mcp

      nunombispo
      A
      license
      A
      quality
      C
      maintenance
      Enables MCP clients to inspect and manage a Dokku host over SSH with structured tools, read-only defaults, and explicit guardrails for safe operations.
      10
      MIT

    • branchlift

      MuratKomurcu1
      A
      license
      Not graded
      quality
      A
      maintenance
      Enables local MCP access to attach to isolated backend environments, monitor runtime health/logs, check security posture, manage snapshots and diffs, audit events, and view sanitized remote inventory.
      15 npm
      Apache 2.0
    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

    A4.2/5.0

    Scored across 25 tools

    Disambiguation4/5

    Most tools map cleanly to distinct Redfish resources (systems, chassis, managers, thermal, power, sensors, tasks, accounts, virtual media). The escape-hatch tools (redfish_get, redfish_walk, redfish_describe_schema, redfish_list_available_actions) are clearly labeled as fallbacks, and get_thermal/get_power/get_sensors are disambiguated by explicit 'use this for...' guidance. Minor overlap between list_* and get_* pairs is conventional and not confusing.

    Naming Consistency5/5

    Tool names follow a consistent verb_noun pattern: list_* for collection resources, get_* for individual resources or derived summaries, and redfish_* for generic/escape-hatch operations. This is a predictable and coherent naming scheme across all 25 tools.

    Tool Count4/5

    25 tools is at the upper edge of the ideal range, but each covers a distinct Redfish subsystem or capability, so the count feels justified for a comprehensive Redfish server. A few tools could be consolidated (e.g., get_boot_config into get_system), but the granularity offers useful pre-built queries.

    Completeness4/5

    The read-side Redfish surface is well covered: systems, chassis, managers, health, thermal, power, sensors, inventory, firmware, logs, boot, BIOS, tasks, accounts, and virtual media are all represented. Missing write/action operations (e.g., system reset, boot override, account creation) are acknowledgeable gaps, but the escape-hatch redfish_list_available_actions hints at a design choice to keep the server read-only or rely on generic action calls.

    Maintenance

    ActivitySlowing
    ResponsivenessUnresponsive

    Resources