Logicmonitor runs on your own machine — the client starts it, so there is no endpoint to ping. 456 installs a week from pypi. Last commit 31 Oct 2026.
LogicMonitor API integration with 167 tools for alerts, devices, dashboards, and more.
What the code does
We read the source, 1 d ago · rules 995398eba69f
What this server is able to do. For an MCP server this is often the job itself — a terminal server runs commands because that is what it is for. Listed so you know what you are plugging in, not as an accusation.
proc = subprocess.run(
Is this your server and something here is wrong? Tell us — corrections are free and do not require a plan.
This code can reach further than it looks
We found places where it runs commands, builds paths or queries from values it is given. None of that is a flaw by itself — it becomes one when the code changes, and code changes quietly between releases. We re-read it on every one.
Connect this server
This server runs on your own machine — install it with the package manager and the client starts it for you. Package name taken from the official registry entry.
claude mcp add logicmonitor -e 'LM_PORTAL=<LM_PORTAL>' -e 'LM_BEARER_TOKEN=<LM_BEARER_TOKEN>' -- uvx lm-mcp{
"mcpServers": {
"logicmonitor": {
"command": "uvx",
"args": [
"lm-mcp"
],
"env": {
"LM_BEARER_TOKEN": "<LM_BEARER_TOKEN>",
"LM_PORTAL": "<LM_PORTAL>"
}
}
}
}[mcp_servers.logicmonitor]
command = "uvx"
args = ["lm-mcp"]
env = { LM_PORTAL = "<LM_PORTAL>", LM_BEARER_TOKEN = "<LM_BEARER_TOKEN>" }{
"mcpServers": {
"logicmonitor": {
"command": "uvx",
"args": [
"lm-mcp"
],
"env": {
"LM_BEARER_TOKEN": "<LM_BEARER_TOKEN>",
"LM_PORTAL": "<LM_PORTAL>"
}
}
}
}{
"servers": {
"logicmonitor": {
"type": "stdio",
"command": "uvx",
"args": [
"lm-mcp"
],
"env": {
"LM_BEARER_TOKEN": "<LM_BEARER_TOKEN>",
"LM_PORTAL": "<LM_PORTAL>"
}
}
}
}Put your own values in place of
<LM_PORTAL> (LogicMonitor portal hostname (e.g., company.logicmonitor.com)), <LM_BEARER_TOKEN> (LogicMonitor API Bearer token).
The author’s registry entry marks them as required.
Optional settings from the registry entry, left out of the block above:
LM_ENABLE_WRITE_OPERATIONS (Enable write operations (create, update, delete)), LM_ACCESS_ID (LMv1 API access ID (required for log/metric ingestion)), LM_ACCESS_KEY (LMv1 API access key (required for log/metric ingestion)), LM_ENABLED_TOOLS (Comma-separated tool names or glob patterns to enable (e.g., get_*,create_device)), LM_DISABLED_TOOLS (Comma-separated tool names or glob patterns to disable (e.g., delete_*)), LM_LOG_LEVEL (Logging level for API request debugging (debug, info, warning, error)).
Alternatives to Logicmonitor
same job, measured the same wayNew Relic MCP server with 55 tools for APM, alerts, dashboards, synthetics, workflows, and more.
Full Datadog API access: monitors, logs, metrics, traces, dashboards, and observability tools
MCP Server for VictoriaLogs. Provides integration with VictoriaLogs API and documentation
MCP Server for VictoriaLogs. Provides integration with VictoriaLogs API and documentation
MCP Server for VictoriaTraces. Provides integration with VictoriaTraces API and documentation
Deploy web apps via AI agents with sota.io. 9 tools for deploy, logs, env, and more.
MCP Server for VictoriaMetrics. Provides integration with VictoriaMetrics API and documentation
MCP Server for VictoriaMetrics. Provides integration with VictoriaMetrics API and documentation
Logicmonitor — questions
Answers built from our own checks of this server.