Redfish MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| REDFISH_PORT | No | Default port for Redfish API (used when not specified per-host) | 443 |
| MCP_TRANSPORT | No | Transport method: stdio, sse, or streamable-http | stdio |
| REDFISH_HOSTS | Yes | JSON array of Redfish endpoint configurations | [{"address":"127.0.0.1"}] |
| REDFISH_PASSWORD | No | Default password for authentication | |
| REDFISH_USERNAME | No | Default username for authentication | |
| REDFISH_AUTH_METHOD | No | Authentication method: basic or session | session |
| MCP_REDFISH_LOG_LEVEL | No | Logging level: DEBUG, INFO, WARNING, ERROR, CRITICAL | INFO |
| REDFISH_SERVER_CA_CERT | No | Path to CA certificate for server verification | |
| REDFISH_DISCOVERY_ENABLED | No | Enable automatic endpoint discovery | false |
| REDFISH_DISCOVERY_INTERVAL | No | Discovery interval in seconds | 30 |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
| logging | {} |
| prompts | {
"listChanged": true
} |
| resources | {
"subscribe": false,
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_resource_dataA | Given a Redfish resource URL (e.g., 'https:///redfish/v1'), fetches and returns its data as JSON. To construct a valid Redfish resource URL as input, use the following url schema 'https:///redfish/v1/'. |
| list_serversA | List configured Redfish servers that can be managed. |
| list_discovered_serversB | List discovered Redfish server candidates for review. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 3 tools
list_servers and list_discovered_servers are similar (both enumerate servers), but the descriptions clearly distinguish configured vs. discovered candidates. get_resource_data is clearly distinct from both.
All three tools use consistent snake_case with a verb_noun pattern: list_servers, list_discovered_servers, get_resource_data. No mixed conventions.
Three tools is quite thin for a Redfish management server; the surface feels more like basic discovery/read than a full management scope. The count is borderline rather than clearly mismatched.
The server only lists servers and fetches arbitrary resource data. Core Redfish management operations such as power actions, firmware updates, or session management are absent, creating significant gaps for real management workflows.