MCP Server

Zharp runs a Model Context Protocol server, so an AI assistant like Claude or Cursor can read your monitors and incidents and answer questions about them.

What an assistant can do

The server is read-only: an assistant can look at one workspace's monitors and incidents, but never create, change, acknowledge or resolve anything. It has five tools:

Things to ask once it's connected:

• “What's down in Zharp right now?”
• “Show me the timeline of the last incident on the Checkout API.”
• “What was the 7-day uptime of each of my API monitors?”

Endpoint

Get a token

Each assistant gets its own token, so you can cut one off without touching the others. Only the workspace owner can add clients.

1. 1
   Open MCP

   Go to Integrations & API → MCP. The page shows the endpoint and the clients that already have tokens.

2. 2
   Add a client

   Click Add client, name it after the assistant (for example “Claude Desktop”), and click Add client.

3. 3
   Copy the token

   The token, starting with zh_mcp_, is shown once. Pick your assistant — Claude Code, Claude Desktop, Cursor or VS Code — and copy its snippet, with the token already filled in, before you click Done. The snippets are the ones below.

The client names itself the first time it connects, and its row under Connected clients shows when it was last used. Open a client to see its recent requests, restrict it to certain IP addresses under Allowed IPs, Roll key or Revoke it.

Connect your assistant

Replace zh_mcp_YOUR_TOKEN with your token in each snippet.

claude mcp add --transport http zharp https://api.zharp.io/api/v1/mcp \
  --header "Authorization: Bearer zh_mcp_YOUR_TOKEN"

{
  "mcpServers": {
    "zharp": {
      "url": "https://api.zharp.io/api/v1/mcp",
      "headers": {
        "Authorization": "Bearer zh_mcp_YOUR_TOKEN"
      }
    }
  }
}

Claude Desktop starts local servers from its config file, so it reaches Zharp through the mcp-remote bridge (it needs Node.js). Open Settings → Developer → Edit Config and add:

{
  "mcpServers": {
    "zharp": {
      "command": "npx",
      "args": [
        "-y",
        "mcp-remote",
        "https://api.zharp.io/api/v1/mcp",
        "--header",
        "Authorization:${ZHARP_AUTH}"
      ],
      "env": {
        "ZHARP_AUTH": "Bearer zh_mcp_YOUR_TOKEN"
      }
    }
  }
}

Restart Claude Desktop afterwards. Don't paste a url and headers entry into claude_desktop_config.json: Claude Desktop doesn't read remote servers from that file. The token sits in env because some systems split an argument at the space in Bearer ….

{
  "servers": {
    "zharp": {
      "type": "http",
      "url": "https://api.zharp.io/api/v1/mcp",
      "headers": {
        "Authorization": "Bearer zh_mcp_YOUR_TOKEN"
      }
    }
  }
}

Check the connection

Ask the server for its tools directly. A working token gets back the five tools listed above:

curl -X POST https://api.zharp.io/api/v1/mcp \
  -H "Authorization: Bearer zh_mcp_YOUR_TOKEN" \
  -H "Content-Type: application/json" \
  -H "Accept: application/json, text/event-stream" \
  -d '{"jsonrpc":"2.0","id":1,"method":"tools/list"}'