Xitoring MCP MCP server

The Xitoring MCP server enables AI assistants to interact with Xitoring's monitoring infrastructure. It exposes over 60 tools allowing agents to inspect servers, query live and historical metrics (CPU, memory, disk), check uptime and SSL status, search incidents, view status pages, and perform write actions like resolving incidents or creating checks. It supports HTTP transport with Bearer token authentication using an Xitoring API key.

Endpoint and access

OAuth sign-in: the first time you connect, your client opens the vendor's own authorization prompt in a browser.

OAuth sign-inEndpoint checked 2026-10-05Operated by Xitoring

MCP endpoint (Streamable HTTP)

https://app.xitoring.com/mcp

Vendor documentation

What you can do with it

Inspect individual servers and query live metrics like CPU and memory usage
Search ongoing and historical incidents to investigate outages
Generate uptime and SSL uptime reports for infrastructure health
Resolve incidents and add incident notes via AI assistant

Connect from your client

Each snippet registers the same endpoint; pick the client you use.

This server is operated by the named third party. Listing and endpoint checks are not an endorsement or a security audit. Review the operator's permissions, terms, and data handling before connecting. How listings are checked and corrected.

Claude Code

Run this once in a terminal. It registers a Streamable HTTP server. Use --scope project to write .mcp.json for the repo.

Claude Code configuration

claude mcp add --transport http xitoring-mcp https://app.xitoring.com/mcp

Codex

Run this once. Codex stores MCP servers in ~/.codex/config.toml (or .codex/config.toml in a trusted project).

Codex configuration

codex mcp add xitoring-mcp --url https://app.xitoring.com/mcp

Cursor

Merge this server into .cursor/mcp.json in your project, then enable xitoring-mcp in your MCP settings.

Cursor configuration

{
  "mcpServers": {
    "xitoring-mcp": {
      "url": "https://app.xitoring.com/mcp"
    }
  }
}

Cline

Merge this into cline_mcp_settings.json (Cline → MCP Servers → Configure). The type must be streamableHttp for a remote HTTP server.

Cline configuration

{
  "mcpServers": {
    "xitoring-mcp": {
      "type": "streamableHttp",
      "url": "https://app.xitoring.com/mcp",
      "disabled": false
    }
  }
}

VS Code

Merge this server into .vscode/mcp.json. Use MCP: List Servers to start xitoring-mcp and inspect its tools.

VS Code configuration

{
  "servers": {
    "xitoring-mcp": {
      "type": "http",
      "url": "https://app.xitoring.com/mcp"
    }
  }
}

Gemini CLI

Run this once. It writes .gemini/settings.json in the current project; pass --scope user for ~/.gemini/settings.json.

Gemini CLI configuration

gemini mcp add --transport http xitoring-mcp https://app.xitoring.com/mcp

Claude Desktop

Merge this into claude_desktop_config.json (macOS: ~/Library/Application Support/Claude/, Windows: %APPDATA%\Claude\), then restart Claude Desktop.

Claude Desktop configuration

{
  "mcpServers": {
    "xitoring-mcp": {
      "url": "https://app.xitoring.com/mcp"
    }
  }
}

Windsurf

Merge this into ~/.codeium/windsurf/mcp_config.json, then refresh MCP in Cascade. Windsurf remote servers use serverUrl, not url.

Windsurf configuration

{
  "mcpServers": {
    "xitoring-mcp": {
      "serverUrl": "https://app.xitoring.com/mcp"
    }
  }
}

See all 148

Do you run Xitoring MCP?

Prove ownership with a DNS record, a well-known file, or your Official MCP Registry entry, and your edits publish immediately. Proofs are re-checked weekly; admins can still hide or remove a listing.

Claim this listing