Sorry MCP server

Read status pages and incidents; make confirmed public changes and manage individual subscribers. Hosted by usefulapi: connect it to Claude, ChatGPT, Cursor or any MCP client.

Connect SorryFree 50 tool calls / monthPro $9/mo · $90/yr · pricing25 tools

What can I ask?

Turn on the Sorry connector, then ask in plain words. The AI picks the tools.

What you can do with Sorry in Claude and ChatGPT

For status-page teams with authorized Sorry API access.

Review current incidents

Find notices and inspect their public timeline and affected components.

Check service components

Read the components and current state of a selected status page.

Publish an approved incident

Create a public notice after explicit confirmation. Request subscriber broadcasts only after reviewing the audience.

Changes data

Schedule agreed maintenance

After explicit confirmation, add a public maintenance notice with the intended schedule and notification setting.

Changes data

Resolve an incident with an agreed update

After confirmation, update the notice state and public comment while respecting the requested broadcast flag.

Changes data

How do I connect Sorry?

Before you connect

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.

Claude claude.ai · Desktop

  1. Open Customize → Connectors, then click + Add → Add custom connector.
  2. Enter the name Sorry and this URL, then click Add:
    https://sorry-app.usefulapi.io/mcp
  3. Claude opens the login page: enter your Sorry API token.
  4. In a chat, click + → Connectors and turn on Sorry.

Team and Enterprise: an Owner adds the connector for the organization first.

ChatGPT chatgpt.com

  1. Open Plugins, click +, then Add custom MCP server.
  2. Enter the name Sorry and this URL, choose OAuth as the authentication, confirm the warning and create it:
    https://sorry-app.usefulapi.io/mcp
  3. ChatGPT opens the login page: enter your Sorry API token.
  4. In Plugins, install Sorry, then choose it in a chat.

No Add custom MCP server option? It depends on your account or workspace settings: see OpenAI's guide.

Claude Code

Run this command, then run /mcp in Claude Code to log in:

claude mcp add --transport http sorry-app https://sorry-app.usefulapi.io/mcp

Cursor

Add to Cursor or add this to ~/.cursor/mcp.json:

{
  "mcpServers": {
    "sorry-app": {
      "url": "https://sorry-app.usefulapi.io/mcp"
    }
  }
}

VS Code

Add to VS Code or add this to .vscode/mcp.json:

{
  "servers": {
    "sorry-app": {
      "type": "http",
      "url": "https://sorry-app.usefulapi.io/mcp"
    }
  }
}

Codex

Run these commands. The second one opens the login page:

codex mcp add sorry-app --url https://sorry-app.usefulapi.io/mcp
codex mcp login sorry-app

Other clients

Windsurf, Cline, Zed and other MCP clients: add this URL as a remote MCP server (Streamable HTTP). The client then opens the login page in your browser.

https://sorry-app.usefulapi.io/mcp

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.

Pricing

PlanPriceLimit
Freeper connected Sorry API token$050 tool calls / month
Proper connected Sorry API token$9/mo · $90/yr10,000 tool calls / month
Pro+per connected Sorry API token$39/mo · $390/yr100,000 tool calls / month

Each paid plan covers this Sorry server only. Ask your AI to run sorryapp_upgrade and choose Pro or Pro+, billed monthly or yearly (it returns a Stripe Checkout link). If you already have Pro, ask to change it to Pro+. The change requires your confirmation, keeps your billing interval and charges the price difference for the rest of the period immediately. Cancel any time with sorryapp_cancel_subscription: your paid plan continues to the end of the paid period, with no refund for the current period, and asking to resume the same plan with sorryapp_upgrade before then undoes the cancel. Or write to [email protected].

Tools 25

Show all 25 tools (the AI picks them for you)

