Read Status.io components, incidents, maintenance; post incidents, schedule maintenance, set status. For engineering and support teams who run a public status page with Status.io. 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": {
"status-io": {
"url": "https://status-io.usefulapi.io/mcp"
}
}
}Add to VS Code or add this to .vscode/mcp.json:
{
"servers": {
"status-io": {
"type": "http",
"url": "https://status-io.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.
The AI reads the overall status, every component and container with its status, open incidents and upcoming maintenance in one view.
statusio_get_status_summary statusio_list_components
The AI lists active or resolved incidents with their messages and affected components, and opens one incident in full.
statusio_list_active_incidents statusio_list_resolved_incidents statusio_get_incident
The AI lists maintenance events by state, pending, active or closed, with messages and affected components.
statusio_list_maintenance statusio_get_maintenance
The AI opens an incident on the public status page, posts update messages with state and component status, and resolves it with a closing message. Notifications go out only if you switch them on.
Changes data · statusio_create_incident statusio_update_incident statusio_resolve_incident
The AI schedules a planned maintenance event, starts it, posts status messages and finishes it, so visitors see the right state at each step.
Changes data · statusio_schedule_maintenance statusio_start_maintenance statusio_update_maintenance statusio_finish_maintenance
The AI sets a component and container to a status such as degraded_performance without creating an incident, and back to operational later.
Changes data · statusio_list_components statusio_update_component_status
The login page asks for your API ID, API key and Status page id.
Find the API ID and API key in your Status.io Dashboard → API tab; the status page id is on the same tab. Each team member has their own pair, and the pair acts with that member's permissions. They are used only to call the Status.io API on your behalf and are never shown to anyone.
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 API ID, API key and Status page id. 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 Status.io connector, then ask in plain words. The AI picks the tools.
| Tool | Type | What it does |
|---|---|---|
statusio_get_status_summary | read | Get status summary The current state of the status page in one call: overall status, every component and container with its status code and last update, open incidents and active/upcoming maintenance. Start here. GET /status/summary/{statuspage_id}. |
statusio_list_components | read | List components List the components of the status page and the containers (data centers / locations) attached to each, with ids. Component and container ids are needed to update a status or to say what an incident affects ('<component_id>-<container_id>'). GET /component/list/{statuspage_id}. |
statusio_list_incidents | read | List incident ids The ids of all active and resolved incidents (ids only, no details): a quick way to see which incidents exist. Fetch one with statusio_get_incident. GET /incidents/{statuspage_id}. |
statusio_list_active_incidents | read | List active incidents Active (unresolved) incidents with their messages and affected components. GET /incident/list/active/{statuspage_id}. |
statusio_list_resolved_incidents | read | List resolved incidents Resolved incidents (history) with their messages and affected components. GET /incident/list/resolved/{statuspage_id}. |
statusio_get_incident | read | Get incident One incident in full: components, containers, infrastructure affected and all its messages. GET /incident/{statuspage_id}/{incident_id}. |
statusio_get_incident_message | read | Get incident message One message (update) of an incident: text, state, status, time and the user who posted it. GET /incident/message/{statuspage_id}/{message_id}. |
statusio_list_maintenance_ids | read | List maintenance ids The ids of all active, closed and upcoming maintenance events (ids only). Fetch one with statusio_get_maintenance. GET /maintenances/{statuspage_id}. |
statusio_list_maintenance | read | List maintenance Maintenance events in one state, with messages and affected components: pending (scheduled, not started), active (in progress) or closed (finished). GET /maintenance/list/{pending|active|closed}/{statuspage_id}. |
statusio_get_maintenance | read | Get maintenance One maintenance event in full, with all messages and the infrastructure affected. GET /maintenance/{statuspage_id}/{maintenance_id}. |
statusio_get_maintenance_message | read | Get maintenance message One message of a maintenance event. GET /maintenance/message/{statuspage_id}/{message_id}. |
statusio_list_subscribers | read | List subscribers List the people and endpoints subscribed to the status page (email addresses, phone numbers, webhook hosts) with ids and their granular preferences. This is personal data of your subscribers. Webhook URLs are shortened to their host, because they can carry secrets. GET /subscriber/list/{statuspage_id}. |
statusio_update_component_status | write | Update component status WRITE: change the PUBLIC status of one component/container pair (for example to degraded_performance) without creating an incident. It changes what visitors of your status page see right away. Set it back to operational when done. Ids from statusio_list_components. POST /component/status/update. |
statusio_create_incident | write | Create incident WRITE: open a new incident on the PUBLIC status page. It is visible to every visitor immediately and sets the status of the affected components. No subscriber, Slack, Teams, IRC or Twitter notification is sent unless you switch it on (notify_*). Returns the new incident id. Say what is affected with all_infrastructure_affected or infrastructure_affected pairs. POST /incident/create. |
statusio_update_incident | write | Update incident WRITE: post a new update message on an existing incident and set its state and component status. The message is public at once. No subscriber or channel notification is sent unless you switch it on (notify_*). To close an incident use statusio_resolve_incident. POST /incident/update. |
statusio_resolve_incident | write | Resolve incident WRITE: resolve an incident with a closing message. The affected components return to operational and the incident moves to history. No notification is sent unless you switch it on (notify_*). POST /incident/resolve. |
statusio_schedule_maintenance | write | Schedule maintenance WRITE: schedule a planned maintenance on the PUBLIC status page. It is visible to visitors as upcoming maintenance. Subscribers are told only if you switch on notify_now / notify_72_hr / notify_24_hr / notify_1_hr (all default off). With automation true Status.io starts and ends it by itself at the planned times. Returns the maintenance id. POST /maintenance/schedule. |
statusio_start_maintenance | write | Start maintenance WRITE: start a scheduled maintenance now; it moves from pending to active and the affected components show planned maintenance. The message is public at once. No notification is sent unless you switch it on (notify_*). POST /maintenance/start. |
statusio_update_maintenance | write | Update maintenance WRITE: post a new status message on an active maintenance event. The message is public at once. No notification is sent unless you switch it on (notify_*). POST /maintenance/update. |
statusio_finish_maintenance | write | Finish maintenance WRITE: finish an active maintenance event; it moves to history and the affected components return to operational. The message is public at once. No notification is sent unless you switch it on (notify_*). POST /maintenance/finish. |
statusio_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. | |
statusio_request_feature | Request a missing feature Tell usefulapi that the user needs something the Status.io 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. | |
statusio_upgrade | Upgrade to Pro (unlimited*) Get Pro: unlimited tool calls (fair use limit: 10,000 a month) on Status.io (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. | |
statusio_cancel_subscription | Cancel the Pro subscription Cancel the caller's Status.io 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 statusio_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 Status.io server only. Subscribe with statusio_upgrade (it returns a Stripe Checkout link). Cancel any time with statusio_cancel_subscription: Pro continues to the end of the paid period, with no refund for the current period, and running statusio_upgrade before then undoes the cancel. Or write to [email protected].
Check the current state of your status page. Review active or resolved incidents and their updates. See pending, active or finished maintenance. Open an incident, post updates and resolve it. Schedule, start and finish a maintenance event. Change a component's public status. See what you can do for the details.
No. usefulapi is an independent service. It is not affiliated with or endorsed by Status.io. The server calls the Status.io API with your own Status.io 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 API ID, API key and Status page id. See Before you connect for where to find them.
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 API ID, API key and Status page id. 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 Status.io 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 Status.io.
Yes, if you approve it. 8 of the 20 Status.io 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 Status.io server only. Cancel any time: Pro then runs to the end of the paid period. Run statusio_usage_status to see how many calls you used.
Ask the AI to run statusio_upgrade: it returns a Stripe Checkout link. To cancel, run statusio_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 statusio_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.