Skip to content
Back to search

idrac-ilo-mcp

Read-only MCP server that lets Claude troubleshoot Dell iDRAC and HPE iLO servers via Redfish

Safety scan

A static text scan, not a guarantee. Select the badge to see what was scanned and every finding.

Checked today
Badge for your README
findsafeskills safety rating

Markdown

[![findsafeskills safety rating](/api/listings/johnwin78-ctrl--idrac-ilo-mcp/badge.svg)](/listings/johnwin78-ctrl--idrac-ilo-mcp)

HTML

<a href="/listings/johnwin78-ctrl--idrac-ilo-mcp"><img src="/api/listings/johnwin78-ctrl--idrac-ilo-mcp/badge.svg" alt="findsafeskills safety rating" /></a>

Install

i

Install instructions from the README

As written by the repo's author. findsafeskills has not verified these steps.

1. Copy this folder to e.g. `C:\Tools\bmc-mcp` (Python 3.10+ must be installed). 2. Double-click **`setup.bat`**. It installs the dependencies, asks for the iDRAC/iLO IP, username and password (typed in its own window, never in chat), tests the connection, and registers `bmc` in Claude desktop's config. It backs the config up first and keeps your other settings. 3. Fully quit Claude desktop (tray icon → Quit) and reopen it.

Rerun `setup.bat` any time to change the server or credentials. The manual steps below do the same thing by hand.

---

What was scanned

The files the safety scan read, as written by the repository's author and shown as plain text. Lines with a finding are marked.

