MIRASTACK Redfish MCP Server — Claude Code MCP server
MIRASTACK Redfish MCP Server connects AI tools to server BMCs via DMTF Redfish. Operates read-only by default and requires explicit confirmation for power or config changes.
Apache-2.0 ★ 1 updated 2026-08-12
claude mcp add --env MIRASTACK_REDFISH_ENDPOINTS=<MIRASTACK_REDFISH_ENDPOINTS> --env MIRASTACK_REDFISH_DEFAULT_ENDPOINT=<MIRASTACK_REDFISH_DEFAULT_ENDPOINT> --env MIRASTACK_REDFISH_HOST=<MIRASTACK_REDFISH_HOST> --env MIRASTACK_REDFISH_USERNAME=<MIRASTACK_REDFISH_USERNAME> --env MIRASTACK_REDFISH_PASSWORD=<MIRASTACK_REDFISH_PASSWORD> --transport stdio mirastack-redfish-mcp-server -- uvx mirastack-redfish-mcpWhat MIRASTACK Redfish MCP Server does
This MCP server links development agents to out-of-band server managers like iDRAC, iLO, XCC, and OpenBMC. It runs over stdio or streamable-http using the Python MCP SDK and pins schema definitions to DMTF Redfish release 2026.1. Through protocol handling for ETag validation, session auth, and 202 task polling, assistants inspect hardware status cleanly.
Strict guardrails prevent unintended operations against physical nodes. With MIRASTACK_REDFISH_WRITE_MODE=off active by default, mutating endpoints never get registered with the model. Raising the write mode to power, config, or full enables deeper control, but each mutation executes as a dry run until the client passes confirm=true.
Connection settings load from MIRASTACK_REDFISH_* variables or a structured JSON map passed in MIRASTACK_REDFISH_ENDPOINTS. When credentials are not supplied, the server falls back to discovery mode, advertising its schema for scanners without exposing BMC endpoints.
What it helps with
- inspect server hardware telemetry through DMTF Redfish interfaces
- block unintended host reboots using dry-run confirmations
- isolate power and BIOS management permissions across test environments
- manage multiple BMC endpoints through unified JSON configurations
Example prompts for the agent
- Check Redfish service root information on the default host
- Run a dry-run test of
reset_manageron endpointilo-lab - Inspect BIOS properties without applying changes
How to install MIRASTACK Redfish MCP Server
Platform CLI
claude mcp add --env MIRASTACK_REDFISH_ENDPOINTS=<MIRASTACK_REDFISH_ENDPOINTS> --env MIRASTACK_REDFISH_DEFAULT_ENDPOINT=<MIRASTACK_REDFISH_DEFAULT_ENDPOINT> --env MIRASTACK_REDFISH_HOST=<MIRASTACK_REDFISH_HOST> --env MIRASTACK_REDFISH_USERNAME=<MIRASTACK_REDFISH_USERNAME> --env MIRASTACK_REDFISH_PASSWORD=<MIRASTACK_REDFISH_PASSWORD> --transport stdio mirastack-redfish-mcp-server -- uvx mirastack-redfish-mcpReplace <…> with your own values. 8 more environment variables are in the server README. uvx runs the command named after the package; if the README names another one, use uvx --from mirastack-redfish-mcp <command>
Platform CLI
codex mcp add mirastack-redfish-mcp-server --env MIRASTACK_REDFISH_ENDPOINTS=<MIRASTACK_REDFISH_ENDPOINTS> --env MIRASTACK_REDFISH_DEFAULT_ENDPOINT=<MIRASTACK_REDFISH_DEFAULT_ENDPOINT> --env MIRASTACK_REDFISH_HOST=<MIRASTACK_REDFISH_HOST> --env MIRASTACK_REDFISH_USERNAME=<MIRASTACK_REDFISH_USERNAME> --env MIRASTACK_REDFISH_PASSWORD=<MIRASTACK_REDFISH_PASSWORD> -- uvx mirastack-redfish-mcpReplace <…> with your own values. 8 more environment variables are in the server README. uvx runs the command named after the package; if the README names another one, use uvx --from mirastack-redfish-mcp <command>
Config file
{
"mcpServers": {
"mirastack-redfish-mcp-server": {
"command": "uvx",
"args": [
"mirastack-redfish-mcp"
],
"env": {
"MIRASTACK_REDFISH_ENDPOINTS": "<MIRASTACK_REDFISH_ENDPOINTS>",
"MIRASTACK_REDFISH_DEFAULT_ENDPOINT": "<MIRASTACK_REDFISH_DEFAULT_ENDPOINT>",
"MIRASTACK_REDFISH_HOST": "<MIRASTACK_REDFISH_HOST>",
"MIRASTACK_REDFISH_USERNAME": "<MIRASTACK_REDFISH_USERNAME>",
"MIRASTACK_REDFISH_PASSWORD": "<MIRASTACK_REDFISH_PASSWORD>"
}
}
}
}Replace <…> with your own values. 8 more environment variables are in the server README. uvx runs the command named after the package; if the README names another one, use uvx --from mirastack-redfish-mcp <command>
Config file
{
"servers": {
"mirastack-redfish-mcp-server": {
"type": "stdio",
"command": "uvx",
"args": [
"mirastack-redfish-mcp"
],
"env": {
"MIRASTACK_REDFISH_ENDPOINTS": "<MIRASTACK_REDFISH_ENDPOINTS>",
"MIRASTACK_REDFISH_DEFAULT_ENDPOINT": "<MIRASTACK_REDFISH_DEFAULT_ENDPOINT>",
"MIRASTACK_REDFISH_HOST": "<MIRASTACK_REDFISH_HOST>",
"MIRASTACK_REDFISH_USERNAME": "<MIRASTACK_REDFISH_USERNAME>",
"MIRASTACK_REDFISH_PASSWORD": "<MIRASTACK_REDFISH_PASSWORD>"
}
}
}
}Replace <…> with your own values. 8 more environment variables are in the server README. uvx runs the command named after the package; if the README names another one, use uvx --from mirastack-redfish-mcp <command>
Platform CLI
gemini mcp add -e MIRASTACK_REDFISH_ENDPOINTS=<MIRASTACK_REDFISH_ENDPOINTS> -e MIRASTACK_REDFISH_DEFAULT_ENDPOINT=<MIRASTACK_REDFISH_DEFAULT_ENDPOINT> -e MIRASTACK_REDFISH_HOST=<MIRASTACK_REDFISH_HOST> -e MIRASTACK_REDFISH_USERNAME=<MIRASTACK_REDFISH_USERNAME> -e MIRASTACK_REDFISH_PASSWORD=<MIRASTACK_REDFISH_PASSWORD> mirastack-redfish-mcp-server uvx mirastack-redfish-mcpReplace <…> with your own values. 8 more environment variables are in the server README. uvx runs the command named after the package; if the README names another one, use uvx --from mirastack-redfish-mcp <command>
Step by step, with commands for each platform: How to add an MCP server to Claude Code, Codex, Cursor, VS Code, Gemini CLI and more
Questions about MIRASTACK Redfish MCP Server
How to install MIRASTACK Redfish MCP Server in Claude Code?
Run `claude mcp add --env MIRASTACK_REDFISH_ENDPOINTS=<MIRASTACK_REDFISH_ENDPOINTS> --env MIRASTACK_REDFISH_DEFAULT_ENDPOINT=<MIRASTACK_REDFISH_DEFAULT_ENDPOINT> --env MIRASTACK_REDFISH_HOST=<MIRASTACK_REDFISH_HOST> --env MIRASTACK_REDFISH_USERNAME=<MIRASTACK_REDFISH_USERNAME> --env MIRASTACK_REDFISH_PASSWORD=<MIRASTACK_REDFISH_PASSWORD> --transport stdio mirastack-redfish-mcp-server -- uvx mirastack-redfish-mcp`. Replace placeholders with your BMC settings.
What does MIRASTACK Redfish MCP Server do?
It exposes Redfish management endpoints to your agent for reading hardware status, monitoring tasks, and executing controlled power or BIOS operations.
How are write operations kept safe?
Mutating tools stay unregistered while MIRASTACK_REDFISH_WRITE_MODE remains off. Once elevated, every modifying call behaves as a dry run unless confirm=true is supplied.