Bring Hyperping into your AI workflows.

Connect Claude, Cursor, Windsurf, or any MCP-compatible client to your Hyperping project with one API token. Read monitors, drill into outages, follow the on-call chain, and pause services from a prompt.

Every REST endpoint, exposed as a tool.

Your AI composes the queries; Hyperping returns the facts. Deletion is intentionally not exposed. Reversible changes only.

Three steps. One token.

Works with any MCP-compatible client. No local server, no SDK.

1. Create an API key

   In Hyperping, open Project Settings → API Keys. Pick read-only or read-write. Keys are strictly scoped to one project.

2. Drop in the server config

   Paste this into your client's MCP config. The same JSON works for Claude Desktop, Cursor, Windsurf, Cline, and Claude Code.

   ~/.claude/claude_desktop_config.jsonjson

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

3. Restart and ask

   Restart your client. Start asking questions. Every call reuses the same auth, permissions, rate limits, and activity logs as the REST API.

How the server behaves.

Same guarantees as the REST API. No new abstractions to reason about.

Endpoint

https://api.hyperping.io/v1/mcp

Transport

MCP over HTTP, stateless. No persistent connection.

Auth

Authorization: Bearer sk_live_...

Scope

One API key, one project. No cross-project access.

Write surface

pause, resume, create, update. Deletion is not exposed.

Read-only keys

Supported. All write tools return a 403 for keys without write scope.

Rate limit

300 req / min / key, shared with REST.

Observability

Every call appears in the project's activity log with the tool name, caller, and latency.

What people actually ask.

Copy any of these into your MCP-connected client.