clr-openmanage-mcp

MCP server for Dell OpenManage Enterprise (OME) — monitor and manage Dell servers through AI assistants like Claude.

Features

• Device management — list devices, view details, health summary

• Alert management — list, filter, acknowledge alerts (single or bulk)

• Warranty tracking — list warranties, find expired ones

• Firmware compliance — check firmware baselines

• Job monitoring — view OME jobs and their status

• Group & policy management — list device groups and alert policies

• OData pagination — automatic multi-page result fetching

• Session-based auth — secure X-Auth-Token sessions, auto-created and cleaned up

Installation

pip install clr-openmanage-mcp
# or
uvx clr-openmanage-mcp

Configuration

Preferred: Configuration file at ~/.config/openmanage/credentials.json (chmod 600):

{
  "host": "ome.example.com",
  "username": "admin",
  "password": "your-password"
}

Alternative: Environment variables are also supported:

Optional:

Claude Desktop

Add to your claude_desktop_config.json:

{
  "mcpServers": {
    "openmanage": {
      "command": "uvx",
      "args": ["clr-openmanage-mcp"]
    }
  }
}

Claude Code

Add via CLI:

claude mcp add openmanage -- uvx clr-openmanage-mcp

Or add to your .mcp.json:

{
  "openmanage": {
    "command": "uvx",
    "args": ["clr-openmanage-mcp"]
  }
}

VS Code

Add to your VS Code settings or .vscode/mcp.json:

{
  "mcp": {
    "servers": {
      "openmanage": {
        "command": "uvx",
        "args": ["clr-openmanage-mcp"]
      }
    }
  }
}

Note: Configuration is read from ~/.config/openmanage/credentials.json or environment variables. No need to specify credentials in MCP config files.

HTTP Transport

To run as a standalone HTTP server:

clr-openmanage-mcp --transport http --host 0.0.0.0 --port 8000

Tools

System

Devices

Alerts

Alert filter values:

Warranties

Groups, Jobs, Policies & Firmware

Example Usage

Once connected, you can ask your AI assistant things like:

• "Show me all devices in OpenManage"

• "Are there any critical alerts?"

• "Which server warranties have expired?"

• "Acknowledge all warranty alerts"

• "Show me recent jobs"

• "What's the firmware compliance status?"

Safety

All tools are read-only except ome_alert_ack and ome_alert_ack_all, which are non-destructive write operations — they mark alerts as acknowledged but do not modify device configuration.

Technical Notes

• SSL: Self-signed certificate verification is disabled (common for OME appliances)

• Auth: Session-based with X-Auth-Token, auto-created on startup and cleaned up on shutdown

• Pagination: Automatically follows OData @odata.nextLink to fetch all pages (unless top is set)

• Jobs API: OME Jobs API doesn't support $orderby, so results are sorted client-side by LastRun

• Warranty dates: OME doesn't support date comparison in OData $filter for warranty endpoints, so expired warranty filtering is done client-side

Development

git clone https://github.com/clearminds/clr-openmanage-mcp.git
cd clr-openmanage-mcp
uv sync
uv run clr-openmanage-mcp

License

MIT — see LICENSE for details.