Overview
What is Xitoring Mcp?
Xitoring Mcp is a hosted, remote HTTP server that connects AI assistants (like Claude, Cursor, and ChatGPT) to Xitoring monitoring data. It exposes 60+ tools for inspecting servers, uptime checks, incidents, status pages, and more, with no local installation required.
How to use Xitoring Mcp?
Configure your MCP-compatible client with the endpoint https://app.xitoring.com/mcp and pass your Xitoring API key as an Authorization: Bearer header. Setup examples are provided for Claude Code CLI, Claude Desktop, Cursor, VS Code with Copilot, and stdio clients via the mcp-remote bridge.
Key features of Xitoring Mcp
- 60+ tools for monitoring data inspection and write actions
- Read and write incidents, status pages, maintenance windows
- Fetch live and historical server metrics (CPU, memory, disk, network)
- List top processes and system info for servers
- Inspect uptime, SSL expiry, and heartbeat checks
- Account-level audit logs and notification delivery history
Use cases of Xitoring Mcp
- Triage ongoing incidents and affected servers or checks
- Check top CPU/memory servers for capacity planning
- Retrieve uptime reports and expiring SSL certificates
- Draft post-mortems and add notes during incident response
- Create maintenance windows and pause checks during deployments
FAQ from Xitoring Mcp
What do I need to use Xitoring Mcp?
A Xitoring account (free tier works), an API key generated from Dashboard > Account > API Access, and an MCP-compatible client such as Claude Desktop, Cursor, or VS Code.
Is Xitoring Mcp installed locally?
No, it is a hosted remote HTTP server at https://app.xitoring.com/mcp. There is nothing to install or run locally.
How is my data secured?
All traffic is HTTPS. Authentication uses a Bearer token (API key). Revoking the key in the Xitoring dashboard immediately cuts off MCP access. You should rotate keys every 90 days.
Are there rate limits?
Yes, MCP shares Xitoring's REST API rate limits. Excessive requests may result in 429 Too Many Requests errors.
What if the server returns 401 Unauthorized?
Check that the API key is correct, not revoked, and the header is exactly Authorization: Bearer YOUR_API_KEY with no extra quotes or typos.
