Redfish MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| REDFISH_HOST | No | The URL of the Redfish endpoint (e.g., https://192.168.1.100) | |
| REDFISH_TIMEOUT | No | Timeout in seconds for Redfish API requests | 30 |
| REDFISH_PASSWORD | No | Password for BMC authentication | |
| REDFISH_USERNAME | No | Username for BMC authentication | |
| REDFISH_VERIFY_SSL | No | Whether to verify SSL certificates (defaults to false for self-signed certificates) | false |
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": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| redfish_get_system_infoB | Get system information and inventory |
| redfish_get_chassis_infoB | Get chassis information and inventory |
| redfish_get_manager_infoB | Get manager information and inventory |
| redfish_power_controlD | Control system power state |
| redfish_get_health_statusA | Get system health and status information for a specific system or all systems |
| redfish_get_sensorsC | Get sensor readings for a specific system |
| redfish_get_firmware_inventoryC | Get firmware inventory information for systems |
| redfish_get_power_consumptionC | Get power consumption and efficiency metrics for systems |
| redfish_manage_usersD | Manage user accounts on the Redfish system |
| redfish_get_manager_logsC | Retrieve manager event logs |
| redfish_clear_logsC | Clear system event logs |
| redfish_get_security_statusB | Get security status and compliance information |
| redfish_get_audit_logsC | Get comprehensive audit logs for security and compliance monitoring |
| redfish_configureC | Configure Redfish connection parameters and test the connection |
| redfish_get_config_statusB | Get current Redfish configuration status |
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 15 tools
Most tools target distinct Redfish resources (manager, system, chassis, sensors, firmware, power, logs, security, configuration). Minor overlap exists between health status and sensor readings, and between manager/audit logs, but descriptions clarify the intent.
Tools share a redfish_ prefix, and most read operations use get_*. However, action tools vary: power_control (noun-verb), manage_users, clear_logs, and configure (bare verb), creating an inconsistent verb-noun pattern.
15 tools is a well-scoped set for a Redfish management server, covering inventory, health, power, logs, security, and configuration without feeling excessive.
The tool set covers the core Redfish lifecycle: inventory retrieval, power control, health/sensor monitoring, logs, user management, and configuration. Some gaps exist (e.g., firmware updates, network/storage inventory, BIOS settings), but these are not critical for basic monitoring and control.