MIRASTACK Redfish MCP Server
OfficialServer Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| MIRASTACK_REDFISH_HOST | No | Base URL of the Redfish service (e.g., http://127.0.0.1:18000 or https://192.0.2.10) | |
| MIRASTACK_REDFISH_PASSWORD | No | BMC password | |
| MIRASTACK_REDFISH_TOOLSETS | No | Comma-separated list of toolsets to override the profile | |
| MIRASTACK_REDFISH_USERNAME | No | BMC username | |
| MIRASTACK_REDFISH_AUTH_MODE | No | Authentication mode (e.g., session, basic) | |
| MIRASTACK_REDFISH_CA_BUNDLE | No | Path to a CA bundle file for TLS verification | |
| MIRASTACK_REDFISH_ENDPOINTS | No | Inline JSON or path to a YAML/JSON file defining multiple endpoints | |
| MIRASTACK_REDFISH_VERIFY_SSL | No | Whether to verify TLS certificates | true |
| MIRASTACK_REDFISH_WRITE_MODE | No | Write mode: off, power, config, or full | off |
| MIRASTACK_REDFISH_TIMEOUT_SEC | No | Timeout in seconds for Redfish requests | |
| MIRASTACK_REDFISH_TOOL_PROFILE | No | Tool registration profile: full, standard, or core | full |
| MIRASTACK_REDFISH_PASSWORD_FILE | No | Path to a file containing the BMC password | |
| MIRASTACK_REDFISH_DEFAULT_ENDPOINT | No | Name of the default endpoint from the endpoints configuration |
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 |
|---|---|
| list_endpointsA | List all configured endpoints and their auth/read-only settings so callers can choose a valid endpoint value. Returns: Object containing an |
| service_infoA | Fetch ServiceRoot and protocol feature flags to understand what query options and links the endpoint supports. Returns: Object with |
| list_systemsA | List ComputerSystem members from /Systems; enable include_details for full resource payloads and health snapshots. Returns: Object containing |
| get_systemA | Fetch a single ComputerSystem resource by URI or ID; if omitted, the first system member is auto-selected. Returns: Object with resolved |
| list_chassisA | List Chassis members and optionally include full details and status for each chassis. Returns: Object containing |
| get_chassisA | Fetch a single Chassis resource by URI or ID; if omitted, the first chassis member is auto-selected. Returns: Object with resolved |
| list_managersA | List Manager members (BMC controllers such as iDRAC/iLO/XCC) and optionally include full payloads and status fields. Returns: Object containing |
| get_managerA | Fetch one Manager (BMC/iDRAC/iLO/XCC) by URI or ID; if omitted, the first manager member is auto-selected. Returns: Object with resolved |
| get_health_summaryA | Collect health/state rollups for Systems, Chassis, and Managers to provide a quick fleet health summary. Returns: Object with |
| get_thermalA | Fetch ThermalSubsystem/Thermal for temperature, fan, and cooling telemetry. Prefer this tool for inlet/exhaust temperature and fan speed requests. Returns: Object with |
| get_powerA | Fetch PowerSubsystem/Power for watts, PSU, power-control, and power-cap telemetry. Prefer this tool for PSU or power-draw requests. Returns: Object with |
| get_sensorsA | 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 |
| get_component_inventoryA | 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 |
| get_log_entriesA | Collect entries from a selected LogService with optional severity and timestamp filtering for troubleshooting workflows. Returns: Object with filtered |
| get_firmware_inventoryA | Retrieve UpdateService firmware inventory members and return each firmware resource payload. Returns: Object with |
| get_boot_configA | Return the Boot section for a system so callers can inspect current override target, mode, and enablement. Returns: Object with |
| get_bios_attributesA | Fetch BIOS attributes and the full BIOS resource for one system. Returns: Object with BIOS |
| list_tasksA | List TaskService task members and optionally include full task resource payloads. Returns: Object with TaskService entries under |
| get_taskA | Fetch a task by URI or task_id; if omitted, the first task member is returned. Returns: Object with a single task payload under |
| list_accountsA | List AccountService account members and optionally include full account payloads. Returns: Object with AccountService entries under |
| list_virtual_mediaA | List VirtualMedia resources for a manager to inspect mounted images and media state. Returns: Object with |
| redfish_getA | 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 |
| redfish_walkA | 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 |
| redfish_describe_schemaA | 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') |
| redfish_list_available_actionsA | 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 |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| triage_unhealthy_hardware | Guided read-only sequence to identify unhealthy systems, chassis, and managers. |
| collect_support_bundle | Read-only workflow for collecting logs, health, and inventory for support. |
| audit_firmware_versions | Read-only firmware inventory audit and drift detection sequence. |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| getting-started | Operator checklist for selecting endpoints, discovering URIs, and safely applying writes. |
| schema-computersystem | Generated schema summary and action guidance for ComputerSystem. |
| schema-chassis | Generated schema summary and action guidance for Chassis. |
| schema-manager | Generated schema summary and action guidance for Manager. |
| schema-task | Generated schema summary and action guidance for Task. |
| schema-updateservice | Generated schema summary and action guidance for UpdateService. |
| schema-virtualmedia | Generated schema summary and action guidance for VirtualMedia. |
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.