logicmonitor-mcp

LogicMonitor MCP server — exposes the LogicMonitor REST API (v3, /santaba/rest) as MCP tools.

Overview

This server implements the Model Context Protocol (Streamable HTTP/SSE transport) and wraps the LogicMonitor endpoints used by MSPbots' own LogicMonitor integration. It follows the MSPbots Vendor MCP Service SOP: stateless, no stored credentials, per-request header authentication.

The underlying API authenticates via LMv1 — a per-request HMAC-SHA256 signature computed from an Access Id / Access Key pair (the same scheme MSPbots itself uses for this integration: Company + Access Id + Access Key, no OAuth). This server computes the LMv1 signature itself for every outgoing request from the credentials supplied in that request's headers; it never persists them.

Related MCP server: databricks-mcp

Quick Start

Docker (recommended)

docker compose up --build

The server starts on http://localhost:8080.

Local (uv)

uv sync
python -m logicmonitor_mcp

Health Check

curl http://localhost:8080/health
# {"status": "ok"}

No credentials are required for the health endpoint.

授权参数说明 (Authentication)

Every request to /mcp must include the following HTTP headers:

Missing any of the three headers returns 401 Unauthorized.

Environment Variables

logicmonitor-mcp has no required environment variables — all identity (company/access id/access key) is per-request via headers.

MCP Endpoint

POST http://localhost:8080/mcp

Connect your MCP client with:

• Transport: http (Streamable HTTP / SSE)

• Headers: X-LogicMonitor-Company, X-LogicMonitor-Access-Id, X-LogicMonitor-Access-Key (all required)

Tool List

13 tools. Originally matched the 15 LogicMonitor API endpoints registered under this integration in MSPbots (sys_integration subject_code LOGICMONITOR); get_device_datasource_instances and get_device_datasource_instance_alertsettings were removed after intent-matching testing found their instance-ID drill-down (device → DataSource → instance → alertsettings) added confusion without a clear caller need — the remaining get_device_datasource_data still covers actual collected metrics. All tools are read-only (readOnlyHint=True); there are no write/delete tools in this service.

Pagination: size defaults to 50 and is server-side clamped to a hard cap of 1000 — LogicMonitor's own documented/enforced maximum for this parameter (values above 1000 are silently clamped by LogicMonitor itself; requesting more never errors, it just returns at most 1000). Independent of that, any single tool response is capped at 20,000 characters — if a page of results would exceed it, the response is truncated with truncated/original_count fields rather than returned in full.

Devices (3)

Device DataSources (2)

Alerts (3)

Admin (2)

Reports (2)

SDT (1)

Error Handling

Tool errors are returned as a JSON string (not a protocol-level exception), so an Agent can branch on it programmatically:

{"error": {"code": "upstream_error", "message": "...", "retryable": true}}

code is one of a fixed vocabulary: not_configured, unauthorized, not_found, invalid_argument, rate_limited, upstream_error. retryable indicates whether the same call is safe to retry (true for rate_limited/upstream_error, false otherwise).

Network Robustness

• Outbound timeouts: connect 5s / read 30s / write 10s / pool 5s.

• Limited retry (up to 3 attempts) with capped exponential backoff on 429/5xx, honoring Retry-After when present.

• Each retry attempt recomputes the LMv1 signature from scratch (it embeds the current epoch), so a retried request is never sent with a stale/expired signature.

• A single shared httpx.AsyncClient connection pool is reused for the process lifetime.

测试示例 (Test Example)

List devices:

{
  "method": "tools/call",
  "params": { "name": "logicmonitor_get_devices", "arguments": { "size": 10 } }
}

Equivalent curl against the running server (streamable HTTP MCP endpoint):

curl -X POST http://localhost:8080/mcp \
  -H "Content-Type: application/json" \
  -H "X-LogicMonitor-Company: <company>" \
  -H "X-LogicMonitor-Access-Id: <access_id>" \
  -H "X-LogicMonitor-Access-Key: <access_key>" \
  -d '{
    "jsonrpc": "2.0",
    "id": 1,
    "method": "tools/call",
    "params": { "name": "logicmonitor_get_devices", "arguments": { "size": 10 } }
  }'

A parameterized call:

{
  "method": "tools/call",
  "params": {
    "name": "logicmonitor_get_device_datasources",
    "arguments": { "device_id": "7186" }
  }
}

API Reference

• Official docs: LogicMonitor REST API v3

• Auth scheme: LMv1 API Tokens

• Base URL pattern: https://{company}.logicmonitor.com/santaba/rest

Known Gaps / Not Yet Verified

• Not yet tested against a live LogicMonitor portal — only protocol-level verification (health check, 401 on missing/partial headers, tools/list returning all 13 tools, unit-tested error-code mapping) has been done so far.

• Tool coverage originally matched MSPbots' existing 15 registered LogicMonitor API entries; 2 were removed post intent-matching testing (see Tool List above). Coverage does not extend to the full LogicMonitor REST API surface (which additionally covers write operations, dashboards, websites, collectors, and LogicModules) — expand on request if broader coverage is needed.