MCP Server

The FTStatus MCP server lets AI assistants (Claude, Cursor, and other Model Context Protocol clients) read your monitors, status, uptime, incidents, and status pages directly from a conversation.

Read-only

The MCP server currently exposes read-only tools scoped to your workspace. It cannot create, edit, or delete anything.

Endpoint

https://app.ftstatus.com/api/mcp

The transport is Streamable HTTP (stateless): the server speaks JSON-RPC 2.0 over a single POST endpoint (initialize, tools/list, tools/call). A GET returns a small liveness/discovery document.

Authentication

Every request must include an FTStatus API key as a Bearer token. A read-only key is recommended (least privilege) — the server only exposes read tools regardless:

Authorization: Bearer os_xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx

Create a key in the dashboard's Settings → General → API keys. Requests without a valid key receive 401. Every tool is scoped to the workspace the key belongs to.

Tools

Tool	Purpose
`list_monitors`	List your workspace's monitors (id, name, URL, type, check interval, current status).
`get_monitor_status`	Current per-region status (active / degraded / error) of one monitor.
`get_monitor_uptime`	Uptime % and latency stats (avg / min / max ms) for a monitor over a period (`1d`, `7d`, or `30d`).
`list_incidents`	Recent incidents, most recent first; optionally filtered to one monitor.
`list_status_pages`	Your workspace's public status pages.

Connect from Claude

Use an MCP client that supports remote Streamable-HTTP servers, pointing at the endpoint with your Bearer key. For clients that only launch local stdio servers, bridge with mcp-remote:

{
  "mcpServers": {
    "ftstatus": {
      "command": "npx",
      "args": [
        "-y",
        "mcp-remote",
        "https://app.ftstatus.com/api/mcp",
        "--header",
        "Authorization: Bearer os_xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx"
      ]
    }
  }
}

You'll need Node.js 18+ on your PATH so the client can run npx.