README.md · README · 188 lines
  1. # idrac-ilo-mcp — let Claude troubleshoot Dell iDRAC & HPE iLO servers
  2. A small **read-only** MCP server that runs on your laptop and gives Claude direct access to a server's
  3. iDRAC or iLO through the **Redfish API**. No web console and no browser involved: you say *"check the server"* and
  4. Claude pulls health, logs, sensors, storage and firmware by itself.
  5. It comes in two versions that do exactly the same thing. Pick **one**:
  6. | Folder | Needs | Use if… |
  7. |-----------|------------------------------|------------------------------------------|
  8. | `python/` | Python 3.10+ | you already have Python, or prefer it |
  9. | `node/` | Node.js 18.17+ | you already have Node, or prefer it |
  10. ## What Claude gets
  11. | Tool | What it returns |
  12. |------|-----------------|
  13. | `bmc_health_summary` | **Start here.** Overall rollups (Dell rollup statuses / HPE AggregateHealthStatus) + every component that is not OK |
  14. | `bmc_get_event_logs` | Event logs, newest first. Dell **SEL + Lifecycle Log**, HPE **IML + iLO Event Log**. Filter by log and severity |
  15. | `bmc_list_logs` | Which logs this BMC has |
  16. | `bmc_get_thermal` | Temperatures with thresholds, fans |
  17. | `bmc_get_power` | PSUs (model, FW, input voltage, status), consumption, redundancy, bad voltage rails |
  18. | `bmc_get_storage` | RAID controllers, drives (predictive failure, SSD wear), virtual disks / logical drives |
  19. | `bmc_get_inventory` | CPUs, populated DIMMs (incl. HPE DIMM status), NICs |
  20. | `bmc_get_firmware` | All installed firmware versions |
  21. | `bmc_identify` | Vendor, iDRAC/iLO generation & FW, model, serial / service tag, BIOS, power state |
  22. | `bmc_redfish_get` | Raw read of any `/redfish/...` path, for anything else |
  23. | `bmc_set_target` / `bmc_list_targets` | Switch to another server during a chat |
  24. **Generation-agnostic.** Nothing is hard-coded to a model. Every path is discovered from the Redfish service root, with
  25. fallbacks for older layouts: legacy `Thermal`/`Power` vs newer `ThermalSubsystem`/`PowerSubsystem`, HPE `Hp` (iLO 4)
  26. vs `Hpe` (iLO 5+) OEM data, HPE SmartStorage, and SimpleStorage. It should work with any Redfish-capable BMC:
  27. roughly **iDRAC 7/8 (FW 2.40+), iDRAC 9, iDRAC 10** and **iLO 4 (FW 2.30+), iLO 5, iLO 6, iLO 7**.
  28. Tested against simulated iDRAC 9, iLO 5 and iLO 4 responses. Real hardware always has quirks, so tell Claude if a tool
  29. comes back empty and it can use `bmc_redfish_get` to look around.
  30. **Read-only by design.** The only non-GET requests it ever sends are a log-in and log-out against the Redfish
  31. SessionService. There are no power, reset, BIOS, RAID, firmware or clear-log tools. For extra safety, use a
  32. read-only BMC account anyway:
  33. - **Dell iDRAC:** a user with role **Read Only** (Login privilege only).
  34. - **HPE iLO:** a user with only the **Login** privilege.
  35. ---
  36. ## Quick setup (Windows, Python version)
  37. 1. Copy this folder to e.g. `C:\Tools\bmc-mcp` (Python 3.10+ must be installed).
  38. 2. Double-click **`setup.bat`**. It installs the dependencies, asks for the iDRAC/iLO IP, username and password
  39. (typed in its own window, never in chat), tests the connection, and registers `bmc` in Claude desktop's config.
  40. It backs the config up first and keeps your other settings.
  41. 3. Fully quit Claude desktop (tray icon → Quit) and reopen it.
  42. Rerun `setup.bat` any time to change the server or credentials. The manual steps below do the same thing by hand.
  43. ---
  44. ## Manual setup (Windows; macOS notes at the end)
  45. ### 1. Copy the folder
  46. Unzip to a stable location, e.g. `C:\Tools\bmc-mcp\`.
  47. ### 2. Install the dependencies (one version only)
  48. **Python**
  49. ```powershell
  50. cd C:\Tools\bmc-mcp\python
  51. py -m pip install -r requirements.txt
  52. ```
  53. **Node**
  54. ```powershell
  55. cd C:\Tools\bmc-mcp\node
  56. npm install
  57. ```
  58. ### 3. Test the connection from your laptop (without Claude)
  59. Your laptop must be able to reach the iDRAC/iLO IP (management network or VPN).
  60. ```powershell
  61. $env:BMC_HOST="192.168.10.21"; $env:BMC_USERNAME="claude_ro"; $env:BMC_PASSWORD="your-password"
  62. py C:\Tools\bmc-mcp\python\bmc_mcp.py --check # Python
  63. node C:\Tools\bmc-mcp\node\bmc-mcp.mjs --check # or Node
  64. ```
  65. You should get a JSON health report. If not, see **Troubleshooting** below.
  66. ### 4. Add it to the Claude desktop app
  67. Open **Claude desktop → Settings → Developer → Edit Config**. That opens `claude_desktop_config.json`
  68. (`%APPDATA%\Claude\claude_desktop_config.json`). Add **one** of these blocks inside `"mcpServers"`:
  69. **Python**
  70. ```json
  71. {
  72. "mcpServers": {
  73. "bmc": {
  74. "command": "py",
  75. "args": ["C:\\Tools\\bmc-mcp\\python\\bmc_mcp.py"],
  76. "env": {
  77. "BMC_HOST": "192.168.10.21",
  78. "BMC_USERNAME": "claude_ro",
  79. "BMC_PASSWORD": "your-password"
  80. }
  81. }
  82. }
  83. }
  84. ```
  85. **Node**
  86. ```json
  87. {
  88. "mcpServers": {
  89. "bmc": {
  90. "command": "node",
  91. "args": ["C:\\Tools\\bmc-mcp\\node\\bmc-mcp.mjs"],
  92. "env": {
  93. "BMC_HOST": "192.168.10.21",
  94. "BMC_USERNAME": "claude_ro",
  95. "BMC_PASSWORD": "your-password"
  96. }
  97. }
  98. }
  99. }
  100. ```
  101. If `py` isn't found, use the full path to `python.exe` instead. Fully quit and reopen Claude desktop.
  102. The `bmc_*` tools then appear in any chat linked to this computer.
  103. ### 5. Use it
  104. > "Check the server's health and tell me what's wrong."
  105. > "Show me critical and warning events from the last few days."
  106. > "Is any drive predicted to fail? What's the RAID status?"
  107. To look at a different server, either change `BMC_HOST` in the config and restart Claude desktop, or just tell Claude
  108. *"switch to 192.168.10.35, user claude_ro, password …"* (it calls `bmc_set_target` for that chat only).
  109. ---
  110. ## Settings
  111. | Variable | Default | Meaning |
  112. |----------|---------|---------|
  113. | `BMC_HOST` | — | IP or hostname, optionally with `https://` |
  114. | `BMC_USERNAME` / `BMC_PASSWORD` | — | BMC account (read-only recommended) |
  115. | `BMC_VERIFY_TLS` | `false` | `true` to verify the certificate (most iDRAC/iLO certificates are self-signed) |
  116. | `BMC_TIMEOUT` | `30` | Seconds per request (raise for slow, older iLOs) |
  117. | `BMC_USE_PROXY` | `false` | BMC traffic ignores system/corporate proxies by default. Set `true` only if you must go through one |
  118. | `BMC_TARGETS_FILE` | — | Path to a JSON file of named servers (see below) |
  119. ### Future: several servers / the whole network
  120. Prepared for this already. Instead of `BMC_HOST`, point `BMC_TARGETS_FILE` at a file like `targets.example.json`:
  121. ```json
  122. { "targets": {
  123. "r750-dcs-01": { "host": "192.168.10.21", "username": "claude_ro", "password": "..." },
  124. "dl380-his-02": { "host": "192.168.10.35", "username": "claude_ro", "password": "..." } } }
  125. ```
  126. The first entry is the default. Say *"switch to dl380-his-02"* and Claude calls `bmc_set_target(name=...)`.
  127. A later version can add a fleet-wide scan tool on top of this same file.
  128. **Credentials:** the config/targets file stores the password in plain text on your laptop. Keep it in your user profile,
  129. use a read-only BMC account, and don't put the targets file in a shared folder.
  130. ---
  131. ## Troubleshooting
  132. | Message | Fix |
  133. |---------|-----|
  134. | `Cannot reach … Is this computer on the management network/VPN?` | Ping the IP; connect to the OOB VLAN/VPN; check the firewall allows TCP 443 |
  135. | `Login rejected (401)` | Wrong user/password, or the account is locked or has no remote/Redfish login |
  136. | `Access denied (403)` | Account lacks Login privilege, or a proxy/firewall blocked it (try `BMC_USE_PROXY` if your site forces a proxy) |
  137. | `GET /redfish/v1/ -> HTTP 404` | Firmware too old for Redfish (iDRAC 7/8 < 2.40, iLO 4 < 2.30). Update the BMC firmware |
  138. | Timeouts on iLO 4 | Set `BMC_TIMEOUT` to `60` |
  139. | Storage comes back empty (HPE) | The server must have finished POST since the last iLO reset; some HBAs/NVMe aren't reported |
  140. | Tools don't show up in Claude | Check the JSON is valid, then fully quit and reopen Claude desktop. See *Settings → Developer* for errors |
  141. ## macOS
  142. Same steps. Use `python3` instead of `py`, paths like `/Users/you/Tools/bmc-mcp/python/bmc_mcp.py`, and the config
  143. file at `~/Library/Application Support/Claude/claude_desktop_config.json`.
  144. ## Files
  145. ```
  146. bmc-mcp/
  147. setup.bat / setup.py one-click installer + Claude desktop registration (Python version)
  148. python/bmc_mcp.py Python server (+ requirements.txt)
  149. node/bmc-mcp.mjs Node server (+ package.json)
  150. targets.example.json template for named servers
  151. test/mock_redfish.py simulated iDRAC 9 / iLO 5 / iLO 4 for testing
  152. test/mcp_client_test.py calls every tool: python test/mock_redfish.py dell 8001 then
  153. python test/mcp_client_test.py py python/bmc_mcp.py 8001
  154. ```

Ratings and comments

Sign in to rate this skill.

Sign in

Free to use. If it’s helped, pass it on.