Logicmonitor MCP

Created By
monitoringartist7 months ago
MCP Server for LogicMonitor
Overview

What is LogicMonitor MCP?

LogicMonitor MCP (Model Context Protocol) is a server designed to enable AI assistants to interact with LogicMonitor, providing a unified interface for monitoring and managing resources.

How to use LogicMonitor MCP?

To use LogicMonitor MCP, you can run it locally or remotely using Docker or Node.js. You need to set up your LogicMonitor company name and API bearer token for authentication.

Key features of LogicMonitor MCP?

  • 125 MCP Tools for comprehensive LogicMonitor operations (73 read-only, 52 write).
  • Unified Server supporting multiple transport modes (STDIO, SSE, HTTP).
  • Flexible Authentication options including bearer token and OAuth.
  • CSRF Protection for session-based authentication.
  • Debug Logging for detailed request/response tracking.
  • Batch Operations for efficient processing of multiple resources.

Use cases of LogicMonitor MCP?

  1. Integrating LogicMonitor with AI assistants for automated monitoring.
  2. Managing resources and alerts through a unified interface.
  3. Facilitating remote access to monitoring tools for multiple users.

FAQ from LogicMonitor MCP?

  • Can LogicMonitor MCP be used for all LogicMonitor operations?

Yes, it provides a wide range of tools for both read and write operations.

  • Is LogicMonitor MCP free to use?

The server itself is open-source, but you need a LogicMonitor account with API access.

  • How secure is LogicMonitor MCP?

It supports various authentication methods and can be configured to use HTTPS for secure connections.

Server Config

{
  "mcpServers": {
    "github": {
      "command": "docker",
      "args": [
        "run",
        "-i",
        "--rm",
        "-e",
        "LM_COMPANY",
        "-e",
        "LM_BEARER_TOKEN",
        "monitoringartist/logicmonitor-mcp-server"
      ],
      "env": {
        "LM_COMPANY": "<YOUR_LOGICMONITOR_COMPANY>",
        "LM_BEARER_TOKEN": "<YOUR_LOGICMONITOR_TOKEN>"
      }
    }
  }
}
Project Info
Created At
7 months ago
Updated At
7 months ago
Author Name
monitoringartist
Star
-
Language
-
License
-
Category
monitoring

Recommend Servers

View All
Bring your real authenticated browser session to AI coding agents. Local-first MCP server + Chrome MV3 extension. No cloud. No telemetry.
@Cubenest

peek records the user's actual logged-in browser (DOM via rrweb, console events, network metadata, optional response bodies via opt-in Deep capture) through a Chrome MV3 extension. The extension ships events through a native-messaging stdio bridge to a local MCP server (peek-mcp), which persists them to a SQLite database at ~/.peek/sessions.db. AI coding agents (Claude Code, Cursor, Cline, Windsurf) read sessions from the database via 10 MCP tools: Tool What it does list_recent_sessions List recently recorded sessions (id, origin, ts, event count). get_session_summary LLM-readable narrative summary of a session. get_session_console_errors Console errors recorded in a session. get_session_network_errors Failed/notable network requests in a session. get_user_action_before_error Last N user actions before a console error. generate_playwright_repro Generate a runnable Playwright test from a session. get_dom_snapshot Reconstruct the DOM at a given timestamp. query_dom_history Timeline of attribute/text changes for a selector. request_authorization Side-panel consent for write actions (Level 3). execute_action Dispatch a UI action (gated by permission level + destructive blocklist). Why local-first matters Every other "browser session for AI" tool ships to a vendor cloud. peek's SQLite + extension live on the user's machine — no remote endpoints, no telemetry. The privacy policy (docs/peek/PRIVACY_POLICY.md) is the source of truth. Install # 1. Add the MCP server to Claude Code claude mcp add peek -- npx -y @peekdev/mcp # 2. Install the Chrome extension from the Chrome Web Store # (link added once the CWS listing is approved)

2 days ago