Connect FTStatus to Claude Code

In this guide, you'll connect the FTStatus MCP server to Claude Code so the agent can read your monitors, current status, uptime/latency, incidents, and status pages directly from your terminal.

1. Create an API key

Open the FTStatus dashboard, go to Settings → General → API keys, and create a key. A read-only key is recommended (least privilege) — the server only exposes read tools regardless. Copy the key (it starts with os_); you'll only see it once.

2. Add the MCP server to Claude Code

Claude Code talks to the FTStatus MCP server over Streamable HTTP. Register it with claude mcp add, passing your key as a Bearer token:

claude mcp add \
  --transport http \
  --scope user \
  --header "Authorization: Bearer os_xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx" \
  ftstatus \
  https://app.ftstatus.com/api/mcp

Project-scoped alternative

To commit the configuration to your repo, create a .mcp.json at the project root and rely on env expansion so the key never lands in version control:

{
  "mcpServers": {
    "ftstatus": {
      "type": "http",
      "url": "https://app.ftstatus.com/api/mcp",
      "headers": {
        "Authorization": "Bearer ${FTSTATUS_API_KEY}"
      }
    }
  }
}

Then export FTSTATUS_API_KEY in your shell.

3. Verify the connection

Open Claude Code and run /mcp. You should see ftstatus listed as connected, with the read tools: list_monitors, get_monitor_status, get_monitor_uptime, list_incidents, list_status_pages.

4. Try your first prompt

> list my ftstatus monitors and their uptime over the last 7 days

Claude Code will call list_monitors and get_monitor_uptime, prompt you to approve the calls, and return the results from your workspace.

Troubleshooting

/mcp shows FTStatus as disconnected

1. Re-check the header — run claude mcp list and confirm the Authorization: Bearer os_… value matches a key in Settings → General → API keys. Trailing whitespace/newlines are a common copy-paste failure.
2. Reachability — curl -i https://app.ftstatus.com/api/mcp returns a liveness document (the tool list) on GET; a POST without a valid key returns 401.
3. Re-add the server — claude mcp remove ftstatus, then re-run the claude mcp add command from step 2.

What's next

• MCP server reference — the full tool list and endpoint contract.
• The same API key + endpoint work for Claude Desktop, Cursor, and any other MCP-compatible client (bridge with mcp-remote if the client only launches local stdio servers).