Read only · 13

  • List status pagessorryapp_list_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.
  • Get status pagesorryapp_get_page
    Get one status page, optionally with related resources embedded (brand, components, custom_domain, notices, notices.updates, theme).
  • List componentssorryapp_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.
  • Get componentsorryapp_get_component
    Get one component of a status page.
  • List noticessorryapp_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.
  • Get noticesorryapp_get_notice
    Get one notice (incident or maintenance) with its state, times and public link.
  • List notice updatessorryapp_list_notice_updates
    List the updates (timeline comments) of one notice: id, content, should_publish, public link, times.
  • Get notice updatesorryapp_get_notice_update
    Get one update of a notice.
  • List notice templatessorryapp_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.
  • List update templatessorryapp_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.
  • List subscriberssorryapp_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.
  • Get subscribersorryapp_get_subscriber
    Get one subscriber of a status page (personal data; webhook URLs redacted).
  • List timezonessorryapp_list_timezones
    List the timezone names Sorry accepts for a status page (name and GMT offset label).

Changes data · 8

  • Create componentsorryapp_create_component
    WRITE: add a component to a status page. It appears on the PUBLIC status page immediately, as operational.
  • Update componentsorryapp_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).
  • Create incident noticesorryapp_create_incident
    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.
  • Create maintenance noticesorryapp_create_maintenance
    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.
  • Update noticesorryapp_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.
  • Add notice updatesorryapp_create_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.
  • Edit notice updatesorryapp_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).
  • Add one subscribersorryapp_create_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.

Your usefulapi plan · 4

  • Usage status (free-tier meter)sorryapp_usage_status
    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.
  • Request a missing featuresorryapp_request_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.
  • Upgrade to Pro or Pro+sorryapp_upgrade
    Get a paid plan for Sorry (the free tier caps monthly usage). Pro: 10,000 tool calls a month, for normal use — plan "monthly" ($9/month) or "yearly" ($90/year, 2 months free). Pro+: 100,000 tool calls a month, for automations and heavy use — plan "plus" ($39/month) or "plus_yearly" ($390/year). Without a plan it returns both Pro and Pro+, each with a payment link, for the user to choose; with a plan, one link. 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). Cancel any time: the plan then runs to the end of the paid period, so it also suits a one-time job. A link opens Stripe Checkout in the browser; after payment the account upgrades automatically. Does not count against the meter.
  • Cancel the Pro subscriptionsorryapp_cancel_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.

FAQ

What can I do with Sorry in Claude or ChatGPT?

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.

Is this an official Sorry product?

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.

Can I connect Sorry to Claude or ChatGPT?

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.

What do I need to connect?

The login page asks for your Sorry API token. See Before you connect for where to find it.

Do I put my Sorry key or an Authorization header in the client config?

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.

How do you keep my Sorry credentials?

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.

Can the AI change my Sorry data?

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.

What does it cost?

The Free plan gives 50 tool calls / month. Pro costs $9/mo or $90/yr, with 10,000 tool calls / month. Pro+ costs $39/mo or $390/yr, with 100,000 tool calls / month. Each subscription covers this Sorry server only. Cancel any time: your paid plan then runs to the end of the paid period. Run sorryapp_usage_status to see how many calls you used.

How do I subscribe or cancel?

Ask the AI to run sorryapp_upgrade and choose Pro or Pro+, billed monthly or yearly: it returns a Stripe Checkout link. If you already have Pro, ask to change it to Pro+. After you confirm, your existing subscription changes in place, keeps its billing interval and charges the price difference for the rest of the period immediately. To cancel, run sorryapp_cancel_subscription. Your paid plan continues to the end of the paid period.

What if a Sorry tool that I need is missing?

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.

Which AI clients can I use?

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.

More Observability MCP servers

AirbrakeAll QuietAuvikAxcientBetter StackChecklyCronitorDead Man's SnitchDicksonOneFieldClimateHealthchecks.ioInstatusNodePingPulsewaySensoristSIGNL4Spike.shSquadcastStatus.ioStatusCakeStatusCastStatusHubStatuspageStatusPage.meStatusPalTemp Stickupdown.io

All Observability servers →