API & MCP

MCP Server

Connect Claude and other AI tools to Statusfield's live status catalog with the hosted MCP server. Read-only, Starter plan and up.

The Model Context Protocol (MCP) is an open standard for connecting AI assistants to external tools and live data. Statusfield hosts a read-only MCP server that exposes the same status catalog as the REST API, so you can ask Claude (or any MCP-capable client) questions like "Is GitHub having issues right now?" and get answers straight from live data.

Requirements

The MCP server uses the same sf_ API key as the REST API — no separate credential. Create one at Settings → Integrations → API Keys, where you can also revoke it later. The key is shown only once at creation time.

Starter plan and up

MCP access is available on the Starter, Pro, and Team plans — the same gate as the REST API. It is not available on the Basic plan. A Basic-plan key returns 403 plan_restriction. See /pricing for per-plan limits.

Connecting

The server speaks Streamable HTTP at POST /api/mcp and authenticates with your sf_ key in the Authorization header.

Get an API key

Go to Settings → Integrations → API Keys at statusfield.com/integrations and create a key. Copy it — it is shown only once.

Add it to the Claude Code CLI

Run the following, replacing sf_<your-key> with your key:

claude mcp add --transport http statusfield \
  https://statusfield.com/api/mcp \
  --header "Authorization: Bearer sf_<your-key>"

Or connect another MCP client

Use your client's supported remote Streamable HTTP connection with URL https://statusfield.com/api/mcp and header Authorization: Bearer sf_<your-key>. Client setup varies; use its documented remote-server settings. Do not paste your key into a prompt or a shared configuration.

Ask a question

Once connected, ask your assistant something like "Is GitHub having any issues right now?" and it will call the matching tool automatically.

Tools

The server exposes four read-only tools:

Tool	Input	Description
`search_services`	`query: string`	Search the catalog by name; returns up to 10 matches as `Name (slug)` lines
`get_service_status`	`slug: string`	Current status of a service and all its components
`list_my_down_services`	(none)	Your own monitored services currently down or degraded

Catalog search vs. monitored status

search_services searches the public catalog without exposing live status. get_service_status returns status only for services your workspace actively monitors. list_my_down_services reports your own monitors that are down or degraded. For the full monitor list, use GET /api/v2/monitors.

Rate limits & quota

Rate limit: your plan's per-workspace burst limit applies to every request. X-RateLimit-Limit and X-RateLimit-Remaining are returned on responses, and a Retry-After (seconds) header is added on 429.
Monthly quota: only tools/call invocations count toward your plan's monthly request quota. Protocol traffic (initialize, tools/list) is free. X-Quota-* headers are returned on metered requests, and exceeding the cap returns 429 quota_exceeded. The counter resets at the start of each UTC month.

Current limits, shared with REST per workspace:

Plan	Requests / minute	Requests / second	Requests / UTC month
Basic	—	—	No API access
Starter	30	5	100,000
Pro	60	10	500,000
Team	120	20	2,000,000

Example prompts

Natural-language questions map onto the tools automatically:

"Is GitHub having any issues right now?" → get_service_status with slug github
"Is anything I monitor down right now?" → list_my_down_services
"Find monitoring services" → search_services with query monitoring

Next steps

API reference — the full REST API, including GET /api/v2/monitors for your own workspace's monitors.
Pricing — per-plan rate limits and monthly quotas.