Back to MCP Servers
🧩

logicmonitor MCP Server

API key required

LogicMonitor API integration with 167 tools for alerts, devices, dashboards, and more.

To add logicmonitor to Claude, run the install command below or copy the ready-made config for Claude Code, Claude Desktop, Cursor and VS Code further down. Restart your client after adding it and its tools show up in your next conversation. It needs 8 environment variables, listed below.

APIDevTools

Install

uvx lm-mcp@1.5.1

Environment variables

LM_PORTALSet in your MCP config
LM_BEARER_TOKENSet in your MCP config
LM_ENABLE_WRITE_OPERATIONSSet in your MCP config
LM_ACCESS_IDSet in your MCP config
LM_ACCESS_KEYSet in your MCP config
LM_ENABLED_TOOLSSet in your MCP config
LM_DISABLED_TOOLSSet in your MCP config
LM_LOG_LEVELSet in your MCP config

Install with your client

Terminal
claude mcp add logicmonitor --env LM_PORTAL=<YOUR_LM_PORTAL> --env LM_BEARER_TOKEN=<YOUR_LM_BEARER_TOKEN> --env LM_ENABLE_WRITE_OPERATIONS=<YOUR_LM_ENABLE_WRITE_OPERATIONS> --env LM_ACCESS_ID=<YOUR_LM_ACCESS_ID> --env LM_ACCESS_KEY=<YOUR_LM_ACCESS_KEY> --env LM_ENABLED_TOOLS=<YOUR_LM_ENABLED_TOOLS> --env LM_DISABLED_TOOLS=<YOUR_LM_DISABLED_TOOLS> --env LM_LOG_LEVEL=<YOUR_LM_LOG_LEVEL> -- uvx lm-mcp@1.5.1

Run this in a terminal to add the server to Claude Code.

What this does

logicmonitor exposes a set of tools to Claude over the Model Context Protocol. After you add it to claude_desktop_config.json (snippet above) and restart Claude Desktop, those tools become callable inside any conversation.

Requirements

This server needs the following environment variables to be set before it can run:

LM_PORTAL
LM_BEARER_TOKEN
LM_ENABLE_WRITE_OPERATIONS
LM_ACCESS_ID
LM_ACCESS_KEY
LM_ENABLED_TOOLS
LM_DISABLED_TOOLS
LM_LOG_LEVEL

Set these via the env object in your MCP config (see claude_desktop_config.json snippet above).

Frequently asked questions

How do I install logicmonitor?

Run the Claude Code command in the install section to add logicmonitor to Claude Code, or copy the ready-made config for your client from the install section on this page. Restart your client afterwards and the tools appear in your next conversation.

Which clients work with logicmonitor?

This page carries setup and config for Claude Code, Claude Desktop, Cursor and VS Code. Any other MCP client that accepts a standard server config can connect to logicmonitor as well.

Does logicmonitor need an API key?

Yes. Before it can run, set these environment variables: LM_PORTAL, LM_BEARER_TOKEN, LM_ENABLE_WRITE_OPERATIONS, LM_ACCESS_ID, LM_ACCESS_KEY, LM_ENABLED_TOOLS, LM_DISABLED_TOOLS, LM_LOG_LEVEL. They go in the env block of your MCP config.

Imported from the Official MCP Registry. The details above come from the registry entry; the maker can claim this listing to correct them, add docs, and see its traffic.

Is this your MCP server?

Claim this listing to see its traffic, fix details yourself, and skip the review queue on future updates.

Listed on clauderules.net

Add this badge to your README

Show visitors this server is listed in the ClaudeRules directory. The badge links straight to this listing.

Markdown
[![Listed on clauderules.net](https://clauderules.net/api/badge/io-github-ryanmat-logicmonitor)](https://clauderules.net/mcp/io-github-ryanmat-logicmonitor)
HTML
<a href="https://clauderules.net/mcp/io-github-ryanmat-logicmonitor" target="_blank" rel="noopener noreferrer"><img src="https://clauderules.net/api/badge/io-github-ryanmat-logicmonitor" alt="Listed on clauderules.net" /></a>