Xitoring

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 YOUR_API_KEY 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/claude_desktop_config.json
• Windows: %APPDATA%\Claude\claude_desktop_config.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:

{
  "mcpServers": {
    "xitoring": {
      "command": "npx",
      "args": [
        "mcp-remote",
        "https://app.xitoring.com/mcp",
        "--header",
        "Authorization: Bearer YOUR_API_KEY"
      ]
    }
  }
}

Verifying the Connection

1. Restart your MCP client.
2. Open the tool / server picker - you should see xitoring listed with its tools.
3. Try the prompt: "List my Xitoring servers and their current status."

If you get a response that names your real servers, you're connected.

Example Prompts

Status & Triage

• "What incidents are ongoing right now, and which servers or checks are affected?"
• "Show me the current status of all my servers - flag anything that isn't reporting."
• "Are there any maintenance windows active or starting in the next 24 hours?"

Performance & Capacity

• "Which 5 servers have the highest CPU usage right now?"
• "Show me the top processes by memory on web-prod-01."
• "Rank my servers by disk usage and tell me which ones are above 80% full."

Uptime & SLA

• "What's the overall uptime for my checks over the last 30 days?"
• "Which SSL certificates are expiring in the next 30 days?"
• "Pull the uptime report for api.example.com for last month."

Incident Response

• "Summarize the last 3 resolved incidents on db-01 and read me their notes."
• "Draft a post-mortem from the timeline of incident #1234."
• "Add a note to the active incident: 'rolling back deploy v2.41, monitoring recovery.'"

Maintenance & Ops

• "Create a 2-hour maintenance schedule for web-prod-01 starting tomorrow at 02:00 UTC."
• "Pause the uptime check for staging.example.com while we redeploy."
• "Create an HTTP check for https://api.example.com/health that runs every minute from EU regions."

Security & Privacy

• All traffic to https://app.xitoring.com/mcp is encrypted over HTTPS.
• Authentication is a Xitoring API key passed as Authorization: Bearer .... Revoking the key in the Xitoring dashboard immediately cuts off MCP access.
• Rotate keys every 90 days for production accounts, and immediately if a key is exposed.
• Be aware: AI clients send conversation context (including tool results) to their model providers. Only data you explicitly request via MCP tools is read from Xitoring, but those results then become part of the conversation the model provider sees.

Troubleshooting

Links

• Full documentation: xitoring.com/docs/mcp
• Generate an API key: xitoring.com/docs/account/api
• Model Context Protocol: modelcontextprotocol.io

Status

The Xitoring MCP server is currently in beta. Tool names and response shapes may change before 1.0. Feedback and bug reports via GitHub issues are very welcome.

License

MIT