io.github.ryanmat/logicmonitor
Provides optional Terraform IaC integration for any provider, enabling generation of Terraform HCL configuration for LogicMonitor resources and supporting Terraform plan/apply/generate workflows.
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@io.github.ryanmat/logicmonitor Summarize current active alerts and their device impact for the last 24 hours."
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
LogicMonitor MCP Server
A Model Context Protocol (MCP) server that gives AI assistants the LogicMonitor REST API v3 through 273 tools, 3 workflow prompts and 25 resources.
Upgrading from 4.x
5.0.0 is a breaking release. Check a setup that worked on 4.3.0 against these before it moves to 5.x. The CHANGELOG has the rest under Upgrading from 4.3.0.
82 of the 306 tool names in 4.3.0 no longer answer: 7 are renamed and 75 removed. The CHANGELOG's table gives each one's 5.0 name or what to call instead.
A tool that changes the portal is listed only with
LM_ENABLE_WRITE_OPERATIONS=true. 4.3.0 listed its write tools and refused the call.A failed call returns one JSON envelope,
{"error": {"code", "message", ...}}, in place of theError:andSuggestion:lines.uvx --from lm-mcp lm-mcp-servertakes the newest release the first time it runs on a machine and uv's cached one after that, so a setup moves to 5.x when that cache is cleared or refreshed.uv tool install lm-mcpstays on its version untiluv tool upgrade lm-mcp. To hold a setup on 4.3.0, start it withuvx --from lm-mcp==4.3.0 lm-mcp-server.
Related MCP server: mcp-m365-mgmt
Overview
Your MCP client starts the server as a subprocess and talks to it over stdio; the server calls your portal with your API token. It can also run as an HTTP service that serves MCP at /mcp.
Of the 273 tools, 261 are there with one portal. Multi-portal mode adds four portal tools, and Edwin AI credentials add eight Edwin tools. The server lists a tool that changes the portal only when you set LM_ENABLE_WRITE_OPERATIONS=true, and refuses it by name until then, so by default a client sees 150 of them (154 in multi-portal mode, 7 more with Edwin credentials).
Before one of the 36 destructive tools runs, the server asks you to confirm when the client supports MCP elicitation. Where it cannot ask, as over the stateless HTTP transport, the write setting is the only check.
Setup
You need uv for uvx, and a LogicMonitor API token: a Bearer token, or an LMv1 access ID and key.
Claude Code
In your portal, go to Settings > Users and Roles > API Tokens.
Create an API-only user or add a token to an existing user, then copy the Bearer token.
Add the server:
claude mcp add logicmonitor \ -e LM_PORTAL=yourcompany.logicmonitor.com \ -e LM_BEARER_TOKEN=<your-bearer-token> \ -- uvx --from lm-mcp lm-mcp-serverRun
claude mcp list. It listslogicmonitoras connected.Ask your assistant to "List the first 5 devices in LogicMonitor".
Other clients
Claude Desktop, Cursor and Gemini CLI read the same block:
{
"mcpServers": {
"logicmonitor": {
"command": "uvx",
"args": ["--from", "lm-mcp", "lm-mcp-server"],
"env": {
"LM_PORTAL": "yourcompany.logicmonitor.com",
"LM_BEARER_TOKEN": "your-bearer-token"
}
}
}
}documentation/client-setup.md has each client's config file and steps, including VS Code and OpenAI Codex CLI, whose formats differ. If your Cursor release still sends only the first 40 MCP tools to the agent, that page shows how to narrow the list with LM_MCP_CATEGORIES.
Container
The image on GitHub Container Registry runs the HTTP transport on port 8080:
docker run --rm -p 8080:8080 \
-e LM_PORTAL=yourcompany.logicmonitor.com \
-e LM_BEARER_TOKEN=<your-bearer-token> \
-e LM_HTTP_AUTH_TOKEN=<a-secret-of-16-characters-or-more> \
ghcr.io/ryanmat/mcp-server-logicmonitor:latestPoint a Streamable HTTP client at http://127.0.0.1:8080/mcp with the header Authorization: Bearer <LM_HTTP_AUTH_TOKEN>. Deployment covers compose, TLS and Kubernetes.
Other install methods
# pip
pip install lm-mcp
# a persistent install; uv tool upgrade lm-mcp picks up a new release
uv tool install lm-mcp
# from source
git clone https://github.com/ryanmat/mcp-server-logicmonitor.git
cd mcp-server-logicmonitor
uv sync
uv run lm-mcp-serverRestart your MCP client after an upgrade.
Usage
Ask your assistant in plain language:
"Triage the critical alerts from the last 4 hours"
"Run a health check on device 123"
"Give me a portal overview for shift handoff"
"Forecast when memory on device 123 reaches 90 percent"
"What is the blast radius if device 789 goes down?"
"Acknowledge alert LMA12345 with the note 'Investigating disk issue'"
"Create a 2-hour SDT for device 123"
The tools also take LogicMonitor filter syntax, for example displayName~"prod",hostStatus:"normal". String values, hostStatus words included, are quoted.
Find a tool
Start with search_tools. It searches the tools your settings list by keyword, so with writes off it names no write tool, and category narrows it to one group. The lm://guide/tool-categories resource groups all 273 tools by domain, and documentation/tools.md lists every tool with its parameters and whether it writes, generated from the registry.
Tool families
Family | What the tools cover |
Alerts | Query, acknowledge, bulk acknowledge, escalate and annotate alerts; alert rules; datapoint thresholds, read at instance, device or group level with the level each comes from, and set or cleared at instance or group level |
Devices | Devices and groups, their properties and manual instances; Active Discovery scheduling; the device delta, to follow what changed; the unmonitored devices a NetScan found |
Metrics | Datasources and the devices each applies to, instances, metric data and graphs |
Dashboards | Dashboards, widgets and dashboard groups |
SDT | Scheduled downtime, one at a time or in bulk |
Collectors | Collectors and collector groups, with the operations below |
Websites | Synthetic checks, website groups and checkpoint locations |
Reports | List, view, run and schedule reports |
Escalations | Escalation chains and recipient groups |
Users and audit | Users, roles, access groups, API tokens, audit logs and ops notes |
LogicModules | Data, config, event, property, topology, log, diagnostic and remediation sources: query, create, update, delete and import, and read any as its full REST object with |
Diagnostics and remediation | Assigned sources, execution results with script output, manual runs, action chains and action rules |
Services | Service Insights services, service groups and rules |
APM | Traced services and their alerts; a service's operations, metrics and properties through the device tools |
Network | Neighbors, interfaces, flows, connections, top talkers and link flaps. See networking intelligence |
Usage and cost | The contract's entitlements per feature, current resource counts (not billing figures), cost recommendations and idle resources |
Ingestion |
|
Batch jobs | Batch jobs and the BatchJob datasources on a device |
update_logicmodule(type, id, changes, mode) is the safe way to change a LogicModule: it reads the definition, deep-merges changes, checks required fields, and returns a dry-run diff unless you ask it to apply.
get_device_flows and get_device_top_talkers answer FEATURE_DISABLED when the portal has NetFlow off, as the only portal tested does, so their row shapes are unverified against NetFlow data.
Analytics and composites
The analytics run in the server, so an assistant gets an answer in one call:
analyze_metricreads one series once for its summary, trend, seasonality, change points, anomalies and a forecast to a threshold, and can compare it with an earlier window.analyze_alertsclusters a window's alerts and reports statistics, noise, flapping and bursts.correlate_metrics,calculate_availability(with MTTR and an SLO error budget) andanalyze_blast_radiuscover the rest.
The composites combine several reads to answer a common investigation: triage, diagnose, health_check, portal_overview, capacity_plan and detect_site_outage. Each takes detail_level (summary or full) and returns what it could read when a sub-call fails. triage, portal_overview, capacity_plan and detect_site_outage send a progress notification per phase when the request carries a progress token. These eleven tools declare an output schema and return structured content beside the JSON text.
Edwin AI
Set EDWIN_CLIENT_ID and EDWIN_CLIENT_TOKEN to an Edwin AI API credential and the server lists eight more tools:
get_edwin_insightsandget_edwin_insightread the incidents Edwin built from correlated alerts, with its root cause and remediation analysis when it has one.get_edwin_records,get_edwin_alert_volumeandget_edwin_metadataread Edwin's copy of alerts and events and its data model.get_edwin_toolslists Edwin's agent tools, andedwin_run_toolruns one. It needs writes on, every run is audited, and multi-portal mode leaves it out, since one Edwin tenant serves every portal there.ask_edwinasks Edwin a question and waits up to two minutes for the answer.
The server calls https://<portal name>.dexda.ai unless EDWIN_HOST names another host; multi-portal mode has no portal name to derive it from, so set EDWIN_HOST there. A credential that lacks a scope a tool needs gets SCOPE_MISSING naming the scope.
Logs
get_log_pipelines, get_tracked_log_queries, get_log_query_groups, get_log_partitions and get_log_usage read LM Logs configuration and usage, and ingest_logs sends log lines. There is no log search: the v3 search endpoint applied neither the query nor the time range when probed.
OpenTelemetry metrics
get_otlp_metric_names, get_otlp_metric_labels and get_otlp_label_values explore the OTLP metrics your portal holds, and query_otlp_metrics runs a PromQL instant or range query. analyze_metric(source="otlp") analyzes a PromQL series, and add_widget and update_widget take an OTLP query for an advanced metrics widget. Alert rules cannot hold one: the v3 alert rule has no query field.
Collector operations
get_collectors marks each collector is_down, and get_collector_health adds the latest status check and five latest events for the collector you name and for each one not known to be up. The events, uploaded log files and upgrade history are readable too. With writes on, run_collector_status_check, restart_collector, acknowledge_collector_down and collector_debug act on a collector; collector_debug runs one debug command from a fixed list, and the portal records each session in its audit log. OpenTelemetry (lmotel) collectors are not listed: the v3 API does not return them.
Terraform imports
get_terraform_imports lists one resource type's objects as import blocks for the logicmonitor/logicmonitor provider, one per object:
import {
to = logicmonitor_device_group.linux_servers_18
id = "18"
}It covers 15 of the 16 types whose provider docs (2.1.7) import by ID: alert_rule, collector, collector_group, dashboard, dashboard_group, datasource, device, device_group, escalation_chain, report_group, role, sdt, website, website_group and widget. It refuses device_group_cluster_alert_conf, whose importer reads a conf by ID without its device group, a read the API answers with 404. Each address ends with the object's ID, so objects that share a name get distinct addresses.
Save the blocks in a .tf file beside the provider configuration:
terraform {
required_providers {
logicmonitor = {
source = "logicmonitor/logicmonitor"
}
}
}
provider "logicmonitor" {}Then run terraform init and terraform plan -generate-config-out=generated.tf (Terraform 1.5 or later), and review generated.tf before terraform apply.
The provider authenticates only with an LMv1 token, api_id and api_key (LM_API_ID, LM_API_KEY), plus company (LM_COMPANY). It takes no Bearer token, so a server set up with LM_BEARER_TOKEN alone needs an LMv1 token for Terraform.
What the server does not do
The server does not run Terraform or launch Ansible jobs. Run Terraform with the terraform CLI, or HashiCorp's Terraform MCP server, which drives runs in HCP Terraform and Terraform Enterprise. Launch Ansible jobs with ansible-playbook, or Red Hat's MCP server for Ansible Automation Platform, a Technology Preview in AAP 2.6.4.
The portal refuses API tokens on API version 4 ("External calls are not supported for API Version 4"), so trace and span search, service maps, Resource Explorer, Cloud Operations billing and the lmotel collector list are out of the server's reach.
Multi-portal mode
One server entry can serve many portals. Set LM_MULTI_PORTAL=true and point the server at a credential vault: an age-encrypted file, or a plaintext JSON file for testing. get_portals, use_portal, get_current_portal and run_portal_reload manage the active portal, and every LogicMonitor tool takes an optional portal argument that runs one call against another portal. Each portal is read-only unless its record marks it writable. The mode is stdio-only. See MULTIPORTAL.md.
Claude Code skills
The repository ships slash-command runbooks. Clone it and run /lm-triage in Claude Code.
Command | What it does |
| Triage alerts: one |
| A device health check: CPU, memory and disk, anomalies, open alerts, availability and topology neighbors |
| A portal-wide overview: alert volume, clusters, noise, collectors, active SDTs, open critical and error alerts, and dead devices |
| Capacity planning: level, trend, daily and weekly cycles, level shifts and threshold-breach forecasts |
| APM: services, operation-level RED metrics and alert correlation |
| Diagnose an alert, then run an assigned RemediationSource or an Edwin AI agent tool after a checklist and your confirmation |
| Check an Edwin AI insight's root cause against the causal CI's metric and the alert window |
| Review LM Logs partitions and their contracts, the pipelines that name them, usage, and saved and tracked queries |
Resources and prompts
Clients read these through the standard MCP resource and prompt calls.
URI | Description |
| Alert object fields, types, and descriptions |
| Device object fields and types |
| SDT (Scheduled Downtime) object fields |
| Dashboard object fields |
| Collector object fields |
| Escalation chain object fields |
| Report object fields |
| Website check object fields |
| DataSource definition fields |
| User object fields |
| Audit log entry fields |
| Alert severity levels: critical(4), error(3), warning(2), info(1) |
| Device status words: normal, dead, dead-collector, unmonitored, disabled |
| SDT types: DeviceSDT, DeviceGroupSDT, etc. |
| Alert cleared status: true, false |
| Alert acknowledgment status: true, false |
| Collector build types: EA, GD, MGD |
| Filter fields and operators for alert queries |
| Filter fields and operators for device queries |
| Filter fields and operators for SDT queries |
| Filter operators: |
| All 273 tools organized by domain category |
| Common filter patterns and query examples |
| Patterns for combining LogicMonitor with other MCP servers |
| Scenario-based best practices with recommendations and anti-patterns |
Prompt | Description | Arguments |
| Analyze active alerts, identify patterns, suggest root cause |
|
| Review resource utilization and identify capacity concerns |
|
| Execute a LogicMonitor remediation source with pre-execution safety checks |
|
Layout
Path | Contents |
| Entry point ( |
| Tool definitions and the handler map |
| Tool handlers, one module per domain |
| Async HTTP clients for the LogicMonitor and Edwin AI APIs |
| Bearer and LMv1 authentication |
| Stdio and HTTP transports |
| MCP prompts and reference resources |
| Claude Code skills |
| Tool reference (generated), client setup, networking intelligence |
| Dockerfile, compose file, Caddyfile, Kubernetes manifest |
| MCP Registry manifest |
| pytest suite and contract fixtures |
Configuration
Set these as environment variables, through your client's env block or -e flags. The server does not read a .env file; to use one from a clone, run uv run --env-file .env lm-mcp-server. server.json lists the same variables for registry clients.
Authentication
Set LM_BEARER_TOKEN, or LM_ACCESS_ID and LM_ACCESS_KEY for an LMv1 token. Either works for every tool, ingest_logs and push_metrics included; with both set, the server uses the Bearer token. To create an LMv1 token, go to Settings > Users and Roles > Users, select a user, open the API Tokens tab, and create the access ID and key.
Portal, tools and requests
Variable | Required | Default | Description |
| Yes, one portal | - | Portal hostname, such as |
| Yes, or LMv1 | - | API Bearer token (10 characters or more) |
| For LMv1 | - | LMv1 access ID; with |
| For LMv1 | - | LMv1 access key |
| No |
| List and allow the tools that change the portal |
| No | - | Comma-separated tool names or glob patterns to enable, such as |
| No | - | Comma-separated tool names or glob patterns to disable, such as |
| No | - | Comma-separated categories to list: |
| No |
| Request timeout in seconds, 5 to 300 |
| No |
| Resends of a rate-limited request, and of a 5xx on an idempotent request (GET, PUT, DELETE); a POST or PATCH that gets a 5xx is not resent. 0 to 10 |
| No |
| Longest wait between retries. A |
| No |
| Tool calls kept in the session history, 0 to 1000 |
| No |
|
|
Multi-portal and Edwin AI
Variable | Required | Default | Description |
| No |
| Serve several portals from one server, chosen with |
| No | - | Age-encrypted portal vault |
| No | - | Age identity file that decrypts the vault |
| No | - | Plaintext JSON portal map, for testing; the vault wins when both are set |
| No | - | Edwin AI API credential client ID. With |
| No | - | Secret of that Edwin AI credential |
| No |
| Edwin AI base URL, https only. Required in multi-portal mode |
HTTP transport
Variable | Required | Default | Description |
| No |
|
|
| No |
| Bind address. Any address but |
| No |
| Port |
| No | - | Bearer token required on every path except |
| No |
| Start on a non-loopback bind with no |
| No | - | Comma-separated |
| No | - | TLS certificate; with |
| No | - | TLS private key |
| No | - | Password of an encrypted TLS private key |
| No |
| Add a LogicMonitor API call to |
Deployment
Stdio needs no deployment: your client starts the server. The HTTP transport serves MCP at /mcp through the MCP SDK's Streamable HTTP, stateless and answering with JSON, beside the health and info routes. With LM_HTTP_AUTH_TOKEN set, /mcp requires it like every route outside / and the health endpoints. /mcp refuses a body that is not application/json with 415, and one over 4 MiB with 413.
cd deploy
cp .env.example .env
# Edit .env with your credentials, including LM_HTTP_AUTH_TOKEN (required)
docker compose up -d # HTTP on port 8080
docker compose --profile tls up -d # behind Caddy with TLSHealth endpoints for orchestration:
GET /health: every component's status, plus the API connectivity check whenLM_HEALTH_CHECK_CONNECTIVITYis on and the caller passes the bearer checkGET /healthz: liveness, 200 or 503GET /readyz: readiness from local checks only; never calls the LogicMonitor API
Every route except /healthz and /readyz answers only the Host names the server expects (the loopback names, a non-wildcard LM_HTTP_HOST and LM_HTTP_ALLOWED_HOSTS) and refuses others with 400; the two probes accept any Host, so probes by pod IP work. The compose file requires LM_HTTP_AUTH_TOKEN in every profile and passes DOMAIN through as an allowed host for the tls profile.
deploy/k8s/deployment.yaml is a Deployment and Service for the published image that runs on AKS, EKS, GKE, OpenShift or plain Kubernetes. It reads credentials from a secret you create, documented at the top of the file, and wires the liveness and readiness probes to the endpoints above. Apply it with kubectl apply -f deploy/k8s/deployment.yaml.
SECURITY.md describes the exposure model.
Troubleshooting
The server logs to stderr. Set LM_LOG_LEVEL=debug to add the httpx and MCP SDK lines.
"Failed to connect" in Claude Code
The server is missing environment variables. Claude Code starts it with its own environment, so variables in your shell or a .env file do not reach it; pass them with -e:
claude mcp remove logicmonitor
claude mcp add logicmonitor \
-e LM_PORTAL=yourcompany.logicmonitor.com \
-e LM_BEARER_TOKEN=<your-bearer-token> \
-- uvx --from lm-mcp lm-mcp-server"Write operations are disabled"
The tools that change the portal are off by default: the server does not list them, and a call to one by name returns this error. Set LM_ENABLE_WRITE_OPERATIONS=true.
"spawn uvx ENOENT" in Claude Desktop
Claude Desktop cannot find uvx. Find its path with which uvx and use the full path:
{
"command": "/Users/yourname/.local/bin/uvx",
"args": ["--from", "lm-mcp", "lm-mcp-server"]
}The server refuses to start with LM_TRANSPORT=http
The default bind is 0.0.0.0, which needs LM_HTTP_AUTH_TOKEN. Set the token, bind to 127.0.0.1, or set LM_HTTP_ALLOW_UNAUTHENTICATED=true for a listener protected another way.
Authentication errors
Check that the token is active and that its user's role grants the access the tool needs. Manage tokens under Settings > Users and Roles > API Tokens.
Rate limits
The server retries a rate-limited request with exponential backoff, waiting at least what Retry-After asks up to LM_RETRY_AFTER_CAP_SECONDS. If you keep hitting limits, make fewer calls.
Development
uv sync --extra http
uv run pytest
uv run ruff check src tests
uv run ruff format src testsCONTRIBUTING.md has the workflow, the type-check ratchet, and what to regenerate after a tool change.
License
MIT License. See LICENSE.
Available Tools
150 toolsanalyze_alertsARead-onlyIdempotent
Analyze one alert window: call this for how many alerts fired and when, which alerts belong together, how noisy alerting is, which datasources burst, or which portal changes preceded a spike over the last hours. One read of the window's active and cleared alerts, under the severity, device, group and datasource filters, feeds every section; 'statistics' gives active and cleared totals, counts by severity, the ten busiest devices and datasources, and the volume of each hour, cleared alerts included; 'clusters' groups two or more alerts by device, by datasource and by signature (datasource and datapoint) and lists the five largest of each type, each with its alert count, its ten most severe alert ids, up to ten of its devices with device_count, and first and last start times, while cluster_count and by_type count every cluster; a device cluster names the device_id its alerts share, null for a website or two devices under one name; 'noise' gives a 0 to 100 score from the entropy of alerts over datasource and datapoint (weight 40), flaps, an alert on the same device and datapoint that re-fires within 30 minutes of clearing (30), and repeats, a combination with three or more alerts (30), with the first ten flap pairs and tuning recommendations; 'bursts' gives the windows of window_seconds on one datasource that hold at least min_alerts alerts on min_devices devices, the ten largest listed and all counted in bursts_detected; 'changes' reads the audit log once and pairs each change (a create, update, delete or import, read from the entry's description) with the first 5-minute alert spike, a bucket above the mean by one standard deviation, within correlation_window_minutes after it, with a confidence from 1.0 to 0.5; it lists the ten pairs of highest confidence and counts them all in total_correlated. Narrow the filters to see what a bounded list leaves out. truncated says when the 5000-alert cap cut either read short. Use get_alerts to list or page through the alerts themselves.
Inputs: hours, device, analyses, group_id, +6 more. Returns: hours, noise, bursts, portal, +7 more
analyze_blast_radiusARead-onlyIdempotent
Count the devices a device failure could reach through topology neighbors: neighbor_count at depth 1, dependent_count beyond it, each device's alert status, and critical path devices. A device whose neighbors neither topology path answers is listed under unreadable with a warning, never counted as zero; on a portal without those routes every read is unreadable.
Inputs: device_id (required), depth. Returns: depth, portal, warning, degraded, +9 more
analyze_metricARead-onlyIdempotent
Analyze one device instance's metric series, such as CPU, memory or disk usage: call this for statistics on a datapoint's recent history, such as its current level against the window, whether it is rising, its daily cycle, when it shifted, or which samples stand out. One paged read of the window feeds every section; 'summary' gives latest, mean, standard deviation, min, max and the latest sample's signed z-score; 'trend' gives least-squares and Theil-Sen slopes per hour, r-squared, coefficient of variation, the detrended 24-hour autocorrelation and a label (volatile, cyclic, increasing, decreasing or stable); 'seasonality' gives detrended autocorrelation at 1, 4, 12, 24 and 168 hours, the dominant period and the peak hours in UTC; 'change_points' gives level shifts, where the mean of the next 30 samples leaves the mean of the previous 30 by five times the noise in that comparison (measured with any steady trend and autocorrelation the noise has), with the daily cycle removed first when the window holds three days or more and that leaves less noise; each shift has its timestamp and the levels before and after it, less the daily cycle when that was removed. A change in the last 30 samples is not reported yet, small shifts in strongly autocorrelated noise go unfound, on a window under a day a change inflates the noise and smaller shifts go unfound, and changes about a day apart in a few days leave the cycle in and go unfound; 'anomalies' gives z-score, IQR and MAD hits, each method's 20 most extreme; 'forecast' gives the least-squares and Holt-Winters (daily season, two days of samples needed) slopes per hour and, with threshold, when each crosses it, within 30 days; 'baseline' compares the window with one as long ending baseline_hours_ago hours ago (one more read): both windows' statistics, the mean's percent deviation and a status (normal within 20 percent, elevated or reduced within 50, anomalous past it). The baseline runs only with baseline_hours_ago. Use get_device_data for the raw samples. With source="otlp" it reads one PromQL range query (query, hours, step) in place of a device instance and runs the same sections on each series it returns, the first 20.
Inputs: step, hours, query, source, +7 more. Returns: step, hours, query, portal, +10 more
audit_network_monitoring_coverageARead-onlyIdempotent
Portal audit that counts UPS/PDU devices onboarded, interface DataSources applied, SNMP credentials configured, and NetFlow exporters set up. Returns a prioritized gap list, each gap with the onboarding step that would let the portal detect what it cannot detect today.
Inputs: group_id.
calculate_availabilityARead-onlyIdempotent
Calculate availability percentage from alert history. Computes SLA-style uptime metrics, MTTR, and per-device breakdown from the window's cleared and active alerts, read as two lists; truncated says when the 5000-alert cap cut either read short. With target_slo it adds error_budget for the window: budget, consumed and remaining minutes, percent consumed, burn rate, projected exhaustion in days and a status (healthy, warning past 50 percent, critical past 90, exhausted).
Common mistakes: hours_back defaults to 720 (30 days). Narrow scope with device_id/group_id for performance.
Inputs: group_id, device_id, hours_back, target_slo, +2 more. Returns: portal, api_total, by_device, device_id, +12 more
capacity_planARead-onlyIdempotent
Composite capacity planning: reads each instance once through analyze_metric to classify its trend, detect seasonality and change points, and forecast when it crosses threshold (default 90). Summary rows carry each forecast method's breach_eta (epoch seconds) and hours_until_breach per datapoint.
Inputs: device_id, threshold, datasource, hours_back, +2 more. Returns: portal, warnings, device_id, threshold, +5 more
clear_session_contextBIdempotent
Clear all session context (variables and history)
Inputs: no named parameters.
correlate_metricsARead-onlyIdempotent
Compute Pearson correlation between multiple metric series. Joins the series by timestamp bucket, as wide as the coarsest series' median sample interval with finer series averaged into it, and correlates over the buckets every series holds, reported as shared_samples. Builds an NxN correlation matrix and highlights strong correlations (|r| > 0.7). Maximum 10 sources.
Inputs: sources (required), hours_back. Returns: labels, portal, warnings, hours_back, +4 more
delete_session_variableAIdempotent
Delete a user-defined session variable
Inputs: name (required).
detect_site_outageARead-onlyIdempotent
Composite workflow for site outage detection. Chains CollectorDown detection, mass-interface-down burst analysis, UPS on-battery events, and downstream device silence into a single site-outage verdict with confidence score, scope, and affected device list. Designed to catch the class of site-outage that generic AIOps correlation misses. Pass a device group ID representing the site.
Inputs: group_id (required), hours_back, detail_level, window_seconds. Returns: scope, portal, signals, verdict, +11 more
diagnoseARead-onlyIdempotent
Composite diagnosis: given an alert, or a device's latest open critical alert, gathers the alert details, device context, alerts clustered and audit changes in the last four hours, blast radius, and the device's assigned DiagnosticSources with the latest results of the alert's diagnostic runs. correlated_alerts lists the five largest clusters of each type with ten alert ids each, and changes the ten change and spike pairs of highest confidence; cluster_count, by_type and total_correlated count them all. It reads those results and never runs a DiagnosticSource. It computes no health score or root cause; health_check reports each metric's z-score.
Inputs: alert_id, device_name, detail_level. Returns: alert, device, portal, changes, +6 more
get_access_groupARead-onlyIdempotent
Get details about a specific access group
Inputs: group_id (required).
get_access_groupsCRead-onlyIdempotent
List access groups
Inputs: limit, offset, name_filter.
get_action_chainARead-onlyIdempotent
Get details about a specific action chain including its stages
Inputs: chain_id (required).
get_action_chainsBRead-onlyIdempotent
List action chains: ordered DiagnosticSource/RemediationSource stages that action rules trigger on alerts (Automated Diagnostics & Remediation)
Inputs: limit, offset.
get_action_ruleARead-onlyIdempotent
Get details about a specific action rule
Inputs: rule_id (required).
get_action_rulesBRead-onlyIdempotent
List action rules: alert conditions (severity, device groups, datasource matchers) that trigger action chains
Inputs: limit, offset, name_filter.
get_active_sdtsBRead-onlyIdempotent
Get currently active SDTs
Inputs: limit, offset, device_id, device_group_id.
get_alert_detailsBRead-onlyIdempotent
Get detailed information about a specific alert
Inputs: alert_id (required), include_message.
get_alert_ruleCRead-onlyIdempotent
Get details about a specific alert rule
Inputs: rule_id (required), raw.
get_alert_rulesBRead-onlyIdempotent
List alert rules: each rule's priority and the escalation chain it routes matching alerts to
Inputs: limit, offset, name_filter, priority_filter.
get_alertsARead-onlyIdempotent
Get open or cleared alerts from LogicMonitor, optionally filtered by severity (critical, error, warning), device, group, datasource or time
For Kubernetes clusters, use group_id (from get_device_groups) instead of device; the device name filter does not work reliably for K8s resources.
Common mistakes: startEpoch/endEpoch use SECONDS not milliseconds. String filter values need double quotes (e.g., monitorObjectName:"hostname").
Inputs: acked, limit, sdted, device, +12 more.
get_alert_settingsARead-onlyIdempotent
Read datapoint alert thresholds at instance, device or group level: each datapoint's threshold in force and the level it comes from (instance, instance_group, device_datasource, device_group with source_group, group or global), beside the level's own and the global threshold. Use it before tuning a noisy threshold with update_alert_settings.
Inputs: level (required), limit, offset, group_id, +5 more.
get_api_tokenBRead-onlyIdempotent
Get details about a specific API token
Inputs: token_id (required), admin_id.
get_api_tokensCRead-onlyIdempotent
List API tokens
Inputs: limit, offset, admin_id.
get_apm_service_alertsBRead-onlyIdempotent
Get the alerts on one APM trace service, one page at a time
Inputs: service_id (required), limit, offset, severity.
get_apm_servicesARead-onlyIdempotent
List APM trace services, the deviceType 6 devices, one page at a time. Entry point for discovering traced services; read a service's datasources, operations (the instances of its operations datasource), metrics and properties with get_device_datasources, get_device_instances, get_device_data and get_device_properties, passing the service id as device_id.
Inputs: limit, offset, name_filter.
get_audit_logsARead-onlyIdempotent
Read the portal audit log: call this for who did what and when. kind='all' returns one page of entries, newest first; kind='change' returns the configuration changes (create, update, delete or import, read from each entry's description) found in a pool of the newest entries, with scanned and has_more; kind='login' returns portal sign-ins, sign-outs and failed logins, one query per login wording (up to six calls), with status and method per row, success_only or failed_only, and total as a lower bound while has_more is true; kind='api_token' returns the rows naming an API token, given by access_id or token_id (read to its access ID), keeping only that exact access ID, with event (change, rejected, throttled), path and method per row. username is an exact name or a comma-separated list; action and resource_type (kinds all and change) are whole words the description holds (the portal applies one, the second is matched on the fetched page); start_time and end_time bound the entry time in epoch seconds. System and automation actors (System:*, LogicMonitor Internal, cloud auto-delete) are dropped after the fetch for kinds all and change unless exclude_system is false or a username is given; dropped counts them and paging follows the rows the portal returned. An argument another kind reads is refused. offset plus the rows read must stay within 10,000, and the filter within about 900 characters.
Inputs: kind, limit, action, offset, +10 more.
get_batchjobARead-onlyIdempotent
Get details about a specific batch job
Inputs: batchjob_id (required).
get_batchjobsCRead-onlyIdempotent
List batch jobs
Inputs: limit, offset, status, name_filter.
get_collectorARead-onlyIdempotent
Get detailed information about a specific collector
Inputs: collector_id (required).
get_collector_eventsARead-onlyIdempotent
List one collector's events, newest first: agent and sbproxy restarts, credential rotation, and reports that the collector is unreachable, each with its time and build. Use it for a collector's recent history; get_collector_health gives its current state.
Inputs: collector_id (required), limit, offset.
get_collector_groupARead-onlyIdempotent
Get details about a specific collector group
Inputs: group_id (required).
get_collector_groupsBRead-onlyIdempotent
List collector groups
Inputs: limit, filter, offset, name_filter.
get_collector_healthARead-onlyIdempotent
Enriched collector status: whether each collector is down, downstream device count, uptime, and optional alert history. Leading indicator for site-level events. Prefer this over get_collectors when investigating potential outages. The collector asked for by collector_id, and each collector not known to be up, carries evidence: its latest status check and its five latest events.
Inputs: collector_id, history_days, include_history, collector_group_id.
get_collector_log_fileARead-onlyIdempotent
Read one uploaded collector log file, named as get_collector_log_files lists it, and return the end of its text: at most max_bytes bytes, starting on a whole line. truncated says whether earlier lines were left out.
Inputs: file_name (required), collector_id (required), max_bytes.
get_collector_log_filesARead-onlyIdempotent
List the log files a collector has uploaded to the portal, as zip files with their size and upload time. A collector uploads them through Send Logs to LogicMonitor in the portal or the !uploadlog debug command, so an empty list means nothing was uploaded. Read one with get_collector_log_file.
Inputs: collector_id (required), limit, offset.
get_collectorsCRead-onlyIdempotent
List collectors from LogicMonitor
Inputs: limit, filter, offset, hostname_filter, +1 more.
get_collector_upgrade_historyARead-onlyIdempotent
List the portal's collector version upgrades a page at a time (limit, offset), each row as the API returns it.
Inputs: limit, offset.
get_configsourceCRead-onlyIdempotent
Get details about a specific ConfigSource
Inputs: configsource_id (required), raw.
get_configsourcesCRead-onlyIdempotent
List ConfigSources
Inputs: limit, filter, offset, name_filter, +1 more.
get_configsource_update_reasonsBRead-onlyIdempotent
Get update history and audit trail for a ConfigSource
Inputs: configsource_id (required), limit, offset.
get_cost_recommendationARead-onlyIdempotent
Get a specific cost recommendation by ID (v224 API)
Inputs: recommendation_id (required).
get_cost_recommendation_categoriesARead-onlyIdempotent
Get cost recommendation categories with counts and savings
Inputs: no named parameters.
get_cost_recommendationsBRead-onlyIdempotent
Get cost optimization recommendations. Category filter takes the category description string from get_cost_recommendation_categories
Inputs: limit, offset, status, category.
get_dashboardCRead-onlyIdempotent
Get detailed information about a specific dashboard
Inputs: dashboard_id (required), raw.
get_dashboard_groupBRead-onlyIdempotent
Get details about a specific dashboard group
Inputs: group_id (required).
get_dashboard_groupsCRead-onlyIdempotent
List dashboard groups
Inputs: limit, offset, name_filter.
get_dashboardsBRead-onlyIdempotent
List dashboards from LogicMonitor
Inputs: limit, filter, offset, group_id, +1 more.
get_dashboard_widgetsBRead-onlyIdempotent
Get widgets configured on a dashboard
Inputs: dashboard_id (required), limit, offset.
get_datasourceCRead-onlyIdempotent
Get details about a specific datasource
Inputs: datasource_id (required), raw.
get_datasource_devicesARead-onlyIdempotent
List the devices/resources a datasource applies to, each with up to 10 of its instances; more_instances says it has others, which get_device_instances lists.
Inputs: datasource_id (required), limit, offset, name_filter.
get_datasourcesCRead-onlyIdempotent
List datasources from LogicMonitor
Inputs: limit, filter, offset, name_filter, +1 more.
get_deviceBRead-onlyIdempotent
Get detailed information about a specific device (resource)
Inputs: device_id (required).
get_device_batchjobsARead-onlyIdempotent
List BatchJob datasources applied to a device (resource); per-run output lives in instance data via get_device_data
Inputs: device_id (required), limit, offset.
get_device_configBRead-onlyIdempotent
List config versions collected for a device instance
Inputs: device_id (required), instance_id (required), device_datasource_id (required), limit, +1 more.
get_device_config_versionARead-onlyIdempotent
Get a specific config version with full content and diffs
Inputs: config_id (required), device_id (required), instance_id (required), device_datasource_id (required), +1 more.
get_device_connectionsCRead-onlyIdempotent
Get device/resource relationships and connections
Inputs: device_id (required).
get_device_dataARead-onlyIdempotent
Get the raw metric values (samples) of a device/resource datasource instance, such as CPU, memory or disk usage
Common mistakes: Returns the last hour unless start_time or end_time is given. Requires device_datasource_id (from get_device_datasources) not the datasource definition ID.
Inputs: device_id (required), instance_id (required), device_datasource_id (required), end_time, +2 more.
get_device_datasourcesARead-onlyIdempotent
Get datasources applied to a device (resource)
Common mistakes: Returns device-datasource associations not definitions. The ID returned here is device_datasource_id for use with get_device_data.
Inputs: device_id (required), limit, offset, name_filter.
get_device_deltaARead-onlyIdempotent
List devices/resources through the device delta, to follow what changed. Without delta_id it lists the devices whose display name contains name_filter, or every device, and returns a delta_id; each such read starts a new delta, so keep the first page's. With delta_id it lists the devices changed since that delta started (change says how), every change since then on each read. name_filter is refused there, since the portal answered a filtered read with an empty page that left out a changed device.
Inputs: limit, offset, delta_id, name_filter.
get_device_eventsourcesBRead-onlyIdempotent
Get EventSources applied to a device (resource). Returns device-level EventSource associations.
Inputs: device_id (required), limit, offset.
get_device_flowsARead-onlyIdempotent
List a NetFlow exporter device's flow records over the last hours_back hours, rows as the API returns them; the API reference gives each flow its source and destination IP, port, DNS name and ASN, its protocol and its bytes. Answers FEATURE_DISABLED when the portal has NetFlow off for the device.
Inputs: device_id (required), limit, offset, hours_back.
get_device_groupARead-onlyIdempotent
Get detailed information about a specific device/resource group, including appliesTo expression and parent ID
Inputs: group_id (required).
get_device_group_propertiesARead-onlyIdempotent
Get a device group's (resource group's) properties: its own, the ones it inherits and the system ones, each with the value in force, its type (custom, inherit or system) and the ancestor groups that hold the same name, nearest first; an inherited value is the nearest one's. property_name reads one property.
Inputs: group_id (required), limit, offset, name_filter, +1 more.
get_device_groupsCRead-onlyIdempotent
List device/resource groups from LogicMonitor
Inputs: limit, offset, parent_id, name_filter.
get_device_instancesCRead-onlyIdempotent
Get instances of a datasource on a device (resource)
Inputs: device_id (required), device_datasource_id (required), limit, offset, +1 more.
get_device_interfacesCRead-onlyIdempotent
Get network interfaces for a device (resource)
Inputs: device_id (required), limit, offset.
get_device_logsourcesCRead-onlyIdempotent
Get LogSources applied to a device (resource)
Inputs: device_id (required), limit, offset.
get_device_neighborsBRead-onlyIdempotent
Get neighboring devices/resources based on topology
Inputs: device_id (required), depth.
get_device_propertiesARead-onlyIdempotent
Get all properties of a device (resource). Each has its value, its type (custom, inherit, auto or system) and sources: the groups and property rules the portal lists for that name, with the value each holds.
Inputs: device_id (required), limit, offset, name_filter.
get_device_propertyARead-onlyIdempotent
Get a specific property of a device (resource): its value, its type (custom, inherit, auto or system) and sources, the groups and property rules the portal lists for that name, with the value each holds.
Inputs: device_id (required), property_name (required).
get_devicesBRead-onlyIdempotent
List devices (resources) from LogicMonitor, optionally filtered by name, hostname, status or device group
Inputs: limit, filter, offset, status, +3 more.
get_device_top_talkersARead-onlyIdempotent
A NetFlow exporter device's top talkers over the last hours_back hours, for 'what is consuming my WAN?': by=endpoint pages the endpoints it saw and by=port the ports, rows as the API returns them (the API reference gives each a usage and a share); by=graph returns its top talkers graph whole. Answers FEATURE_DISABLED when the portal has NetFlow off for the device.
Inputs: device_id (required), by, limit, offset, +1 more.
get_diagnostic_remediation_assignmentsARead-onlyIdempotent
List the diagnostic and remediation sources assigned to a specific resource or alert (Automated Diagnostics & Remediation). Unlike get_diagnosticsources/get_remediationsources, this resolves which modules actually apply to the target.
Inputs: limit, alert_id, module_type, resource_id.
get_diagnostic_remediation_resultsARead-onlyIdempotent
Get structured execution results for diagnostic and remediation source runs: status, trigger type, executor, script output, and timing. Provide exactly one of alert_id or host_id. Time window params are epoch milliseconds; result timestamps are epoch seconds.
Inputs: limit, cursor, offset, host_id, +9 more.
get_diagnosticsourceBRead-onlyIdempotent
Get details about a specific DiagnosticSource including datapoints
Inputs: source_id (required), raw.
get_diagnosticsourcesBRead-onlyIdempotent
List DiagnosticSources from LogicMonitor
Inputs: limit, filter, offset, name_filter, +1 more.
get_escalation_chainCRead-onlyIdempotent
Get details about a specific escalation chain
Inputs: chain_id (required), raw.
get_escalation_chainsCRead-onlyIdempotent
List escalation chains
Inputs: limit, offset, name_filter.
get_eventsourceCRead-onlyIdempotent
Get details about a specific EventSource
Inputs: eventsource_id (required), raw.
get_eventsourcesBRead-onlyIdempotent
List EventSources
Inputs: limit, filter, offset, name_filter, +1 more.
get_graph_dataCRead-onlyIdempotent
Get graph image data for visualization
Inputs: graph_id (required), device_id (required), instance_id (required), device_datasource_id (required), +2 more.
get_integrationARead-onlyIdempotent
Get a specific integration's full definition. Field set depends on integration type; password/OAuth secret fields are masked.
Inputs: integration_id (required).
get_integrationsARead-onlyIdempotent
List LogicMonitor integrations (Custom HTTP Delivery, Slack, PagerDuty, etc.). Returns a short summary per integration.
Inputs: limit, offset, name_filter, type_filter.
get_interface_metricsARead-onlyIdempotent
Pull interface-level metrics (in/out bytes, errors, discards, utilization, status) for a device's interface over a time window. Answers 'how is this port performing?' Resolves the Interface-family DataSource and the instance matching the interface name before fetching datapoints.
Inputs: device_id (required), interface (required), metrics, hours_back.
get_link_flapsARead-onlyIdempotent
Identify interfaces with repeated up/down transitions in a time window. Answers 'which ports are unstable?' Common causes: bad cable, duplex mismatch, bad SFP, PoE power cycling, WAN instability.
Inputs: device, group_id, hours_back, min_transitions, +1 more.
get_log_partitionsARead-onlyIdempotent
List the LM Logs partitions with whether each is active or paused, its criteria, and its active contract (state, SKU, retention, usage limit, period). Use it to check partition state and contract limits.
Inputs: limit, offset.
get_log_pipelinesARead-onlyIdempotent
List every LM Logs pipeline with its log query and the partitions it names. It returns all pipelines at once and takes no arguments. It does not search log content.
Inputs: no named parameters.
get_log_query_groupsBRead-onlyIdempotent
List the saved LM Logs query groups (folders) with their type, owner, permission and the queries each holds.
Inputs: limit, offset.
get_logsourceCRead-onlyIdempotent
Get details about a specific LogSource
Inputs: logsource_id (required), raw.
get_logsourcesCRead-onlyIdempotent
List LogSources
Inputs: limit, filter, offset, name_filter, +1 more.
get_log_usageARead-onlyIdempotent
Read the portal's LM Logs usage figure from /log/usage: one number, as returned. The API states no unit or period for it.
Inputs: no named parameters.
get_netscanBRead-onlyIdempotent
Get details about a specific network scan
Inputs: netscan_id (required).
get_netscansCRead-onlyIdempotent
List network scans
Inputs: limit, offset, name_filter.
get_oidCRead-onlyIdempotent
Get details about a specific OID
Inputs: oid_id (required).
get_oidsCRead-onlyIdempotent
List OID definitions
Inputs: limit, offset, oid_filter.
get_ops_noteCRead-onlyIdempotent
Get details about a specific ops note
Inputs: note_id (required).
get_ops_notesCRead-onlyIdempotent
List ops notes
Inputs: limit, offset, tag_filter.
get_otlp_label_valuesARead-onlyIdempotent
List the values observed for one native OTLP metric label, such as every service_name, optionally narrowed to one metric
Inputs: key (required), end, limit, start, +1 more.
get_otlp_metric_labelsARead-onlyIdempotent
List the label names on native OTLP metrics, optionally narrowed to one metric or to names containing a substring
Inputs: end, limit, start, metric, +1 more.
get_otlp_metric_namesARead-onlyIdempotent
List the names of metrics ingested through native OpenTelemetry (OTLP), optionally those containing a substring, to find what to query with query_otlp_metrics or analyze_metric(source="otlp"). A portal without OTLP Metrics answers with available: false
Inputs: end, limit, start, contains.
get_power_eventsARead-onlyIdempotent
Filter alerts for UPS/PDU power-event signatures across APC, Liebert, and Eaton DataSources ('on battery', 'runtime remaining', 'input voltage lost') over a time window. Returns events matched by DataSource or alert name substring with counts per pattern.
Inputs: device, group_id, patterns, severity, +1 more.
get_propertysourceCRead-onlyIdempotent
Get details about a specific PropertySource
Inputs: propertysource_id (required), raw.
get_propertysourcesCRead-onlyIdempotent
List PropertySources
Inputs: limit, filter, offset, name_filter, +1 more.
get_recipient_groupBRead-onlyIdempotent
Get details about a specific recipient group
Inputs: group_id (required).
get_recipient_groupsCRead-onlyIdempotent
List recipient groups
Inputs: limit, detail, offset, name_filter.
get_referenceARead-onlyIdempotent
Get LogicMonitor reference content (schemas, enums, filter syntax, guides). Mirrors content from MCP Resources for clients without full Resource support (Copilot cloud agent, OpenAI Codex, Cline). Categories: schema, enums, filters, syntax, guide. Pass list=true (or omit both category and name) to discover all available (category, name) pairs.
Inputs: list, name, category.
get_remediationsourceARead-onlyIdempotent
Get details about a specific RemediationSource including the Groovy script
Inputs: source_id (required), raw.
get_remediationsourcesCRead-onlyIdempotent
List RemediationSources from LogicMonitor
Inputs: limit, filter, offset, name_filter, +1 more.
get_reportBRead-onlyIdempotent
Get detailed information about a specific report
Inputs: report_id (required).
get_report_executionARead-onlyIdempotent
Poll the status of a report generation task started by run_report (returns status and result URL when finished)
Inputs: task_id (required), report_id (required).
get_report_groupsCRead-onlyIdempotent
List report groups
Inputs: limit, offset, name_filter.
get_reportsCRead-onlyIdempotent
List reports from LogicMonitor
Inputs: limit, filter, offset, group_id, +3 more.
get_roleARead-onlyIdempotent
Get details about a specific role
Inputs: role_id (required).
get_rolesBRead-onlyIdempotent
List roles
Inputs: limit, filter, offset, name_filter.
get_scheduled_downtime_jobsCRead-onlyIdempotent
Get batch jobs related to SDT automation
Inputs: limit, offset.
get_scheduled_reportsBRead-onlyIdempotent
Get reports with schedules configured
Inputs: limit, offset, enabled_only, include_nextgen.
get_sdtsCRead-onlyIdempotent
List scheduled downtimes from LogicMonitor
Inputs: admin, limit, filter, offset, +3 more.
get_serviceARead-onlyIdempotent
Get details about a specific Service Insight service
Inputs: service_id (required).
get_service_groupsBRead-onlyIdempotent
List Service Insight service groups (BizService device groups)
Inputs: limit, offset, name_filter.
get_service_insights_rulesARead-onlyIdempotent
List the portal's Service Insights rules, rows as the API returns them. offset must be a multiple of limit; the portal answers any other offset with a 400. get_services lists the services themselves.
Inputs: limit, offset.
get_servicesBRead-onlyIdempotent
List Service Insight business services (deviceType 6 devices, including APM trace services)
Inputs: limit, offset, name_filter.
get_session_contextBRead-onlyIdempotent
Get current session context (variables and history)
Inputs: no named parameters.
get_session_historyCRead-onlyIdempotent
List recent tool call history
Inputs: limit.
get_session_variableBRead-onlyIdempotent
Get a user-defined session variable
Inputs: name (required).
get_tenantsARead-onlyIdempotent
List the portal's tenant names, as the tenants API answers them: names only, with no paging or detail.
Inputs: no named parameters.
get_terraform_importsARead-onlyIdempotent
List a resource type's portal objects as Terraform import blocks for the logicmonitor/logicmonitor provider, one import { to, id } block per object, for 15 of the provider resource types that import by ID; cluster alert confs are left out, since the API refuses the read the provider's importer makes. Run terraform init, then terraform plan -generate-config-out=generated.tf on the blocks to have Terraform write the resource configuration. The provider authenticates with LMv1 api_id and api_key only.
Inputs: resource_type (required), limit, filter, offset.
get_topology_mapCRead-onlyIdempotent
Get network topology map data
Inputs: limit, offset, include_connections.
get_topologysourceCRead-onlyIdempotent
Get details about a specific TopologySource
Inputs: topologysource_id (required), raw.
get_topologysourcesCRead-onlyIdempotent
List TopologySources
Inputs: limit, filter, offset, name_filter, +1 more.
get_tracked_log_queriesARead-onlyIdempotent
List the portal's tracked log queries, each row as the API returns it. Use it to see which log queries the portal tracks; it does not run them.
Inputs: limit, offset.
get_unmonitored_devicesBRead-onlyIdempotent
List the portal's unmonitored devices/resources, found by a NetScan and not monitored, rows as the API returns them.
Inputs: limit, offset.
get_upcoming_sdtsARead-onlyIdempotent
Get SDTs scheduled to start within a time window
Inputs: limit, offset, hours_ahead.
get_usage_contractARead-onlyIdempotent
Read the portal's contracted entitlements, for license and contract questions: every feature the contract names, entitled or not, each with its role (billable_line, metered_no_entitlement, metered_unpaid, repeats_parent, rollup_or_carveout), entitled quantity, unit and roll-up basis, plus the detected billing_mode. It does not count the portal's current resources.
Inputs: billable_only.
get_usage_metricsARead-onlyIdempotent
Read how many devices, Kubernetes, AWS, Azure and GCP resources, websites and services the portal holds now, as point-in-time counts. The portal is billed on each feature's roll-up basis in the contract, so these are not billed figures.
Inputs: no named parameters.
get_userARead-onlyIdempotent
Get details about a specific user
Inputs: user_id (required).
get_usersARead-onlyIdempotent
List users from LogicMonitor
Inputs: limit, filter, offset, name_filter.
get_websiteBRead-onlyIdempotent
Get detailed information about a specific website
Inputs: website_id (required).
get_website_checkpointsARead-onlyIdempotent
List the portal's website checkpoint locations, the places website checks run from; each id is the smg_id a website's checkpoints carry in get_website.
Inputs: limit, offset.
get_website_dataCRead-onlyIdempotent
Get synthetic check data for a website
Inputs: website_id (required), checkpoint_id (required), end_time, start_time.
get_website_groupsCRead-onlyIdempotent
List website groups
Inputs: limit, offset, parent_id, name_filter.
get_websitesCRead-onlyIdempotent
List websites from LogicMonitor
Inputs: limit, filter, offset, group_id, +1 more.
get_widgetBRead-onlyIdempotent
Get details about a specific widget
Inputs: widget_id (required), dashboard_id (required).
health_checkARead-onlyIdempotent
Composite health check: resolves a device, picks up to five of its datasources whose names mention CPU, memory or disk (drive, volume, filesystem), reads the first instance of each through analyze_metric (summary and anomalies over 24 hours), checks open alerts, and calculates 30-day availability. A device with none of those datasources gets an empty metrics list and a warning.
Inputs: device_id, device_name, detail_level. Returns: portal, metrics, warnings, device_id, +5 more
portal_overviewARead-onlyIdempotent
Shift-handoff overview of the portal: reads the alert window of the last hours_back hours once for statistics, clusters and noise, and lists the collectors and the active SDTs. alert_clusters lists the five largest clusters of each type with ten alert ids each, and its cluster_count and by_type count them all. detail_level=full adds up to 20 open critical and 20 open error alerts from across the portal, not only the window, and up to 20 dead devices; summary does not read them.
Inputs: hours_back, detail_level. Returns: noise, portal, warnings, collectors, +8 more
query_otlp_metricsARead-onlyIdempotent
Run a PromQL query against native OTLP metrics. A range query (start and end in epoch seconds, optional step) returns each series' samples over the window; instant=true returns each series' value now and takes no window. Returns at most 20 series and 500 points a series, downsampled; for statistics on a series use analyze_metric(source="otlp")
Inputs: query (required), end, step, start, +1 more.
search_toolsARead-onlyIdempotent
Search the tools this server offers under its current settings by keyword, optionally within one category. Use it to find the tool for a task. It never names a tool the settings hide, so with writes off no write tool appears. Words such as 'the' and 'on' are ignored, plurals match singulars, and a query word that is a tool's full name ranks that tool first.
Inputs: query (required), limit, category.
set_session_variableAIdempotent
Set a user-defined session variable for use across tool calls
Inputs: name (required), value (required).
triageARead-onlyIdempotent
Triage the alerts of the last hours_back hours in one call. Reads the alert window once through analyze_alerts for its statistics, clusters (by device, datasource and signature), noise and changes, then counts the blast radius of up to three device clusters, largest first. Each count row gives the devices reached as neighbors and as dependents, how many of them have a critical alert open, and how many devices' neighbors could not be read; a website cluster gets none. The clusters section lists the five largest clusters of each type with ten alert ids each, and changes the ten change and spike pairs of highest confidence; cluster_count, by_type and total_correlated count them all, and a narrower severity, device or window shows the rest. detail_level=full adds the devices each blast radius reached. Use analyze_alerts for bursts or a single section, and analyze_blast_radius for one device.
Inputs: device, group_id, severity, hours_back, +1 more. Returns: noise, portal, changes, clusters, +5 more
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
TDQS
Scored across 150 tools
Most list/detail pairs are clearly named and many composite tools have detailed descriptions explaining their boundaries. However, with 150 tools there is substantial overlap between alert-related tools (get_alerts, analyze_alerts, triage, diagnose, portal_overview), collector tools (get_collectors, get_collector_health), and service tools (get_services, get_apm_services), making tool selection difficult despite the descriptions.
The dominant pattern is get_<resource> for retrieval, with fairly consistent singular/plural distinctions. But the set also mixes analyze_*, calculate_*, query_*, search_tools, set/delete/clear session verbs, and standalone noun-like names such as triage, diagnose, health_check, capacity_plan, and portal_overview, so conventions are only partially consistent.
150 tools is an extreme surface for a single MCP server, far beyond typical limits and likely to overwhelm an agent's context and decision-making. Many tools are narrow variants or composite shortcuts that could be consolidated.
The read/investigation surface is very broad, covering devices, alerts, collectors, datasources, metrics, logs, topology, NetFlow, cost, and governance. However, obvious dead ends exist: get_report_execution polls a task started by run_report, but run_report is not listed, and get_alert_settings references update_alert_settings, which is also absent. Core write/update operations are largely missing outside session variables.
Maintenance
Related MCP Connectors
Lets AI agents analyze API metrics, request logs, and traces, and manage apps and alerts.
Connect your AI agent to 300+ methods and 100+ live tools
Manage uptime monitors and incidents and search logs, metrics and traces from an AI assistant.
Governed app access for AI agents: 1,000+ apps & 12,000+ tools via Code Mode MCP.
Related MCP Servers
- AlicenseAqualityDmaintenanceMCP server enabling AI assistants to interact with your LogicMonitor, providing 125 tools for comprehensive monitoring and management operations.7090 npm14AGPL 3.0
- AlicenseNot gradedqualityCmaintenanceEnables AI assistants and automation tools to manage Microsoft 365, Entra ID, and Intune resources through 32 tools for user/device/file management and infrastructure monitoring.8MIT
- AlicenseNot gradedqualityDmaintenanceProvides secure access to the LogicMonitor API, enabling AI assistants to manage monitoring infrastructure through natural language commands.25 npm7Mozilla Public 2.0
- AlicenseNot gradedqualityDmaintenanceEnables AI assistants to interact with the Databricks platform through 263 tools and 8 prompt templates, covering Unity Catalog, SQL, Compute, Jobs, Pipelines, and more.Apache 2.0