MIRASTACK Redfish MCP Server

MIRASTACK Redfish MCP Server is an MCP integration. Governed MCP server for DMTF Redfish BMCs. Read-only by default; writes are opt-in and dry-run.

Packages and local setup

The published pypi package is mirastack-redfish-mcp, version 0.1.1. Its declared MCP transport is stdio.

The package declares MIRASTACK_REDFISH_ENDPOINTS: JSON payload or YAML/JSON path defining one or more Redfish endpoints.; MIRASTACK_REDFISH_DEFAULT_ENDPOINT: Default endpoint name used when no endpoint argument is provided.; MIRASTACK_REDFISH_HOST: Single-endpoint Redfish base URL, for example https://192.0.2.10.; MIRASTACK_REDFISH_USERNAME: Single-endpoint Redfish username.; MIRASTACK_REDFISH_PASSWORD: Single-endpoint Redfish password.; MIRASTACK_REDFISH_PASSWORD_FILE: Path to a file containing the single-endpoint Redfish password.; MIRASTACK_REDFISH_VERIFY_SSL: TLS verification. Defaults to true. Set false only for lab endpoints with controlled certificates.; MIRASTACK_REDFISH_CA_BUNDLE: Path to a custom CA bundle used for TLS verification.; MIRASTACK_REDFISH_TIMEOUT_SEC: HTTP timeout in seconds for Redfish requests.; MIRASTACK_REDFISH_AUTH_MODE: Auth mode: auto, session, or basic.; MIRASTACK_REDFISH_WRITE_MODE: Write tier: off (default), power, config, or full. Mutating tools are not registered unless raised.; MIRASTACK_REDFISH_TOOL_PROFILE: Tool profile: core, standard, or full.; MIRASTACK_REDFISH_TOOLSETS: Optional comma-separated toolset override..

The published oci package is docker.io/mirastack/mirastack-redfish-mcp:0.1.1. Its declared MCP transport is stdio.

Before connecting

Check the maintainer’s instructions for account access, authentication and the supported client configuration. Once connected, inspect the tools your client receives and try a small task that matches the server’s stated purpose. The registry description does not include a verified, complete tool list.

Project and source

View the publisher’s registry entry · Project repository · Project website. This profile uses version 0.1.1 from the registry. Registration identifies the publisher namespace; it does not establish that this is a first-party integration for every service it connects.

Browse related other integrations MCP servers for tools that cover the same kind of work.