Dell iDRAC MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| IDRAC_HOST | Yes | Host name or IP of the iDRAC. `https://` is assumed; a port may be added (e.g. `10.0.0.5:8443`). | |
| IDRAC_PASSWORD | Yes | iDRAC password. | |
| IDRAC_USERNAME | Yes | iDRAC user name. | |
| IDRAC_AUTH_MODE | No | `session` (X-Auth-Token) or `basic` (HTTP Basic on every request). | session |
| IDRAC_VERIFY_TLS | No | Verify the iDRAC's TLS certificate. | false |
| IDRAC_ALLOW_CONFIG | No | `true` selects admin mode (used by the extension). | false |
| IDRAC_ALLOW_ACTIONS | No | `true` selects operator mode (used by the extension). | false |
| IDRAC_MAX_CONCURRENCY | No | Maximum parallel requests to the iDRAC. | 4 |
| IDRAC_PERMISSION_MODE | No | Permission mode: `read-only`, `operator` or `admin`. | read-only |
| IDRAC_TIMEOUT_SECONDS | No | Per-request timeout. | 60 |
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
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| idrac_statusA | Check the connection to the iDRAC and report its firmware, Redfish version, the server model and service tag, and this MCP server's permission mode. Use this first when another tool fails or to confirm the setup works. |
| idrac_getA | GET any Redfish resource on the iDRAC by path, e.g. /redfish/v1/Chassis/System.Embedded.1/Power. Use it for data the dedicated tools do not cover. Responses are returned as JSON and truncated at max_chars. |
| idrac_system_overviewA | One-call summary of the server: model, service tag, BIOS and iDRAC firmware, power state, overall health, CPU and memory totals, current power draw and inlet temperature. A good starting point for most questions. |
| idrac_processorsA | List the installed CPUs with model, cores, threads, speed and health. |
| idrac_memoryA | List memory modules (DIMMs) with slot, size, type, speed, manufacturer, part number and health. Empty slots are hidden unless include_empty is true. |
| idrac_storageA | List storage controllers (PERC RAID and others), their physical disks (model, size, media type, health, predicted failure, SSD wear) and virtual disks (RAID level, size, state). Can take a while on iDRAC 8. |
| idrac_network_interfacesA | List the server's network ports (MAC, link state, speed) and the iDRAC's own network settings (IP address, gateway, DNS servers, host name). |
| idrac_firmware_inventoryA | List firmware versions of the iDRAC, BIOS, Lifecycle Controller, RAID controller, NICs, disks, power supplies and other components. Previous (rollback) versions are hidden unless include_previous is true. |
| idrac_manager_infoA | Details of the iDRAC itself: firmware, date and time, which network services are enabled (HTTPS, SSH, IPMI over LAN, SNMP, virtual console/media) with their ports, NTP servers and the number of open Redfish sessions. |
| idrac_healthA | Check every subsystem (CPUs, memory, fans, temperatures, power supplies, voltages, storage) and list only what is not healthy, plus the most recent warning or critical events from the System Event Log. |
| idrac_thermalA | Current fan speeds (RPM) and temperature readings (inlet, exhaust, CPUs) with their warning and critical thresholds and fan redundancy. Read-only: iDRAC 8 offers no Redfish fan-speed control. |
| idrac_powerA | Current, average, minimum and peak power consumption, power cap, and the power supplies (model, capacity, input voltage, firmware, health) with redundancy. Optionally the voltage sensors. |
| idrac_logsA | Read recent entries, newest first, from the System Event Log ('sel': hardware events such as sensor alarms, power and memory errors) or the Lifecycle Controller log ('lclog': configuration changes, firmware updates, logins, jobs). Filter by minimum severity or text. |
| idrac_list_jobsA | List the iDRAC job queue (BIOS and RAID configuration jobs, firmware updates, exports) with state and progress, or get one job by id. |
| idrac_bios_attributesA | Read the current BIOS settings (attribute names and values), filtered by text or exact names, plus any changes pending for the next reboot. With describe=true the allowed values and help text are included (slow the first time). |
| idrac_boot_settingsA | Show the boot mode (UEFI or BIOS), the boot order, and any one-time boot override with the targets that can be used for it (PXE, virtual CD, BIOS setup, ...). |
| idrac_virtual_mediaA | Show the iDRAC virtual media devices (virtual CD/DVD and removable disk): whether an image is attached, which one, and whether this firmware supports attaching images through Redfish. |
| idrac_export_configA | Export the Server Configuration Profile: every iDRAC, BIOS, NIC and RAID setting as XML. Useful as a backup, to compare settings, or to read iDRAC settings such as thermal profiles that have no other Redfish view. Runs as a short export job on the iDRAC (no settings change); takes 30-120 seconds. |
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 18 tools
Most tools target clearly distinct iDRAC resources or subsystems, and the generic idrac_get is explicitly positioned as a fallback for uncovered data. There is some potential confusion among idrac_status, idrac_system_overview, and idrac_manager_info, plus mild overlap between health, thermal, and power reporting, but their descriptions provide enough separation.
All names use the consistent idrac_ prefix and snake_case, making the set predictable and readable. The only minor inconsistency is that most tools are resource nouns while a few use action-first forms such as idrac_get, idrac_list_jobs, and idrac_export_config.
Eighteen tools is on the heavier side for the 3-15 typical range, but the iDRAC domain is broad and each tool covers a meaningful subsystem or operation. The count is reasonable for comprehensive read-only server diagnostics, though a few reporting tools could arguably be consolidated.
The server covers monitoring comprehensively: system overview, hardware inventory, health, thermal, power, logs, jobs, BIOS reads, boot settings, virtual media state, network interfaces, and config export. However, it lacks lifecycle/control operations such as power actions, BIOS setting writes, virtual media attach, job creation/deletion, firmware updates, and iDRAC/user management, leaving notable gaps if an agent needs to change or operate the server.