Skip to main content
Glama
Sign In
proliant-mcp

proliant-mcp

by hjma29
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Related Servers

Alternatives to proliant-mcp

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

      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
      -

    • Redfish Fleet MCP

      MukeshA39
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI assistants to query and monitor a fleet of bare-metal servers through vendor-neutral Redfish BMCs using natural language, covering health, thermal, power, storage, firmware, logs, and error checks, with a confirmation-gated reboot tool.
      MIT

    • Dell iDRAC MCP

      mbgroen
      A
      license
      A
      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.
      18
      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.6/5.0

    Scored across 12 tools

    Disambiguation4/5

    Each tool targets a distinct resource or granularity, but get_server_summary overlaps meaningfully with get_health, get_processors, get_memory, and get_firmware_inventory, since it reports power/health state, CPU count, total memory, and BIOS/iLO versions. get_fleet_summary is clearly framed as a bulk variant of get_server_summary, and redfish_get is explicitly positioned as the escape hatch for uncovered data.

    Naming Consistency4/5

    Eleven of the twelve tools follow a clean verb_noun pattern (list_servers, get_ilo_info, get_firmware_inventory, get_event_log, etc.). The lone deviation is redfish_get, which inverts the order to noun_verb, though it remains readable.

    Tool Count5/5

    Twelve tools is well within the ideal range and each is scoped to a distinct slice of iLO data (firmware, memory, storage, network, health, events). Nothing feels padded or missing in terms of breadth.

    Completeness4/5

    Read-only inventory and health coverage is thorough, including a raw Redfish escape hatch for anything not modeled. However, there are no write/action operations (power control, UID light toggle, log clearing) even though power/UID state is reported, and redfish_get is GET-only so agents have no remediation path.

    Maintenance

    ActivityMaintained
    ResponsivenessNo recent community issues

    Resources