Click on "Install Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@OpManager MCP Servershow me all critical alarms in the network"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
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
Start the HTTP Server
Test a Tool Call
π Configuration
Environment Variables
Create a .env file (optional - for server defaults only):
Variable | Description | Default |
| Logging level |
|
| Allowed HTTP methods for tools |
|
| Path to OpenAPI spec | bundled |
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 |
| β Yes | OpManager server hostname |
| β Yes | API key for authentication |
| No | Server port (default: 8060) |
| No | Force SSL (auto-detected from port) |
| 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 |
| GET | Health check with tool count |
| GET | List all available tools |
| GET | SSE connection for MCP |
| POST | MCP message handler |
| POST | Direct tool invocation |
Health Check
List Tools
π€ 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/sseMessages URL:
http://localhost:3000/messages
Example System Prompt for n8n
π₯ Claude Desktop Integration
Add to your Claude Desktop config (~/Library/Application Support/Claude/claude_desktop_config.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 Compose
π§ͺ Development
Run Tests
Code Quality
Regenerate OpenAPI Spec
π Project Structure
π License
MIT License - see LICENSE for details.
π Acknowledgments
Built with Model Context Protocol SDK
OpManager REST API by ManageEngine