Read status pages and incidents; make confirmed public changes and manage individual subscribers. For status-page teams with authorized Sorry API access. 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": {
"sorry-app": {
"url": "https://sorry-app.usefulapi.io/mcp"
}
}
}Add to VS Code or add this to .vscode/mcp.json:
{
"servers": {
"sorry-app": {
"type": "http",
"url": "https://sorry-app.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.
Find notices and inspect their public timeline and affected components.
sorryapp_list_notices sorryapp_get_notice sorryapp_list_notice_updates
Read the components and current state of a selected status page.
sorryapp_get_page sorryapp_list_components
Create a public notice after explicit confirmation. Request subscriber broadcasts only after reviewing the audience.
Changes data · sorryapp_create_incident
After explicit confirmation, add a public maintenance notice with the intended schedule and notification setting.
Changes data · sorryapp_create_maintenance
After confirmation, update the notice state and public comment while respecting the requested broadcast flag.
Changes data · sorryapp_update_notice
The login page asks for your Sorry API token.
Create a user-specific token at app.sorryapp.com → My Account → API Tokens. The token is encrypted for authorized API calls. Requested status records and subscriber contact details reach your selected AI client/LLM provider; webhook URLs and credentials are redacted. Status writes are public even with publish=false; publish=true additionally requests subscriber/integration broadcasts and SMS charges may apply. Explicit confirmation is required. No operation is automatically replayed: check Sorry after an uncertain write. Revoke the token in Sorry to stop access; disconnect UsefulAPI to stop this connection. Usage and billing are tied to this token: rotating it creates a new UsefulAPI identity. Cancel the old UsefulAPI plan before rotation or contact support to arrange a transfer. Vendor subscriptions, quotas and charges remain separate.
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 Sorry API token. 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 Sorry connector, then ask in plain words. The AI picks the tools.
| Tool | Type | What it does |
|---|---|---|
sorryapp_list_pages | read | List status pages List the status pages the API token's user can access: id, name, state (operational/degraded/...), timezone, locale, support contacts, notification channels. The id is the page_id every other tool takes. Sorry: GET /v1/pages. |
sorryapp_get_page | read | Get status page Get one status page, optionally with related resources embedded (brand, components, custom_domain, notices, notices.updates, theme). Sorry: GET /v1/pages/{page_id}?include=... |
sorryapp_list_components | read | List components List a status page's components (the parts of your service shown on the page): id, name, description, state (operational/degraded/partially-degraded), position, parent_id. Sorry: GET /v1/pages/{page_id}/components. |
sorryapp_get_component | read | Get component Get one component of a status page. Sorry: GET /v1/pages/{page_id}/components/{component_id}. |
sorryapp_list_notices | read | List notices List a status page's notices (incidents = type unplanned, maintenance = type planned): id, type, state, timeline_state, subject, synopsis, began/ended times, public link. Optional filters and embedded updates/components. Sorry: GET /v1/pages/{page_id}/notices. |
sorryapp_get_notice | read | Get notice Get one notice (incident or maintenance) with its state, times and public link. Sorry: GET /v1/pages/{page_id}/notices/{notice_id}. |
sorryapp_list_notice_updates | read | List notice updates List the updates (timeline comments) of one notice: id, content, should_publish, public link, times. Sorry: GET /v1/pages/{page_id}/notices/{notice_id}/updates. |
sorryapp_get_notice_update | read | Get notice update Get one update of a notice. Sorry: GET /v1/pages/{page_id}/notices/{notice_id}/updates/{update_id}. |
sorryapp_list_notice_templates | read | List notice templates List the page's notice templates (reusable subject + opening comment for new incidents or maintenance): id, name, subject, initial_comment, optional component_id. Returns the vendor-default template page; paging controls are withheld pending a verified request contract. Sorry: GET /v1/pages/{page_id}/notice_templates. |
sorryapp_list_update_templates | read | List update templates List the page's update templates (reusable text for one notice update): id, name, content, optional component_id. Returns the vendor-default template page; paging controls are withheld pending a verified request contract. Sorry: GET /v1/pages/{page_id}/update_templates. |
sorryapp_list_subscribers | read | List subscribers List a status page's subscribers (people and channels notified of notices): id, email, phone number, name, company, tags, created time. Webhook URLs of Slack/Teams subscribers are redacted. Contains personal data. Sorry: GET /v1/pages/{page_id}/subscribers. |
sorryapp_get_subscriber | read | Get subscriber Get one subscriber of a status page (personal data; webhook URLs redacted). Sorry: GET /v1/pages/{page_id}/subscribers/{subscriber_id}. |
sorryapp_list_timezones | read | List timezones List the timezone names Sorry accepts for a status page (name and GMT offset label). Sorry: GET /v1/timezones. |
sorryapp_create_component | write | Create component WRITE: add a component to a status page. It appears on the PUBLIC status page immediately, as operational. Sorry: POST /v1/pages/{page_id}/components. |
sorryapp_update_component | write | Update component WRITE: rename a component or change its description on the PUBLIC status page (overwrites the previous value). It cannot change the component's state: state follows open notices (use the notice tools). Sorry: PATCH /v1/pages/{page_id}/components/{component_id}. |
sorryapp_create_incident | write | Create incident notice WRITE: open an incident (an unplanned notice) on the status page. These changes are PUBLIC on the status page, including publish=false. publish=true additionally requests delivery to subscribers and integrations (email, SMS, Slack, Teams, X); vendor SMS/notification charges may apply. Confirm the content and audience first. It marks the listed components degraded on the PUBLIC page. Starts in the investigating state. Sorry: POST /v1/pages/{page_id}/notices with type=unplanned. |
sorryapp_create_maintenance | write | Create maintenance notice WRITE: schedule maintenance (a planned notice) on the status page. These changes are PUBLIC on the status page, including publish=false. publish=true additionally requests delivery to subscribers and integrations (email, SMS, Slack, Teams, X); vendor SMS/notification charges may apply. Confirm the content and audience first. Sorry: POST /v1/pages/{page_id}/notices with type=planned. |
sorryapp_update_notice | write | Update notice WRITE: change a notice: its subject, state (for example resolved), affected components, schedule, and/or add a comment (an update) to its timeline. These changes are PUBLIC on the status page, including publish=false. publish=true additionally requests delivery to subscribers and integrations (email, SMS, Slack, Teams, X); vendor SMS/notification charges may apply. Confirm the content and audience first. Fields you pass overwrite the previous values. Sorry: PATCH /v1/pages/{page_id}/notices/{notice_id}. |
sorryapp_create_notice_update | write | Add notice update WRITE: add one update (a comment) to a notice's timeline. It is PUBLIC on the status page, and Sorry's docs say a new update is also published to the page's configured integrations (email, SMS, Slack, Teams, X). The docs list no switch to suppress that on this endpoint, so confirm_publish=true is required; this endpoint has no exposed suppression switch. Sorry: POST /v1/pages/{page_id}/notices/{notice_id}/updates. |
sorryapp_edit_notice_update | write | Edit notice update WRITE: rewrite the text of an existing notice update on the PUBLIC status page (overwrites the previous text; the old text is not kept). Sorry: PATCH /v1/pages/{page_id}/notices/{notice_id}/updates/{update_id}. |
sorryapp_create_subscriber | write | Add one subscriber WRITE: add ONE subscriber (an email address and/or a phone number) to a status page. From then on that person is emailed/texted about notices published on the page, and Sorry may send them a confirmation. Add only people who asked to be notified. No bulk import. Sorry: POST /v1/pages/{page_id}/subscribers. |
sorryapp_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. | |
sorryapp_request_feature | Request a missing feature Tell usefulapi that the user needs something the Sorry 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. | |
sorryapp_upgrade | Upgrade to Pro (unlimited*) Get Pro: unlimited tool calls (fair use limit: 10,000 a month) on Sorry (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. | |
sorryapp_cancel_subscription | Cancel the Pro subscription Cancel the caller's Sorry 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 sorryapp_upgrade later to undo the cancel before the period ends. Does not count against the meter. |
| Plan | Price | Limit |
|---|---|---|
| Freeper connected Sorry API token | $0 | 50 tool calls / month |
| Proper connected Sorry API token | $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 Sorry server only. Subscribe with sorryapp_upgrade (it returns a Stripe Checkout link). Cancel any time with sorryapp_cancel_subscription: Pro continues to the end of the paid period, with no refund for the current period, and running sorryapp_upgrade before then undoes the cancel. Or write to [email protected].
Review current incidents. Check service components. Publish an approved incident. Schedule agreed maintenance. Resolve an incident with an agreed update. See what you can do for the details.
No. usefulapi is an independent service. It is not affiliated with or endorsed by Sorry. The server calls the Sorry API with your own Sorry 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 Sorry API token. 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 Sorry API token. 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 Sorry 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 Sorry.
Yes, if you approve it. 8 of the 21 Sorry tools can create or change data. The other 13 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 Sorry server only. Cancel any time: Pro then runs to the end of the paid period. Run sorryapp_usage_status to see how many calls you used.
Ask the AI to run sorryapp_upgrade: it returns a Stripe Checkout link. To cancel, run sorryapp_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 sorryapp_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.