Name: Xitoring MCP
Author: xitoring

LABSCO SUMMARY

Monitoring data you can question, with the dashboard buttons attached.

The read side turns a fleet into something you can interrogate — rank servers by disk usage, pull the notes off the last three incidents, generate a month of uptime. The write tools make the same key able to resolve an incident or pause a server, so point it at a client that asks for approval before running a tool, and issue a dedicated key so the activity is easy to trace.

What it is

A hosted endpoint over your Xitoring monitoring account — servers, uptime and SSL checks, incidents, metrics, status pages and reports — with over 60 tools spanning reads, reports and a curated set of write actions.

What you get

Live and historical metrics per server — CPU, load average, memory, disk usage, disk IO, network — and the top processes on any host
Every check type listed and inspected, with response time, overall uptime and average latency across regions
Ongoing and historical incidents, their notes, and the trigger and notification-role routing behind them
Uptime and SSL uptime reports, subscription details and ticket lists
Account, Xitogent and notification history for troubleshooting and compliance
Write actions: resolve incidents, add notes, send test notifications, pause and unpause checks or servers, create HTTP, ping, SSL and heartbeat checks, schedule maintenance windows, open tickets and invite contacts

Requirements

A Xitoring account with at least one server, uptime check or integration configured, plus an API key generated under Dashboard → Account → API Access. The key travels as an Authorization bearer header to the streamable HTTP endpoint; clients that only speak stdio bridge through mcp-remote.

Setup effort

Paste a URL with a key — add the endpoint to your client

See installation options

USE CASES

01

Reconstructing what happened during an outage

Pull the incident, its notes and the notification history into one timeline, then draft the post-mortem from it.

02

Finding the server that is about to run out of room

Rank the fleet by disk usage and CPU, then drill into the top processes on whichever host stands out.

03

Producing the monthly uptime number

Generate overall uptime, per-check reports, average latency and SSL uptime without leaving the conversation.

04

Quieting alerts around a deploy

Pause the affected checks and servers before the release, then unpause them once it lands.

BEFORE YOU INSTALL

What to know first

Requires

A client that can reach a remote MCP server over HTTP

INSTALLATION

Connect your client

Add the endpoint to your client.

Server setup

ENDPOINT URL

https://app.xitoring.com/mcp

MCP Clients

Claude Code

CLAUDE CODE · TERMINAL

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

Cursor

CURSOR · JSON

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

VS Code

VS CODE · JSON

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

Any MCP client — mcp-remote

ANY MCP CLIENT — MCP-REMOTE · JSON

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

Xitoring MCP