Logicmonitor MCP Server

What the code does

We read the source, 18 h ago · rules 3dff92dd89df

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(

        env = dict(os.environ)

Is this your server and something here is wrong? Tell us — corrections are free and do not require a plan.

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 -- uvx lm-mcp

{
  "mcpServers": {
    "logicmonitor": {
      "args": [
        "lm-mcp"
      ],
      "command": "uvx"
    }
  }
}

[mcp_servers.logicmonitor]
command = "uvx"
args = ["lm-mcp"]

{
  "mcpServers": {
    "logicmonitor": {
      "args": [
        "lm-mcp"
      ],
      "command": "uvx"
    }
  }
}

{
  "mcpServers": {
    "logicmonitor": {
      "args": [
        "lm-mcp"
      ],
      "command": "uvx"
    }
  }
}

This one needs environment variables set before it will start: LM_PORTAL (LogicMonitor portal hostname (e.g., company.logicmonitor.com)), LM_BEARER_TOKEN (LogicMonitor API Bearer token), 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)). The author declared them in the registry entry; get the values from the project itself.