MIRASTACK Redfish MCP Server
OfficialClick on "Install Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@MIRASTACK Redfish MCP ServerCheck the power state and thermal readings for all servers."
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
MIRASTACK Redfish MCP Server
Governed MCP server for DMTF Redfish-compliant BMCs — iDRAC, iLO, XCC, OpenBMC and compatible implementations. Read-only by default: mutating tools are not registered unless you explicitly raise the write mode, and every mutation is a dry-run until confirmed.
Built by MIRASTACK LABS. Apache-2.0.
Highlights
MCP
stdioandstreamable-httptransports via the official Python MCP SDK.Distilled schema metadata from DMTF Redfish-Publications, pinned to release
2026.1.Protocol-correct Redfish behavior: session auth, ETag/
If-Match,202task polling, and registry-backed error rendering.Safe write controls: tiered registration plus dry-run-first confirmations.
Related MCP server: Redfish MCP Server
Why this exists
A BMC is a pre-OS, out-of-band control plane with authority above normal host-level root access. Giving an autonomous agent BMC access without strong guardrails creates immediate blast-radius risk across power, boot, firmware, and account boundaries. This server forces dangerous actions behind deliberate write-mode elevation, and keeps every mutation dry-run by default so intent can be reviewed before application. The result is a governed operational interface rather than an always-armed remote control. The model can still move fast on diagnostics, but privilege transitions become explicit and auditable.
Installation
pip install mirastack-redfish-mcpTry it in 60 seconds (no hardware)
Run a local DMTF mockup, start the MCP server in read-only mode, and call a read tool:
docker compose -f examples/mockup/docker-compose.yml up -d
export MIRASTACK_REDFISH_HOST="http://127.0.0.1:18000"
export MIRASTACK_REDFISH_USERNAME="<bmc-username>"
export MIRASTACK_REDFISH_PASSWORD="<bmc-password>"
export MIRASTACK_REDFISH_WRITE_MODE="off"
mirastack-redfish-mcp --transport stdioExample tool call:
{"tool":"service_info","arguments":{}}Expected output shape:
{
"endpoint": "default",
"service_root": {
"@odata.id": "/redfish/v1"
},
"capabilities": {
"redfish_version": "..."
}
}Quick Start (hardware, stdio)
export MIRASTACK_REDFISH_HOST="https://192.0.2.10"
export MIRASTACK_REDFISH_USERNAME="<bmc-username>"
export MIRASTACK_REDFISH_PASSWORD="<bmc-password>"
export MIRASTACK_REDFISH_WRITE_MODE="off"
mirastack-redfish-mcp --transport stdioQuick Start (streamable-http)
mirastack-redfish-mcp \
--transport streamable-http \
--host 127.0.0.1 \
--port 8000 \
--path /mcp \
--stateless-http \
--json-responseWarning: binding to
0.0.0.0exposes BMC control to every host that can reach this port. Bind to loopback unless the listener sits behind an authenticating proxy on a trusted management network.
Configuration
Canonical environment variables
Use MIRASTACK_REDFISH_* variables:
MIRASTACK_REDFISH_HOSTMIRASTACK_REDFISH_USERNAMEMIRASTACK_REDFISH_PASSWORDorMIRASTACK_REDFISH_PASSWORD_FILEoptional:
MIRASTACK_REDFISH_VERIFY_SSL(default:true),MIRASTACK_REDFISH_CA_BUNDLE,MIRASTACK_REDFISH_TIMEOUT_SEC,MIRASTACK_REDFISH_AUTH_MODE
Multi-endpoint configuration
Set MIRASTACK_REDFISH_ENDPOINTS to inline JSON or a YAML/JSON file:
{
"idrac-prod": {
"base_url": "https://192.0.2.10",
"username": "<bmc-username>",
"password_file": "/run/secrets/idrac_password",
"verify_ssl": true,
"read_only": true
},
"ilo-lab": {
"base_url": "https://192.0.2.11",
"username": "<bmc-username>",
"password": "<bmc-password>",
"verify_ssl": true
}
}Lab-only override (not recommended for production):
{
"ilo-lab": {
"verify_ssl": false
}
}Set MIRASTACK_REDFISH_DEFAULT_ENDPOINT to choose the default endpoint.
Compatibility
Legacy bare REDFISH_* environment variables are still read as a fallback, with a one-time deprecation warning per variable.
Tool registration profile
MIRASTACK_REDFISH_TOOL_PROFILE=full(default): all toolsets allowed by write mode.MIRASTACK_REDFISH_TOOL_PROFILE=standard: excludes raw write escape hatches.MIRASTACK_REDFISH_TOOL_PROFILE=core: curated 15-tool small-model surface.MIRASTACK_REDFISH_TOOLSETS(comma-separated) overrides profiles with explicit toolsets.
Measured advertised tool-schema payload at MIRASTACK_REDFISH_WRITE_MODE=full: core 20,795 bytes (15 tools), standard 43,669 bytes (33 tools), full 54,745 bytes (40 tools). Re-measure with python3 scripts/check_tool_metadata.py --sizes.
Write Safety Model
MIRASTACK_REDFISH_WRITE_MODE=off(default): mutating tools are not registered.MIRASTACK_REDFISH_WRITE_MODE=power: power/reset/boot control tools are registered.MIRASTACK_REDFISH_WRITE_MODE=config: config-tier tools are registered.MIRASTACK_REDFISH_WRITE_MODE=full: full-tier tools are registered.
Every mutating tool accepts confirm:
confirm=false: dry-run response (dry_run=true,applied=false) withnext_step.confirm=true: action is applied.
Per-endpoint read_only=true overrides global write mode and blocks all writes on that endpoint.
Tier contract
Power tier:
set_power_state,set_boot_override,reset_manager,cancel_taskConfig tier:
set_bios_attributes,eject_virtual_media,redfish_patch,redfish_post,redfish_delete,redfish_invoke_actionFull tier:
insert_virtual_media,clear_logs,manage_account,simple_update,reset_to_defaults
Development
python3 -m venv .venv
source .venv/bin/activate
pip install -e .[dev]
make build-index
make verifyThe schema index is generated from DMTF Redfish-Publications, pinned to one release for reproducibility. See CONTRIBUTING.md for refresh procedure.
Registry Publishing Notes
server.jsonincludes PyPI and OCI package definitions for MCP Registry.This README carries the required marker:
mcp-name: ai.mirastacklabs/mirastack-redfish-mcp.Docker image includes the
io.modelcontextprotocol.server.nameOCI label.Install the official publisher CLI via Homebrew:
brew install mcp-publisher.Do not use
npx mcp-publisherorpip install mcp-publisherfor registry publishing.
Contributing
GitHub is a public read-only mirror. Issues are welcome on GitHub, but pull requests opened on GitHub cannot be merged. See CONTRIBUTING.md for accepted contribution paths.
Security
See SECURITY.md.
License
Apache-2.0.
This server cannot be installed
Maintenance
Resources
Unclaimed servers have limited discoverability.
Looking for Admin?
If you are the server author, to access and configure the admin panel.
Related MCP Servers
- Alicense-qualityDmaintenanceEnables interaction with Redfish-compliant BMC devices for server management, firmware updates, and hardware monitoring through session-based authentication and standardized API endpoints.1MIT
- FlicenseCqualityDmaintenanceEnables 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.151
- Alicense-qualityDmaintenanceEnables interacting with a Redmine instance via REST API, allowing issues, projects, time logging, and generic endpoint calls through an MCP agent.15MIT
- AlicenseBqualityAmaintenanceEnables AI agents to manage infrastructure through natural language queries to Redfish API endpoints, supporting listing endpoints and retrieving resource data.215BSD 3-Clause
Related MCP Connectors
Remote MCP for tool license checks, vendor policy review, alternatives, and license receipts.
Remote MCP for Copilot CLI switch gate MCP, structured receipts, audit logs, and reviewer-ready evid
Remote MCP for A2A caller identity, scope policy, verdict receipts, and audit history.
Latest Blog Posts
- Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)By Om-Shree-0709 on .mcpAgent IdentityOAuth 2.1
- Your AI Chatbot Just Exposed Your CEO's Salary to an InternBy Om-Shree-0709 on .Agent IdentityMCP SecurityOAuth Delegation
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/mirastacklabs-ai/mirastack-redfish-mcp'
If you have feedback or need assistance with the MCP directory API, please join our Discord server