MIRASTACK Redfish MCP Server
OfficialThis MCP server provides a governed, read-only-by-default Redfish interface to DMTF-compliant BMCs (iDRAC, iLO, XCC, OpenBMC) for monitoring, diagnostics, and optional explicitly confirmed control.
Key capabilities:
Endpoint & service discovery:
list_endpoints,service_info,redfish_walk,redfish_describe_schema,redfish_list_available_actionsSystem, chassis & manager inspection: list/get computer systems, chassis, and managers;
get_health_summaryfor fleet-wide health rollupsTelemetry & inventory:
get_thermal,get_power,get_sensors;get_component_inventoryfor processors, memory, storage, network interfaces, and PCIe devices;get_firmware_inventory;get_log_entriesConfiguration reads:
get_boot_config,get_bios_attributes,list_accounts,list_virtual_media; task inspection vialist_tasksandget_taskRaw/escape-hatch access:
redfish_getwith$select,$expand,$only,$excerpt;redfish_walkfor topology exploration; schema metadata and available-action lookupsSafe write controls: mutating tools are registered only when
MIRASTACK_REDFISH_WRITE_MODEis explicitly elevated (power,config, orfull). Every mutation is dry-run by default and requiresconfirm=trueto apply. Per-endpointread_only=truepermanently blocks writes on that endpoint.
Operational features include single or multi-endpoint configuration via environment variables or JSON/YAML files, stdio and streamable-http transports, pip or Docker deployment, session authentication, ETag/If-Match handling, 202 task polling, registry-backed error rendering, and a discovery mode that can start without endpoint credentials for read-only tool discovery and metadata indexing.
Click on "Deploy 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 Server Check 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": "..."
}
}Discovery mode
The server also starts with zero endpoint credentials and still serves read-only
tool discovery (for MCP scanner validation and metadata indexing). In this mode,
schema/corpus-backed tools continue to work, while BMC-connected tools return a
configuration error that names the required environment variables:
MIRASTACK_REDFISH_HOST, MIRASTACK_REDFISH_USERNAME, and
MIRASTACK_REDFISH_PASSWORD (or MIRASTACK_REDFISH_PASSWORD_FILE), or
MIRASTACK_REDFISH_ENDPOINTS for multi-endpoint setup.
Discovery mode also covers a missing endpoints file. If MIRASTACK_REDFISH_ENDPOINTS
points at a path that does not exist - which is how container platforms and MCP directory
scanners inject a placeholder - the server logs a warning naming that path on stderr and
starts with zero endpoints. A file that does exist but cannot be read or parsed remains a
hard startup failure, and a partially configured single endpoint (for example
MIRASTACK_REDFISH_HOST without MIRASTACK_REDFISH_PASSWORD) still raises, so a typo can
never silently downgrade a configured deployment.
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.
Container and directory deployments
The published image puts the console script on PATH, so docker run ... mirastack-redfish-mcp --transport stdio works unchanged.
Some MCP directories ignore the repository Dockerfile and generate their own image from source. If that generated build installs with uv sync, the project lands in a virtualenv at /app/.venv and the console script is not on PATH, so a launcher that spawns the bare name fails with ENOENT. Point the launcher at the absolute path instead:
{
"buildSteps": ["uv sync"],
"cmdArguments": ["/app/.venv/bin/mirastack-redfish-mcp", "--transport", "stdio"]
}A placeholder MIRASTACK_REDFISH_ENDPOINTS path that the platform never creates is safe - the server starts in discovery mode and serves the read-only tool surface.
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.
Available Tools
25 toolsget_bios_attributesGet BIOS attributesARead-onlyIdempotent
Fetch BIOS attributes and the full BIOS resource for one system. Returns: Object with BIOS attributes, bios_uri, and full BIOS resource payload. Example: get_bios_attributes(system_uri='/redfish/v1/Systems/1')
Inputs: endpoint, system_uri. Returns: object
get_boot_configGet boot override configurationARead-onlyIdempotent
Return the Boot section for a system so callers can inspect current override target, mode, and enablement. Returns: Object with system_uri and current boot override configuration block. Example: get_boot_config(system_uri='/redfish/v1/Systems/1')
Inputs: endpoint, system_uri. Returns: object
get_chassisGet one chassis resourceARead-onlyIdempotent
Fetch a single Chassis resource by URI or ID; if omitted, the first chassis member is auto-selected. Returns: Object with resolved uri and full resource payload for one Chassis. Example: get_chassis(uri='/redfish/v1/Chassis/1')
Inputs: uri, endpoint, chassis_id. Returns: object
get_component_inventoryGet system component inventoryARead-onlyIdempotent
Walk the Processors, Memory, Storage, EthernetInterfaces, and PCIeDevices collections of one system. With include_details true each member is fetched, returning model, manufacturer, serial number, part number, capacity, core count, and MAC address where the vendor reports them. Returns: Object with components keyed by collection name, each carrying uri, count, members (descriptor fields when include_details is true, otherwise URI stubs), and details_truncated. Example: get_component_inventory(system_uri='/redfish/v1/Systems/1', include_details=true)
Inputs: endpoint, system_uri, include_details. Returns: object
get_firmware_inventoryGet firmware inventoryARead-onlyIdempotent
Retrieve UpdateService firmware inventory members and return each firmware resource payload. Returns: Object with firmware_inventory_uri and firmware resources under items. Lists are wrapped as {items, total, truncated}. Example: get_firmware_inventory(limit=200)
Inputs: limit, endpoint. Returns: object
get_health_summarySummarize system healthARead-onlyIdempotent
Collect health/state rollups for Systems, Chassis, and Managers to provide a quick fleet health summary. Returns: Object with groups keyed by Systems/Chassis/Managers, each a list of per-member health and state rollups. Example: get_health_summary()
Inputs: endpoint. Returns: object
get_log_entriesGet log service entriesARead-onlyIdempotent
Collect entries from a selected LogService with optional severity and timestamp filtering for troubleshooting workflows. Returns: Object with filtered entries and the endpoint plus chosen manager/log-service context. Lists are wrapped as {items, total, truncated}. Example: get_log_entries(log_service_uri='/redfish/v1/Managers/1/LogServices/SEL', severity='Critical', limit=50)
Inputs: limit, since, endpoint, severity, +2 more. Returns: object
get_managerGet one manager resourceARead-onlyIdempotent
Fetch one Manager (BMC/iDRAC/iLO/XCC) by URI or ID; if omitted, the first manager member is auto-selected. Returns: Object with resolved uri and full resource payload for one Manager controller. Example: get_manager(uri='/redfish/v1/Managers/1')
Inputs: uri, endpoint, manager_id. Returns: object
get_powerGet chassis power dataARead-onlyIdempotent
Fetch PowerSubsystem/Power for watts, PSU, power-control, and power-cap telemetry. Prefer this tool for PSU or power-draw requests. Returns: Object with power_uri plus full power resource payload. Example: get_power(chassis_uri='/redfish/v1/Chassis/1')
Inputs: endpoint, chassis_uri. Returns: object
get_sensorsGet sensor readingsARead-onlyIdempotent
Fetch broad cross-domain sensor data from Sensors collection; if absent, fall back to deprecated Thermal inline arrays. Use get_thermal for cooling details and get_power for PSU/power metrics. Returns: Object with sensors_uri and sensors, or fallback plus inline temperatures/fans arrays on services without a Sensors collection. Lists are wrapped as {items, total, truncated}. Example: get_sensors(chassis_uri='/redfish/v1/Chassis/1', limit=100)
Inputs: limit, endpoint, chassis_uri. Returns: object
get_systemGet one computer systemARead-onlyIdempotent
Fetch a single ComputerSystem resource by URI or ID; if omitted, the first system member is auto-selected. Returns: Object with resolved uri and full resource payload for one ComputerSystem. Example: get_system(uri='/redfish/v1/Systems/1')
Inputs: uri, endpoint, system_id. Returns: object
get_taskGet one task resourceARead-onlyIdempotent
Fetch a task by URI or task_id; if omitted, the first task member is returned. Returns: Object with a single task payload under task and the resolved task URI. Example: get_task(task_id='Task42')
Inputs: uri, task_id, endpoint. Returns: object
get_thermalGet chassis thermal dataARead-onlyIdempotent
Fetch ThermalSubsystem/Thermal for temperature, fan, and cooling telemetry. Prefer this tool for inlet/exhaust temperature and fan speed requests. Returns: Object with thermal_uri plus full thermal resource payload. Example: get_thermal(chassis_uri='/redfish/v1/Chassis/1')
Inputs: endpoint, chassis_uri. Returns: object
list_accountsList account resourcesARead-onlyIdempotent
List AccountService account members and optionally include full account payloads. Returns: Object with AccountService entries under accounts (URIs only or full account resources). Lists are wrapped as {items, total, truncated}. Example: list_accounts(include_details=false)
Inputs: endpoint, include_details. Returns: object
list_chassisList chassis resourcesARead-onlyIdempotent
List Chassis members and optionally include full details and status for each chassis. Returns: Object containing collection_uri and chassis items with URIs and optional details. Lists are wrapped as {items, total, truncated}. Example: list_chassis(include_details=false)
Inputs: endpoint, include_details. Returns: object
list_endpointsList configured Redfish endpointsARead-onlyIdempotent
List all configured endpoints and their auth/read-only settings so callers can choose a valid endpoint value. Returns: Object containing an endpoints list with endpoint names, URLs, and default/read-only flags. Example: list_endpoints()
Inputs: no named parameters. Returns: object
list_managersList manager resourcesARead-onlyIdempotent
List Manager members (BMC controllers such as iDRAC/iLO/XCC) and optionally include full payloads and status fields. Returns: Object containing collection_uri and managers items with URIs and optional details. Lists are wrapped as {items, total, truncated}. Example: list_managers(include_details=true)
Inputs: endpoint, include_details. Returns: object
list_systemsList computer systemsARead-onlyIdempotent
List ComputerSystem members from /Systems; enable include_details for full resource payloads and health snapshots. Returns: Object containing collection_uri and systems items with URIs and optional details. Lists are wrapped as {items, total, truncated}. Example: list_systems(endpoint='default', include_details=true)
Inputs: endpoint, include_details. Returns: object
list_tasksList Redfish tasksARead-onlyIdempotent
List TaskService task members and optionally include full task resource payloads. Returns: Object with TaskService entries under tasks (URIs only or full task resources). Lists are wrapped as {items, total, truncated}. Example: list_tasks(include_details=true)
Inputs: endpoint, include_details. Returns: object
list_virtual_mediaList virtual media devicesARead-onlyIdempotent
List VirtualMedia resources for a manager to inspect mounted images and media state. Returns: Object with manager_uri and VirtualMedia resources under virtual_media. Lists are wrapped as {items, total, truncated}. Example: list_virtual_media(manager_uri='/redfish/v1/Managers/1')
Inputs: endpoint, manager_uri. Returns: object
redfish_describe_schemaDescribe Redfish schema typeARead-onlyIdempotent
Return distilled schema metadata for one Redfish resource type from the bundled index artifact. Full summaries are large, so pass property_name or action_name to retrieve just one definition. Returns: Full summary with URIs, properties, actions, versions, and enum metadata; or one narrowed property/action definition. Example: redfish_describe_schema(resource_type='ComputerSystem', property_name='PowerState')
Inputs: resource_type (required), action_name, property_name. Returns: object
redfish_getRaw Redfish GETARead-onlyIdempotent
Escape hatch: use when no typed tool fits. Fetch any Redfish URI directly and apply query options only when the endpoint advertises support. Returns: Object with requested resource, resolved request URI, and query options that were actually applied. Example: redfish_get(uri='/redfish/v1/Systems/1', select='Id,PowerState')
Inputs: uri (required), only, expand, select, +2 more. Returns: object
redfish_list_available_actionsList available actions for resourceARead-onlyIdempotent
Prefer this before any unfamiliar write/action call. Combine schema actions with live action metadata (ActionInfo and AllowableValues) for a resource URI. Returns: Object with schema_actions plus live_actions (target URIs, required params, allowable values). Example: redfish_list_available_actions(uri='/redfish/v1/Systems/1')
Inputs: uri (required), endpoint. Returns: object
redfish_walkWalk Redfish graphARead-onlyIdempotent
Escape hatch: use for topology exploration when typed list/get tools are insufficient. Perform a breadth-first walk over linked @odata.id resources. Returns: Object with nodes (each uri, depth, and type from @odata.type) and visited_count. Example: redfish_walk(start_uri='/redfish/v1', max_depth=2, max_nodes=120)
Inputs: endpoint, max_depth, max_nodes, start_uri. Returns: object
service_infoGet Redfish ServiceRoot capabilitiesARead-onlyIdempotent
Fetch ServiceRoot and protocol feature flags to understand what query options and links the endpoint supports. Returns: Object with service_root, redfish_version, capabilities, links, and resolved endpoint name. Example: service_info(endpoint='default')
Inputs: endpoint. Returns: object
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
TDQS
Scored across 25 tools
Most tools map cleanly to distinct Redfish resources (systems, chassis, managers, thermal, power, sensors, tasks, accounts, virtual media). The escape-hatch tools (redfish_get, redfish_walk, redfish_describe_schema, redfish_list_available_actions) are clearly labeled as fallbacks, and get_thermal/get_power/get_sensors are disambiguated by explicit 'use this for...' guidance. Minor overlap between list_* and get_* pairs is conventional and not confusing.
Tool names follow a consistent verb_noun pattern: list_* for collection resources, get_* for individual resources or derived summaries, and redfish_* for generic/escape-hatch operations. This is a predictable and coherent naming scheme across all 25 tools.
25 tools is at the upper edge of the ideal range, but each covers a distinct Redfish subsystem or capability, so the count feels justified for a comprehensive Redfish server. A few tools could be consolidated (e.g., get_boot_config into get_system), but the granularity offers useful pre-built queries.
The read-side Redfish surface is well covered: systems, chassis, managers, health, thermal, power, sensors, inventory, firmware, logs, boot, BIOS, tasks, accounts, and virtual media are all represented. Missing write/action operations (e.g., system reset, boot override, account creation) are acknowledgeable gaps, but the escape-hatch redfish_list_available_actions hints at a design choice to keep the server read-only or rely on generic action calls.
Maintenance
Related MCP Connectors
MCP server for mandates, delegation, policy-gated execution, credential grants, and audit.
Read-only MCP access to a documented IT fleet: state, changes, posture. 15 tools.
Hosted remote MCP for protected account access, permissions, activity history and supported undo.
Governed MCP gateway: one endpoint for your tools, with credential custody and audit log.
Related MCP Servers
- AlicenseNot gradedqualityDmaintenanceEnables 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-
- AlicenseAqualityBmaintenanceEnables AI agents to manage infrastructure through natural language queries to Redfish API endpoints, supporting listing endpoints and retrieving resource data.320BSD 3-Clause
- FlicenseAqualityCmaintenanceEnables 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.174-