clr-openmanage-mcp
MCP server for Dell OpenManage Enterprise that allows AI assistants to monitor and manage Dell servers, including device health, alerts, warranties, firmware compliance, and jobs.
README
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:
| Variable | Description | Example |
|---|---|---|
OME_HOST |
OME server hostname or IP | ome.example.com |
OME_USERNAME |
OME admin username | admin |
OME_PASSWORD |
OME admin password | secretpass |
Optional:
| Variable | Description | Default |
|---|---|---|
OME_READ_ONLY |
Run in read-only mode | false |
OME_TRANSPORT |
Transport protocol (stdio or http) |
stdio |
OME_LOG_LEVEL |
Log level | INFO |
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
| Tool | Description |
|---|---|
ome_version |
Get OME version, build info, and operation status |
Devices
| Tool | Description | Parameters |
|---|---|---|
ome_list_devices |
List all managed devices | top? |
ome_get_device |
Get full detail for a single device | device_id |
ome_device_health |
Aggregate device health summary (count by status) | — |
Alerts
| Tool | Description | Parameters |
|---|---|---|
ome_list_alerts |
List alerts with optional filters | severity?, category?, status?, top? |
ome_get_alert |
Get full detail for a single alert | alert_id |
ome_alert_count |
Alert count aggregated by severity | — |
ome_alert_ack |
Acknowledge one or more alerts by ID | alert_ids |
ome_alert_ack_all |
Acknowledge all unacknowledged alerts matching filters | severity?, category? |
Alert filter values:
| Parameter | Accepted values |
|---|---|
severity |
critical, warning, info, normal |
status |
unack, ack |
category |
e.g. Warranty, System Health |
Warranties
| Tool | Description | Parameters |
|---|---|---|
ome_list_warranties |
List all warranty records | top? |
ome_warranties_expired |
List warranties past their end date | — |
Groups, Jobs, Policies & Firmware
| Tool | Description | Parameters |
|---|---|---|
ome_list_groups |
List device groups | top? |
ome_list_jobs |
List jobs (sorted by most recent) | top? |
ome_list_policies |
List alert policies | top? |
ome_list_firmware |
List firmware compliance baselines | top? |
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.nextLinkto fetch all pages (unlesstopis set) - Jobs API: OME Jobs API doesn't support
$orderby, so results are sorted client-side byLastRun - Warranty dates: OME doesn't support date comparison in OData
$filterfor 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.
推荐服务器
Baidu Map
百度地图核心API现已全面兼容MCP协议,是国内首家兼容MCP协议的地图服务商。
Playwright MCP Server
一个模型上下文协议服务器,它使大型语言模型能够通过结构化的可访问性快照与网页进行交互,而无需视觉模型或屏幕截图。
Magic Component Platform (MCP)
一个由人工智能驱动的工具,可以从自然语言描述生成现代化的用户界面组件,并与流行的集成开发环境(IDE)集成,从而简化用户界面开发流程。
Audiense Insights MCP Server
通过模型上下文协议启用与 Audiense Insights 账户的交互,从而促进营销洞察和受众数据的提取和分析,包括人口统计信息、行为和影响者互动。
VeyraX
一个单一的 MCP 工具,连接你所有喜爱的工具:Gmail、日历以及其他 40 多个工具。
graphlit-mcp-server
模型上下文协议 (MCP) 服务器实现了 MCP 客户端与 Graphlit 服务之间的集成。 除了网络爬取之外,还可以将任何内容(从 Slack 到 Gmail 再到播客订阅源)导入到 Graphlit 项目中,然后从 MCP 客户端检索相关内容。
Kagi MCP Server
一个 MCP 服务器,集成了 Kagi 搜索功能和 Claude AI,使 Claude 能够在回答需要最新信息的问题时执行实时网络搜索。
e2b-mcp-server
使用 MCP 通过 e2b 运行代码。
Neon MCP Server
用于与 Neon 管理 API 和数据库交互的 MCP 服务器
Exa MCP Server
模型上下文协议(MCP)服务器允许像 Claude 这样的 AI 助手使用 Exa AI 搜索 API 进行网络搜索。这种设置允许 AI 模型以安全和受控的方式获取实时的网络信息。