LogicMonitor API integration with 120 tools for alerts, devices, metrics, and SDTs.
Copy the AI prompt to install this server into Claude Code, Cursor, or another agent β or use 1-click editor setup below.
We haven't yet run this listing's install command through our automated sandbox check. This isn't a red flag β we're steadily working through the catalog.
π‘ Paste the JSON block into your client's configuration file under mcpServers, then restart the application.
Inspect callable tools, capabilities, and parameters exposed to AI agents by Logicmonitor.
search_toolskeyword search across every tool by name and description
Model Context Protocol (MCP) server for LogicMonitor REST API v3 integration. Enables AI assistants to interact with LogicMonitor monitoring data through 306 structured tools, 15 workflow prompts, and 26 resources. Optional integrations: IBM watsonx.ai for Granite TTM forecasting and NL summaries, Terraform IaC for any provider, and HuggingFace local Granite model fallback.
Works with any MCP-compatible client: Claude Desktop, Claude Code, Cursor, Continue, Cline, and more.
1. Get your LogicMonitor Bearer Token:
2. Configure your MCP client:
For Claude Code (CLI):
With IBM watsonx.ai integration (optional -- adds Granite TTM forecasting and NL summaries):
With Terraform IaC (optional -- adds terraform plan/apply/generate tools):
With HuggingFace local models (optional -- local Granite TTM + NL summaries, no cloud API needed):
For Claude Desktop, add to your config file (see MCP Client Configuration below).
3. Verify it's working:
You should see: logicmonitor: uvx --from lm-mcp lm-mcp-server - β Connected
4. Test with a prompt:
Multi-portal mode arrives, hardened. A single server can now serve many customer
portals, selecting the active one at runtime with list_portals, use_portal,
current_portal, and reload_portals β one entry in your MCP client instead of
one server (and one pasted token) per portal. Credentials live in an
age-encrypted vault, every portal is read-only unless its vault record says
otherwise, and the mode is deliberately stdio-only: the server refuses to start
it on the shared HTTP transport. The release also carries a full dependency
refresh clearing 53 dependabot alerts across the lockfile.
Native OTLP metrics arrive. LogicMonitor's new OTLP Metrics feature (feature-flag
gated, Prometheus-backed) ships in its first phase with a single UI surface (the
dashboard Advanced Metrics Widget) and no Metrics Explorer yet; these four tools
are the first programmatic window into that data: get_otlp_metric_names,
get_otlp_metric_labels, and get_otlp_label_values for discovery, and
query_otlp_metrics for full PromQL range queries returning time-series matrices.
All four were validated live against a flag-enabled portal fed by a real OTel
collector (Kubernetes cAdvisor and application metrics), translate the
feature-disabled portal responses into a clear availability notice, and cap large
matrix responses with even-stride downsampling so they stay LLM-friendly.
Major. Every tool now wraps an endpoint proven to exist, validated against a live
portal. Six tools that called nonexistent API paths since introduction are removed
(get_cloud_cost_accounts, get_cost_summary, get_resource_cost,
get_remediation_status, get_remediation_history, get_batchjob_history); the cost
recommendation tools move onto the working /cost-optimization API; the Service Insight
tools query real Service Insight objects (deviceType 6 devices and BizService groups)
instead of the legacy v1 websites API. The Automated Diagnostics & Remediation surface
arrives in full: get_diagnostic_remediation_assignments and
get_diagnostic_remediation_results (structured execution records with script output,
replacing audit-log scraping), execute_diagnostic, full CRUD plus import/export for
diagnostic and remediation sources, and the new action chain / action rule namespace
(11 tools including the set_action_rule_status toggle). update_logicmodule gains the
two new source types and its apply mode actually applies now (it previously tripped its
own sub-tools' confirm guards). run_report executions are pollable via
get_report_execution, get_alert_details can fetch the full message body, and NextGen
reports are visible to the report list tools.
Full release history, including v3.9.x and earlier, is in CHANGELOG.md. The v3.8.0 networking intelligence tools have a dedicated reference: documentation/networking-intelligence.md.
306 Tools across comprehensive LogicMonitor API coverage (277 LM + 18 AAP + 10 Terraform + 1 watsonx):
Server-side intelligence that transforms raw monitoring data into actionable insights:
Pure-Python statistical methods for capacity planning, trend analysis, and operational scoring:
Multi-step analysis tools that combine several sub-tools into a single call. Each supports detail_level ("summary" or "full"), optional summarize=true for plain-English NL summaries via IBM Granite (requires watsonx.ai), and handles sub-tool failures gracefully with partial results.
Factual signals from GitHub, npm, and our automated checks β not a rating.
No reviews yet β be the first to share how this listing worked for you.
Showcase your server listing on GitHub or your project documentation. Embed this dynamic SVG badge to highlight official listing status and live engagement.
[](https://allmcps.com/mcp/logicmonitor)<a href="https://allmcps.com/mcp/logicmonitor"><img src="https://allmcps.com/api/badge/logicmonitor?style=directory" alt="Logicmonitor on AllMCPs" /></a>