OpexMX MCP Server
Connect any AI agent to your OpexMX instance via the Model Context Protocol. Let Claude Code, Cursor, Hermes, OpenClaw, or any MCP-compatible agent create tickets, search assets, manage inventory, and more — all authenticated with your API key.
Quick Setup
1. Download the MCP Server
v0.1.0 — Single binary, no installation needed.
2. Get Your API Key
- Open OpexMX and go to Settings → API Keys
- Click Generate New Key
- Copy the key (it starts with
mx_)
3. Configure Your Agent
Claude Code — add to ~/.claude/settings.json:
{
"mcpServers": {
"opexmx": {
"command": "opexmx-mcp",
"env": {
"OPEXMX_API_URL": "https://your-instance.opexmx.com",
"OPEXMX_API_KEY": "mx_your_api_key"
}
}
}
}
Cursor — add to .cursor/mcp.json:
{
"mcpServers": {
"opexmx": {
"command": "opexmx-mcp",
"env": {
"OPEXMX_API_URL": "https://your-instance.opexmx.com",
"OPEXMX_API_KEY": "mx_your_api_key"
}
}
}
}
Hermes / OpenClaw — run via stdio:
export OPEXMX_API_URL="https://your-instance.opexmx.com"
export OPEXMX_API_KEY="mx_your_api_key"
opexmx-mcp
Then configure your agent's MCP client to use the opexmx-mcp binary as the MCP server command.
Available Tools
The MCP server exposes 20+ tools covering the full OpexMX API:
Asset Management
- search_assets — Search assets by name, type, location, or status
- get_asset — Get detailed asset information including hierarchy
- list_asset_children — Get child assets in the hierarchy tree
Work Orders & Tickets
- create_ticket — Create a new maintenance ticket
- search_tickets — Search tickets with filters (status, priority, assignee)
- update_ticket — Update ticket status, priority, or assignment
- add_ticket_comment — Add a comment or update to a ticket
Inventory & Parts
- search_parts — Search spare parts inventory
- get_part_stock — Check current stock levels for a part
- create_purchase_request — Submit a purchase request for parts
Scheduling
- get_pm_schedule — View upcoming preventive maintenance tasks
- list_work_orders — List work orders with date and status filters
Reporting
- get_asset_health — Get health score and condition data for an asset
- get_kpi_summary — Get KPI metrics (MTBF, MTTR, OEE, etc.)
Security
- Each user generates their own API key from Settings
- Agents inherit that user's permissions — no shared credentials
- API keys can be revoked at any time
- All communication is over HTTPS
- No OAuth complexity — simple, long-lived keys
System Requirements
- Binary size: ~1.7 MB
- Memory: ~3 MB RAM
- Runtime: None — single Rust-compiled binary
- Platforms: macOS (ARM/Intel), Linux (x86_64/ARM64), Windows (x86_64)
- Network: Requires outbound HTTPS to your OpexMX instance