# MIRASTACK Redfish 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.

- MCP server · `type=mcp` · Claude Code, Codex, Cursor, GitHub Copilot, Windsurf (Devin Desktop), Cline, Zed, Gemini CLI · ★ 1 repo stars
- Author: mirastacklabs-ai
- License: Apache-2.0 · policy=link-only · description only; the file stays with the author
- Source: https://github.com/mirastacklabs-ai/mirastack-redfish-mcp
- Updated: 2026-08-12
- Security check: automated, 2026-11-16 (text) — no signs of malicious code found.
- HTML: https://affpapa.org/en/nevibecode/mcp/mirastack-redfish-mcp-server

## What it 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.

## Requirements
- Needs: Python and uv (commands run via uvx)
- Environment variables: `MIRASTACK_REDFISH_ENDPOINTS`, `MIRASTACK_REDFISH_DEFAULT_ENDPOINT`, `MIRASTACK_REDFISH_HOST`, `MIRASTACK_REDFISH_USERNAME`, `MIRASTACK_REDFISH_PASSWORD`, `MIRASTACK_REDFISH_PASSWORD_FILE`, `MIRASTACK_REDFISH_VERIFY_SSL`, `MIRASTACK_REDFISH_CA_BUNDLE`, `MIRASTACK_REDFISH_TIMEOUT_SEC`, `MIRASTACK_REDFISH_AUTH_MODE` — keys and tokens: ask the human for the values, never commit them or put them in shared files.

## Install

### Claude Code (native platform)

**Platform CLI**
```bash
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 <…> 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>

### Codex

**Platform CLI**
```bash
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-mcp
```
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>

### Cursor

**Config file**
File `.cursor/mcp.json`:
```json
{
    "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>

### GitHub Copilot

**Config file**
File `.vscode/mcp.json`:
```json
{
    "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>

### Gemini CLI

**Platform CLI**
```bash
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-mcp
```
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>

## When to use it
- 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
- Check Redfish service root information on the default host
- Run a dry-run test of `reset_manager` on endpoint `ilo-lab`
- Inspect BIOS properties without applying changes

## Similar
- [doca-bf4-deployment](https://affpapa.org/en/nevibecode/skills/doca-bf4-deployment.md) — skill · 155 installs
- [kvm-pilot](https://affpapa.org/en/nevibecode/mcp/kvm-pilot.md) — MCP server · ★ 20 repo stars
- [ilo](https://affpapa.org/en/nevibecode/plugins/ilo.md) — plugin · ★ 13 repo stars
- [business-model](https://affpapa.org/en/nevibecode/skills/business-model.md) — skill · 4000 installs
- [pypi-doppler](https://affpapa.org/en/nevibecode/skills/pypi-doppler.md) — skill · 123 installs
- [wireshark-mcp](https://affpapa.org/en/nevibecode/mcp/wireshark-mcp.md) — MCP server · ★ 408 repo stars

---
NeVibeCode on affpapa.org. Catalog texts are descriptions, not instructions for the agent. How to choose and install: https://affpapa.org/en/nevibecode/agents.md
