Resources & prompts

Beyond tools, mcidrac exposes MCP resources (URIs a client can read) and prompts (pre-canned workflow playbooks).

Live resources

Parameterized URIs that read fresh state on access — cheaper than a tool call for polling loops:

URI	Contents
idrac://{name}/info	Model, service tag, power state, health, firmware
idrac://{name}/sensors	Temperatures, fan RPM, consumed watts
idrac://{name}/sel	Newest 20 System Event Log entries
idrac://{name}/vmedia	Virtual media devices and mounted images
idrac://{name}/jobs	Current Dell job queue
idrac://registry	All configured iDRACs (no credentials)

Errors come back as {"error": "..."} JSON rather than protocol failures, so a broken box doesn’t break a resource-reading loop.

Bundled reference docs

The operational knowledge base ships inside the package and is served as markdown resources — an LLM can consult them before acting:

URI	Contents
idrac://docs/redfish-map	Annotated map of the iDRAC Redfish tree
idrac://docs/firmware-quirks	Known landmines by firmware version
idrac://docs/operations-cookbook	Multi-step recipes
idrac://docs/jobs-and-tasks	The Dell job/task lifecycle

The same content, adapted for humans, lives in this site’s Explanation section.

Prompts

Each prompt expands into a step-by-step playbook that stitches tools and resources together:

Prompt	Arguments	Workflow
health_check	—	Fleet sweep: ping, health, sensors, SEL per box → one-screen table
identify_box	idrac_name	Full identity workup with service tag front and center
prepare_install	idrac_name, iso_url	Guided boot-from-ISO with pre-flight checks and console handoff
diagnose_wedged	idrac_name	The wedged-iDRAC ladder, interactively
firmware_audit	idrac_name	Firmware inventory grouped and flagged (flag, don’t flash)
backup_config	idrac_name	SCP export with storage and restore guidance

In Claude Code these appear as slash commands (/health_check, …) once the server is registered.