Read pages, components, incidents and maintenances; create and update incidents in Statuspage. For engineering and support teams that publish incidents on Statuspage. Hosted by usefulapi — connect from Claude, ChatGPT, Cursor, or any MCP client.
Team and Enterprise: an Owner adds the connector for the organization first.
Run this command, then run /mcp in Claude Code to log in:
Add to Cursor or add this to ~/.cursor/mcp.json:
{
"mcpServers": {
"statuspage": {
"url": "https://statuspage.usefulapi.io/mcp"
}
}
}Add to VS Code or add this to .vscode/mcp.json:
{
"servers": {
"statuspage": {
"type": "http",
"url": "https://statuspage.usefulapi.io/mcp"
}
}
}No Add custom MCP server option? It depends on your account or workspace settings: see OpenAI's guide.
Run these commands. The second one opens the login page:
Other MCP clients (Windsurf, Cline, Zed and more): add the URL as a remote MCP server (Streamable HTTP). The client then opens the login page in your browser. Do not add an Authorization header: see Before you connect.
List the unresolved incidents and the components with their status.
statuspage_list_unresolved_incidents statuspage_list_components
Read the uptime of a component for a period.
statuspage_get_component statuspage_get_component_uptime
List past incidents and open one to read its updates.
statuspage_list_incidents statuspage_get_incident
Create an incident with a name, a status and the affected components.
Changes data · statuspage_list_components statuspage_create_incident
Update an incident with a new status message, or set a component status.
Changes data · statuspage_get_incident statuspage_update_incident statuspage_update_component_status
The login page asks for your Statuspage API key.
In Statuspage, open your user menu (bottom left) → API info and copy the API key. The key is used only to call the API for you and to derive a private account id.
Add only the URL. Do not add an Authorization header or an API key to the client config. The server signs you in with OAuth: the login page asks for your Statuspage API key. If the config has such a header, remove it: some clients then send that header instead of the login token, and every call fails with 401.
Turn on the Statuspage connector, then ask in plain words. The AI picks the tools.
| Tool | Type | What it does |
|---|---|---|
statuspage_list_pages | read | List status pages List the status pages the API key can see, with ids, names and subdomains. Start here to get a page_id. API: GET /pages. |
statuspage_get_page | read | Get a status page Get the profile of one status page (name, subdomain, domain, time zone, notification settings). API: GET /pages/{page_id}. |
statuspage_list_components | read | List components List the components of a page with their current status (operational, degraded_performance, partial_outage, major_outage, under_maintenance). API: GET /pages/{page_id}/components. |
statuspage_get_component | read | Get a component Get one component with its status, group and description. API: GET /pages/{page_id}/components/{component_id}. |
statuspage_get_component_uptime | read | Get component uptime Get uptime data for one component over a date range (default: the last 90 days). Dates are ISO 8601. API: GET /pages/{page_id}/components/{component_id}/uptime. |
statuspage_list_component_groups | read | List component groups List the component groups of a page. API: GET /pages/{page_id}/component-groups. |
statuspage_list_incidents | read | List incidents List incidents of a page, newest first. Use q to search by name, status or impact text. API: GET /pages/{page_id}/incidents. |
statuspage_list_unresolved_incidents | read | List unresolved incidents List incidents that are not resolved yet (investigating, identified, monitoring). API: GET /pages/{page_id}/incidents/unresolved. |
statuspage_list_maintenances | read | List maintenances List scheduled maintenances of a page. kind: scheduled (all planned), upcoming (not started) or active (in progress). API: GET /pages/{page_id}/incidents/{scheduled|upcoming|active_maintenance}. |
statuspage_get_incident | read | Get an incident Get one incident with its full update timeline and affected components. API: GET /pages/{page_id}/incidents/{incident_id}. |
statuspage_count_subscribers | read | Count subscribers Count the subscribers of a page by type (email, sms, webhook and others). API: GET /pages/{page_id}/subscribers/count. |
statuspage_list_metrics | read | List metrics List the metrics shown on a page (for example response time). API: GET /pages/{page_id}/metrics. |
statuspage_update_component_status | write | Update a component status WRITE, public. Set the status of one component on the live status page. Visitors see the change at once. API: PATCH /pages/{page_id}/components/{component_id}. |
statuspage_create_incident | write | Create an incident WRITE, public. Create a real-time incident on the live status page. It is visible to visitors. With deliver_notifications true (the default of Statuspage) it also sends messages to subscribers. A second call creates a second incident. API: POST /pages/{page_id}/incidents. |
statuspage_update_incident | write | Update an incident WRITE, public. Post a new update on an incident: change its status, add update text, or set the status of components. Each call with body adds a new timeline entry and can notify subscribers, so do not repeat it. Setting status resolved closes the incident. API: PATCH /pages/{page_id}/incidents/{incident_id}. |
statuspage_usage_status | Usage status (free-tier meter) Report the caller's current usage: the plan, calls used this month, the limit of the plan (the free monthly cap or the Pro fair use limit), remaining, and whether the limit is reached. Read-only; does not count against the meter. | |
statuspage_request_feature | Request a missing feature Tell usefulapi that the user needs something the Statuspage tools cannot do yet (a missing tool, field or filter). Call it only when the user asks for something none of the tools can do, and tell the user that you send the request. Do not call it for errors or for normal requests. Do not include personal data, credentials or customer records. Stored with the product name and the client type (for example Claude or Cursor), without the user's account. At most 5 requests per day. Does not count against the meter. | |
statuspage_upgrade | Upgrade to Pro (unlimited*) Get Pro: unlimited tool calls (fair use limit: 10,000 a month) on Statuspage (the free tier caps monthly usage). Plans: "monthly" — $9/month; "yearly" — $90/year (2 months free). Cancel any time: Pro then runs to the end of the paid period, so it also suits a one-time job. *A fair use limit applies. For heavy use (near Pro's limit): "plus" or "plus_yearly" — Pro+, $39/month or $390/year, unlimited tool calls (fair use limit: 100,000 a month); an existing Pro subscription changes to Pro+ in place (needs confirm: true; the price difference for the rest of the period is charged at once). Otherwise returns a short link to open in your browser (it opens Stripe Checkout); after payment the account upgrades automatically. Does not count against the meter. | |
statuspage_cancel_subscription | Cancel the Pro subscription Cancel the caller's Statuspage Pro subscription at the end of the paid period (no refund for the current period; Pro continues until then, then the free tier applies). Requires confirm: true. Run statuspage_upgrade later to undo the cancel before the period ends. Does not count against the meter. |
| Plan | Price | Limit |
|---|---|---|
| Free | $0 | 50 tool calls / month |
| Proper user | $9/mo · $90/yr | Unlimited* |
*Pro fair use limit: 10,000 tool calls a month on this server. For more, write to [email protected].
Pro covers this Statuspage server only. Subscribe with statuspage_upgrade (it returns a Stripe Checkout link). Cancel any time with statuspage_cancel_subscription: Pro continues to the end of the paid period, with no refund for the current period, and running statuspage_upgrade before then undoes the cancel. Or write to [email protected].
Check what is broken now. Review the uptime of a component. Prepare a post-incident review. Open an incident. Post an update. See what you can do for the details.
No. usefulapi is an independent service. It is not affiliated with or endorsed by Statuspage. The server calls the Statuspage API with your own Statuspage access, so it sees only the data that your account can see.
Yes. In Claude, add this server's URL as a custom connector. In ChatGPT, add it as a custom MCP server in Plugins. Then log in once. Cursor, VS Code, Claude Code and Codex work too. See the setup steps.
The login page asks for your Statuspage API key. See Before you connect for where to find it.
No. Add only the URL. Do not add an Authorization header or an API key to the client config. The server signs you in with OAuth: the login page asks for your Statuspage API key. If the config has such a header, remove it: some clients then send that header instead of the login token, and every call fails with 401.
The login stores them encrypted in the authorization grant of your connection. The server uses them to call the Statuspage API for you and to derive a private account id for usage metering. usefulapi does not show them on any page or in any reply. To stop all access, remove the connector and change or delete these credentials in Statuspage.
Yes, if you approve it. 3 of the 15 Statuspage tools can create or change data. The other 12 are marked read-only. Most MCP clients ask you to approve a tool call before it runs.
The Free plan gives 50 tool calls / month. Pro costs $9/mo or $90/yr, with unlimited tool calls (fair use limit: 10,000 tool calls a month), for this Statuspage server only. Cancel any time: Pro then runs to the end of the paid period. Run statuspage_usage_status to see how many calls you used.
Ask the AI to run statuspage_upgrade: it returns a Stripe Checkout link. To cancel, run statuspage_cancel_subscription. Pro continues to the end of the paid period.
Tell the AI what you wanted to do. It can send the request with statuspage_request_feature. We store the text with the server name, the type of AI client and the tool you tried, not with your account, and read every request when we plan new tools. You can send up to 5 requests per day.
Any client that supports remote MCP servers (Streamable HTTP) with OAuth login: Claude (web and desktop), Claude Code, ChatGPT, Codex, Cursor, VS Code, Windsurf and others.
This is a Model Context Protocol endpoint — meant to be connected from an AI client, not opened in a browser. An invalid_token response at the URL is the auth gate working as designed; clients authenticate automatically.
Need a tool this server does not have, or a connection to another system? We build custom integrations and MCP servers.