Xitoring MCP server

Xitoring MCP Server

Connect AI assistants like Claude, Cursor, and ChatGPT to your Xitoring monitoring data.

The Xitoring MCP server is a hosted, remote HTTP server - there is nothing to install or run locally. Point your MCP-compatible client at https://app.xitoring.com/mcp with your Xitoring API key and you're done.

What is Xitoring?

Xitoring is an all-in-one monitoring platform: uptime checks (HTTP, TCP, DNS, ICMP), server monitoring via the Xitogent agent (CPU, memory, disk, network, processes), SSL expiry, heartbeat checks, incident management, status pages, and notification routing. Teams use it to detect outages, triage performance regressions, track SLAs, and run on-call.

What the MCP Server Can Do

The server exposes 60+ tools across these areas:

Servers & Metrics

Inspect servers and Xitogent agents, fetch live and historical CPU / memory / disk / network metrics, list top processes, and pull system info.

Uptime, SSL & Heartbeat

List and inspect every check type (HTTP, HTTPS, TCP, DNS, ICMP, SSL, heartbeat). Get response time, latency, regional reachability, and uptime percentages.

Incidents & Alerting

Search and filter incidents, read incident timelines and notes, inspect triggers and notification routing, and follow incident state changes.

Status Pages & Maintenance

View status pages and the components they expose, list current and upcoming maintenance windows.

Reports & Account

Pull uptime and SSL reports, inspect subscription and quota usage, list and read support tickets.

Audit Logs

Account-level audit logs, Xitogent connection / installation logs, and notification delivery history.

Write Actions

Resolve incidents, add notes, pause / unpause checks, create new checks, schedule maintenance, send test notifications, invite contacts, and open support tickets.

Prerequisites

• A Xitoring account (free tier works for trying it out)
• A Xitoring API key - generate one at Dashboard > Account > API Access > Generate Key. Docs: xitoring.com/docs/account/api
• An MCP-compatible client (Claude Code, Claude Desktop, Cursor, VS Code with Copilot, etc.)

Setup

Pick the section that matches your client. In every example, replace YOURAPIKEY with the key you generated above.

Claude Code CLI (fastest)

claude mcp add --transport http --scope user xitoring \
  https://app.xitoring.com/mcp \
  --header "Authorization: Bearer YOUR_API_KEY"

Claude Desktop

Edit your config file:

• macOS: ~/Library/Application Support/Claude/claudedesktopconfig.json
• Windows: %APPDATA%\Claude\claudedesktopconfig.json

{
  "mcpServers": {
    "xitoring": {
      "type": "http",
      "url": "https://app.xitoring.com/mcp",
      "headers": {
        "Authorization": "Bearer YOUR_API_KEY"
      }
    }
  }
}

Restart Claude Desktop after saving.

Cursor

Settings > MCP > Add new MCP server, then paste:

{
  "mcpServers": {
    "xitoring": {
      "url": "https://app.xitoring.com/mcp",
      "headers": {
        "Authorization": "Bearer YOUR_API_KEY"
      }
    }
  }
}

VS Code (GitHub Copilot)

Create .vscode/mcp.json in your workspace:

{
  "servers": {
    "xitoring": {
      "type": "http",
      "url": "https://app.xitoring.com/mcp",
      "headers": {
        "Authorization": "Bearer YOUR_API_KEY"
      }
    }
  }
}

Stdio-only clients (via mcp-remote bridge)

If your client only supports stdio transport, bridge through mcp-remote:

Shortened. The full README is on GitHub.