Skip to main content
Glama
Sign In
Dell iDRAC MCP

Dell iDRAC MCP

by mbgroen
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Related Servers

Alternatives to Dell iDRAC 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 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

    • 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.
      -
    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.8/5.0

    Scored across 18 tools

    Disambiguation4/5

    Most tools target clearly distinct iDRAC resources or subsystems, and the generic idrac_get is explicitly positioned as a fallback for uncovered data. There is some potential confusion among idrac_status, idrac_system_overview, and idrac_manager_info, plus mild overlap between health, thermal, and power reporting, but their descriptions provide enough separation.

    Naming Consistency4/5

    All names use the consistent idrac_ prefix and snake_case, making the set predictable and readable. The only minor inconsistency is that most tools are resource nouns while a few use action-first forms such as idrac_get, idrac_list_jobs, and idrac_export_config.

    Tool Count4/5

    Eighteen tools is on the heavier side for the 3-15 typical range, but the iDRAC domain is broad and each tool covers a meaningful subsystem or operation. The count is reasonable for comprehensive read-only server diagnostics, though a few reporting tools could arguably be consolidated.

    Completeness3/5

    The server covers monitoring comprehensively: system overview, hardware inventory, health, thermal, power, logs, jobs, BIOS reads, boot settings, virtual media state, network interfaces, and config export. However, it lacks lifecycle/control operations such as power actions, BIOS setting writes, virtual media attach, job creation/deletion, firmware updates, and iDRAC/user management, leaving notable gaps if an agent needs to change or operate the server.

    Maintenance

    ActivityMaintained
    ResponsivenessSyncing

    Resources