MCP Integration

The Model Context Protocol (MCP) server exposes Hyperping's monitoring data and controls to AI agents over HTTP. Works with any MCP-compatible client: Claude Desktop, Claude Code, Cursor, Windsurf, mcp-inspector, or custom clients built on the MCP SDK.

Endpoint

Quick start

1. Create an API key

   Go to Project Settings → API Keys and create a read_only or read_write key. Keys are strictly scoped to one project.

2. Add the server to your client

   Paste the mcpServers block below into your Claude Desktop, Cursor, or Windsurf config.

3. Restart the client

   Restart your client. Start asking questions: "What's down?", "SLA on the API monitor this month?"

Client configuration

Claude Desktop, Cursor, Windsurf, Claude Code. Add to the mcpServers block of your client config:

{
  "mcpServers": {
    "hyperping": {
      "type": "http",
      "url": "https://api.hyperping.io/v1/mcp",
      "headers": {
        "Authorization": "Bearer sk_..."
      }
    }
  }
}

Older clients that only speak stdio can bridge via mcp-remote:

{
  "mcpServers": {
    "hyperping": {
      "command": "npx",
      "args": [
        "-y",
        "mcp-remote",
        "https://api.hyperping.io/v1/mcp",
        "--header",
        "Authorization: Bearer sk_..."
      ]
    }
  }
}

Tool reference

Your AI composes the queries; Hyperping returns the facts. Writes are scoped to reversible operations, delete_monitor is intentionally not exposed.

Security

Not available via MCP

Limits

Next steps