OpManager MCP Server
Enables AI assistants to interact with ManageEngine OpManager for network monitoring and IT operations management. Provides credential-less access to 85+ API endpoints for managing devices, alarms, discovery, dashboards, and reports through natural language.
README
OpManager MCP Server
A credential-less Model Context Protocol (MCP) server for ManageEngine OpManager REST API integration. This server enables AI assistants like Claude to interact with your OpManager infrastructure through natural language.
โจ Key Features
- ๐ Credential-less Design: No hardcoded API keys - users provide
hostandapiKeyper request - ๐ SSL Auto-Detection: Port 8061 โ HTTPS, Port 8060 โ HTTP (with manual override)
- ๐ก 85+ API Endpoints: Full OpManager API coverage for devices, alarms, dashboards, discovery, and more
- ๐ Dynamic Tool Generation: Automatically generates MCP tools from OpenAPI specification
- ๐ Multiple Transports: Supports stdio (Claude Desktop) and HTTP/SSE (n8n, web clients)
- ๐ณ Docker Ready: Containerized deployment with Docker and Docker Compose
๐ Quick Start
Installation
# Clone the repository
git clone https://github.com/sachdev27/opmanager-mcp-server.git
cd opmanager-mcp-server
# Create virtual environment
python -m venv venv
source venv/bin/activate # On Windows: venv\Scripts\activate
# Install the package
pip install -e ".[http]"
Start the HTTP Server
uvicorn opmanager_mcp.http_server:app --host 0.0.0.0 --port 3000
Test a Tool Call
curl -X POST http://localhost:3000/call \
-H "Content-Type: application/json" \
-d '{
"name": "opmanager_get_allDevices",
"arguments": {
"host": "opmanager.example.com",
"apiKey": "your-api-key-here",
"port": 8061
}
}'
๐ Configuration
Environment Variables
Create a .env file (optional - for server defaults only):
cp .env.example .env
| Variable | Description | Default |
|---|---|---|
MCP_SERVER_LOG_LEVEL |
Logging level | INFO |
ALLOWED_HTTP_METHODS |
Allowed HTTP methods for tools | GET,POST,PUT,DELETE,PATCH |
LOCAL_OPENAPI_SPEC_PATH |
Path to OpenAPI spec | bundled openapi.json |
Note:
OPMANAGER_HOSTandOPMANAGER_API_KEYare NOT configured server-side. Users provide these per-request for security.
Getting Your OpManager API Key
- Log in to OpManager web console
- Navigate to Settings โ REST API
- Generate a new API key
- Use this key in your tool calls
๐ง Tool Parameters
Every tool accepts these connection parameters:
| Parameter | Required | Description |
|---|---|---|
host |
โ Yes | OpManager server hostname |
apiKey |
โ Yes | API key for authentication |
port |
No | Server port (default: 8060) |
use_ssl |
No | Force SSL (auto-detected from port) |
verify_ssl |
No | Verify SSL certificates (default: true) |
SSL Auto-Detection
- Port 8061: Automatically uses HTTPS
- Port 8060: Automatically uses HTTP
- Override with
use_ssl: true/falseif needed
๐ HTTP API Endpoints
| Endpoint | Method | Description |
|---|---|---|
/health |
GET | Health check with tool count |
/tools |
GET | List all available tools |
/sse |
GET | SSE connection for MCP |
/messages |
POST | MCP message handler |
/call |
POST | Direct tool invocation |
Health Check
curl http://localhost:3000/health
# {"status":"healthy","tool_count":60}
List Tools
curl http://localhost:3000/tools | jq '.tools[].name'
๐ค n8n Integration
- Start the HTTP server on port 3000
- In n8n, add an AI Agent node with MCP Client tool
- Configure the MCP Client:
- SSE URL:
http://localhost:3000/sse - Messages URL:
http://localhost:3000/messages
- SSE URL:
Example System Prompt for n8n
You are an IT operations assistant with access to OpManager for network monitoring.
When using OpManager tools, always include:
- host: "opmanager.company.com"
- apiKey: "your-api-key"
- port: 8061 (for HTTPS)
Available operations:
- List all devices: opmanager_get_allDevices
- Get device details: opmanager_get_device (requires deviceName)
- List alarms: opmanager_get_alarms
- Acknowledge alarm: opmanager_add_alarmNotes
๐ฅ Claude Desktop Integration
Add to your Claude Desktop config (~/Library/Application Support/Claude/claude_desktop_config.json):
{
"mcpServers": {
"opmanager": {
"command": "python",
"args": ["-m", "opmanager_mcp.main"],
"cwd": "/path/to/opmanager-mcp-server",
"env": {
"LOCAL_OPENAPI_SPEC_PATH": "/path/to/opmanager-mcp-server/openapi.json"
}
}
}
}
Note: With Claude Desktop, you'll tell Claude your OpManager host and API key in conversation, and it will include them in tool calls.
๐ Available Tools (60+ GET operations)
Devices
opmanager_get_allDevices- List all monitored devicesopmanager_get_device- Get device details by nameopmanager_get_deviceAvailability- Device availability history
Alarms
opmanager_get_alarms- List alarms with filteringopmanager_get_alarmDetails- Get alarm detailsopmanager_add_alarmNotes- Add notes/acknowledge alarm
Discovery
opmanager_get_discoveryStatus- Check discovery progressopmanager_add_discovery- Start network discovery
Reports & Dashboards
opmanager_get_allDashboards- List all dashboardsopmanager_get_scheduledReports- List scheduled reports
And more...
Run curl http://localhost:3000/tools to see all available tools.
๐ณ Docker
Build and Run
docker build -t opmanager-mcp-server .
docker run -d -p 3000:3000 --name opmanager-mcp opmanager-mcp-server
Docker Compose
docker-compose up -d
๐งช Development
Run Tests
# Install dev dependencies
pip install -e ".[dev]"
# Run all tests
pytest
# Run with coverage
pytest --cov=opmanager_mcp --cov-report=term-missing
# Current: 32 tests, 50% coverage
Code Quality
# Format
black opmanager_mcp tests
isort opmanager_mcp tests
# Lint
ruff check opmanager_mcp tests
# Type check
mypy opmanager_mcp
Regenerate OpenAPI Spec
python generate_openapi.py
๐ Project Structure
opmanager-mcp-server/
โโโ opmanager_mcp/
โ โโโ __init__.py # Package exports
โ โโโ api_client.py # HTTP client for OpManager API
โ โโโ config.py # Configuration management
โ โโโ exceptions.py # Custom exceptions
โ โโโ http_server.py # HTTP/SSE server (Pure ASGI)
โ โโโ logging_config.py # Logging configuration
โ โโโ main.py # CLI entry point
โ โโโ server.py # MCP server implementation
โ โโโ tool_generator.py # OpenAPI to MCP tool converter
โโโ tests/
โ โโโ conftest.py # Test fixtures
โ โโโ test_api_client.py # API client tests
โ โโโ test_config.py # Config tests
โ โโโ test_http_server.py # HTTP server tests
โ โโโ test_server.py # MCP server tests
โ โโโ test_tool_generator.py # Tool generation tests
โโโ openapi.json # OpManager OpenAPI specification
โโโ pyproject.toml # Project configuration
โโโ Dockerfile # Container image
โโโ docker-compose.yml # Compose configuration
โโโ README.md # This file
๐ License
MIT License - see LICENSE for details.
๐ Acknowledgments
- Built with Model Context Protocol SDK
- OpManager REST API by ManageEngine
Recommended Servers
playwright-mcp
A Model Context Protocol server that enables LLMs to interact with web pages through structured accessibility snapshots without requiring vision models or screenshots.
Magic Component Platform (MCP)
An AI-powered tool that generates modern UI components from natural language descriptions, integrating with popular IDEs to streamline UI development workflow.
Audiense Insights MCP Server
Enables interaction with Audiense Insights accounts via the Model Context Protocol, facilitating the extraction and analysis of marketing insights and audience data including demographics, behavior, and influencer engagement.
VeyraX MCP
Single MCP tool to connect all your favorite tools: Gmail, Calendar and 40 more.
Kagi MCP Server
An MCP server that integrates Kagi search capabilities with Claude AI, enabling Claude to perform real-time web searches when answering questions that require up-to-date information.
graphlit-mcp-server
The Model Context Protocol (MCP) Server enables integration between MCP clients and the Graphlit service. Ingest anything from Slack to Gmail to podcast feeds, in addition to web crawling, into a Graphlit project - and then retrieve relevant contents from the MCP client.
Qdrant Server
This repository is an example of how to create a MCP server for Qdrant, a vector search engine.
Neon Database
MCP server for interacting with Neon Management API and databases
Exa Search
A Model Context Protocol (MCP) server lets AI assistants like Claude use the Exa AI Search API for web searches. This setup allows AI models to get real-time web information in a safe and controlled way.
E2B
Using MCP to run code via e2b.