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: Sumo Logic MCP Server

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", "service": "logicmonitor-mcp", "transport": "http"}

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

15 tools — matching the 15 LogicMonitor API endpoints already registered under this integration in MSPbots (sys_integration subject_code LOGICMONITOR), so tool coverage is consistent with MSPbots' existing scope.

Devices (3)

Device DataSources (4)

Alerts (3)

Admin (2)

Reports (2)

SDT (1)

测试示例 (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 headers, tools/list returning all 15 tools) has been done so far.

• Tool coverage intentionally matches MSPbots' existing 15 registered LogicMonitor API entries rather than the full LogicMonitor REST API surface (which additionally covers write operations, dashboards, websites, collectors, and LogicModules) — expand on request if broader coverage is needed.