Logicmonitor MCP
About
Logicmonitor MCP is a Model Context Protocol server for LogicMonitor that enables AI assistants to interact with LogicMonitor monitoring data and operations. It provides 125 MCP tools (73 read-only, 52 write) for comprehensive LogicMonitor management.
Explore
- 125 MCP Tools for comprehensive LogicMonitor operations (73 read-only, 52 write)
- Unified Server: Single server implementation supporting all transport modes (STDIO, SSE, HTTP)
- Multiple Transport Modes: STDIO for local use, SSE/HTTP for remote access
- Flexible Authentication: No auth (dev), bearer token, or OAuth/OIDC
- CSRF Protection: Automatic CSRF protection for session-based authentication
- Read-Only Mode: Safe monitoring without modification capabilities (enabled by default)
- Flexible Configuration: CLI flags, environment variables, or .env file
- Debug Logging: JSON or human-readable formats with detailed request/response logging
- Tool Filtering: Enable specific tools or disable search functionality
- Rate Limiting: Automatic retry with exponential backoff
- Batch Operations: Process multiple resources efficiently
- Smart Batching: Adaptive concurrency that automatically adjusts to API rate limits
- TLS/HTTPS Support: Optional TLS for secure remote access
Setting up with Highlight
This MCP is not yet compatible with Highlight’s one-click setup. However, you can still use it with Highlight by following these steps:
- Download and install Highlight from highlightai.com/download
- Navigate to the plugins tab and select "Add Custom Plugin"
-
Configure the plugin with the settings below
Plugin Name
Logicmonitor MCPCommand (node, npx, python, etc.)Please refer to the README for specific instructions on how to obtain API keys or other required environment variables.
- Enable "Start Automatically" if you want the plugin to start when Highlight launches
From the repository
- Node.js >= 18 (or Docker)
- LogicMonitor account with API access
- LogicMonitor API Bearer Token
npx logicmonitor-mcp-server
npm install -g logicmonitor-mcp-server
logicmonitor-mcp-server
Add to Claude Desktop (~/Library/Application Support/Claude/claude_desktop_config.json on macOS):
{
"mcpServers": {
"logicmonitor": {
"command": "npx",
"args": ["-y", "logicmonitor-mcp-server"],
"env": {
"LM_COMPANY": "mycompany",
"LM_BEARER_TOKEN": "your-bearer-token-here"
}
}
}
}
Best for: Personal use, Claude Desktop integration, local development
docker run -d -p 3000:3000 \
-e LM_COMPANY=mycompany \
-e LM_BEARER_TOKEN=your-token \
-e MCP_TRANSPORT=streamable-http \
-e OAUTH_PROVIDER=none \
monitoringartist/logicmonitor-mcp-server
npm install
export LM_COMPANY=mycompany
export LM_BEARER_TOKEN=your-bearer-token-here
npm start
| Flag | Environment Variable | Default | Description |
|------|---------------------|---------|-------------|
| --server.tls-cert-file <path> | MCP_TLS_CERT_FILE | - | Path to TLS certificate file for HTTPS. Server uses HTTPS if both cert and key are configured |
| --server.tls-key-file <path> | MCP_TLS_KEY_FILE | - | Path to TLS private key file for HTTPS. Both cert and key required for HTTPS |
Note: By default (when TLS is not configured), the server listens on HTTP protocol. When both certificate and key files are provided, the server automatically switches to HTTPS protocol only.
| Flag | Environment Variable | Default | Description |
|------|---------------------|---------|-------------|
| --enabled-tools <list> | MCP_ENABLED_TOOLS | all | Comma-separated list of enabled tools |
| --read-only | MCP_READ_ONLY | true | Enable only read-only tools (safer). Set MCP_READ_ONLY=false to enable write operations |
| Flag | Environment Variable | Default | Description |
|------|---------------------|---------|-------------|
| --mcp-bearer-token <token> | MCP_BEARER_TOKEN | - | Static bearer token for authenticating clients connecting to the MCP server. Used as an alternative or supplement to OAuth for remote access via SSE/HTTP transports. Not required for STDIO transport. |
| - | OAUTH_PROVIDER | none | OAuth provider type: none (disabled), github, google, azure, okta, auth0, or custom. Set to none or leave unset to disable OAuth authentication. |
Note: This is for authenticating to the MCP server, not for LogicMonitor API access.
Authentication Modes:
- No Authentication (default): If neither MCP_BEARER_TOKEN nor OAuth is configured (OAUTH_PROVIDER=none), unauthenticated access is allowed. Suitable for development/testing only.
- Bearer Token: Simple static token authentication - set MCP_BEARER_TOKEN
- OAuth/OIDC: Enterprise authentication - configure OAUTH_PROVIDER and related settings (see env.example)
- Both: Both authentication methods can work simultaneously
export MCP_TRANSPORT=sse
export MCP_ADDRESS=localhost:3000
export MCP_DEBUG=true
npm start
curl http://localhost:3000/healthz
To enable HTTPS for the SSE or streamable HTTP transport, provide both certificate and key files:
export MCP_TLS_CERT_FILE=/path/to/cert.pem
export MCP_TLS_KEY_FILE=/path/to/key.pem
export MCP_TRANSPORT=sse
npm start
export MCP_READ_ONLY=false
npm start
Read-Only:
- list_escalation_chains - List alert escalation chains
- get_escalation_chain - Get escalation chain details
- list_recipients - List alert recipients
- get_recipient - Get recipient details
- list_recipient_groups - List recipient groups
- get_recipient_group - Get recipient group details
Write Operations:
- create_escalation_chain - Create escalation chain
- update_escalation_chain - Modify escalation chain
- delete_escalation_chain - Delete escalation chain
- create_recipient - Create alert recipient
- update_recipient - Modify recipient
- delete_recipient - Delete recipient
- create_recipient_group - Create recipient group
- update_recipient_group - Modify recipient group
- delete_recipient_group - Delete recipient group
Read-Only:
- list_resource_properties - List custom properties for device
- list_resource_group_properties - List properties for device group
Write Operations:
- update_resource_property - Update device property value
- update_resource_group_property - Update device group property value
| Transport | Authentication | Security Level | Use Case |
|-----------|---------------|----------------|----------|
| STDIO | Not required (local process) | ✅ Secure | Claude Desktop, local CLI |
| SSE/HTTP (no auth) | None (default: OAUTH_PROVIDER=none) | ⚠️ Development only | Local testing |
| SSE/HTTP (bearer) | Static token via MCP_BEARER_TOKEN | ✅ Secure (with HTTPS) | API clients, internal services |
| SSE/HTTP (OAuth) | OAuth/OIDC provider | ✅ Secure (with HTTPS) | Web applications, enterprise SSO |
export LM_COMPANY=mycompany
export LM_BEARER_TOKEN=your-lm-token
export MCP_TRANSPORT=sse
export OAUTH_PROVIDER=none # or omit - this is the default
npm start
``
⚠️ Warning: Unauthenticated access allows anyone to connect. Use only in trusted environments.
export OAUTH_PROVIDER=github # github, google, azure, okta, auth0, custom
export OAUTH_CLIENT_ID=your-client-id
export OAUTH_CLIENT_SECRET=your-client-secret
export OAUTH_SESSION_SECRET=$(openssl rand -hex 32)
export OAUTH_CALLBACK_URL=https://your-domain.com/auth/callback
"401 Unauthorized" when connecting to SSE/HTTP:
- Check that MCP_BEARER_TOKEN is set and matches the token in your request/auth/login
- For OAuth, ensure you've logged in at
- Verify token hasn't expired (OAuth tokens expire, static tokens don't)
"No authentication configured" warning:
- This is expected when OAUTH_PROVIDER=none and MCP_BEARER_TOKEN is not set
- For development, this is fine - server allows unauthenticated access
- For production, configure authentication (see Security Considerations above)
OAuth login not working:
- Verify OAUTH_PROVIDER, OAUTH_CLIENT_ID, OAUTH_CLIENT_SECRET are set correctly--debug --log-level debug`)
- Check callback URL matches OAuth provider configuration
- Review server logs for detailed error messages (
The server provides 122 tools for comprehensive LogicMonitor operations. Tools are categorized by functionality and marked as read-only (safe) or write (modifies data).
Claude Desktop / Cursor
Paste into your MCP client config file to install this server.
{
"mcpServers": {
"logicmonitor mcp": {
"github": {
"command": "docker",
"args": [
"run",
"-i",
"--rm",
"-e",
"LM_COMPANY",
"-e",
"LM_BEARER_TOKEN",
"monitoringartist/logicmonitor-mcp-server"
],
"env": {
"LM_COMPANY": "<YOUR_LOGICMONITOR_COMPANY>",
"LM_BEARER_TOKEN": "<YOUR_LOGICMONITOR_TOKEN>"
}
}
}
}
}McpServers
{
"github": {
"command": "docker",
"args": [
"run",
"-i",
"--rm",
"-e",
"LM_COMPANY",
"-e",
"LM_BEARER_TOKEN",
"monitoringartist/logicmonitor-mcp-server"
],
"env": {
"LM_COMPANY": "<YOUR_LOGICMONITOR_COMPANY>",
"LM_BEARER_TOKEN": "<YOUR_LOGICMONITOR_TOKEN>"
}
}
}Model Context Protocol (MCP) server for LogicMonitor - enables AI assistants to interact with your LogicMonitor.
Features
- 125 MCP Tools for comprehensive LogicMonitor operations (73 read-only, 52 write)
- Unified Server: Single server implementation supporting all transport modes (STDIO, SSE, HTTP)
- Multiple Transport Modes: STDIO for local use, SSE/HTTP for remote access
- Flexible Authentication: No auth (dev), bearer token, or OAuth/OIDC
- CSRF Protection: Automatic CSRF protection for session-based authentication
- Read-Only Mode: Safe monitoring without modification capabilities (enabled by default)
- Flexible Configuration: CLI flags, environment variables, or .env file
- Debug Logging: JSON or human-readable formats with detailed request/response logging
- Tool Filtering: Enable specific tools or disable search functionality
- Rate Limiting: Automatic retry with exponential backoff
- Batch Operations: Process multiple resources efficiently
- Smart Batching: Adaptive concurrency that automatically adjusts to API rate limits
- TLS/HTTPS Support: Optional TLS for secure remote access
Images
Cursor Prompt - Resource Check Demo
High‑level demonstration of using the LogicMonitor MCP server in Cursor, showing how to execute a
LogicMonitor resource check using an MCP prompt with the argument "www.google.com" (a resource in LogicMonitor).
The agent has knowledge about available MCP tools and uses them in a self‑correcting way:
Cursor Tools
Screenshot showing the available LogicMonitor MCP tools within Cursor:
Grafana Assistant Tools
Screenshot showing the available LogicMonitor MCP tools within Grafana Assistant:
VS Code Tools
Screenshot showing the available LogicMonitor MCP tools within Visual Studio Code:
Installation Options
Local LogicMonitor MCP server
Run LogicMonitor MCP Server locally with STDIO transport for Claude Desktop:
```bash
Sign in to leave a review
Use Google, GitHub, or an email account so ratings stay tied to real people.
No reviews posted yet.
