Base44
Build and edit Base44 apps from an AI assistant, and query data your app's users submit.
Query incidents, alerts, on-call schedules and telemetry, and declare or update incidents.
Opens Agent Studio, where connecting is one click. The connector URL below works in any MCP client.
Paste it into any MCP client. Setup docs
The incident.io MCP server connects incident.io to Claude, ChatGPT, Cursor and any MCP-compatible agent. It covers incidents, alerts, escalations, on-call schedules, catalog, follow-ups and connected observability data — so a responder asks who is on call, or declares an incident, in the conversation. Sign-in is OAuth, or an API key for automation.
Verified connector
Listed by Anthropic as a partner connector in its Connectors Directory.
Connection checked by Agentman on .
Anthropic states this reflects the level of review a connector received, not a security audit.
Tool names from Anthropic's directory listing. This server requires sign-in, so we could not read tool descriptions or parameter schemas.
incident_create, incident_update and escalation_respond are documented as creating an incident, changing its status and severity, and acknowledging or declining a page. An assistant that misreads a request here pages a human or declares an incident that did not happen. Approve tool calls deliberately on this server.ask_incident is not a read despite the name. incident.io documents it as an AI agent for incident investigation and management actions, so grouping it with the other two ask tools as a query interface would be wrong.readOnlyHint or destructiveHint on any tool. Every read/write label on this page is incident.io's prose, not the protocol's machine-readable annotation — a client that surfaces annotations to decide when to ask permission has nothing from us to go on.ask_telemetry queries the observability platforms wired into incident.io Investigations; with none connected, there is nothing for it to read.authorization_servers and resource and no scopes_supported field — matching incident.io's own instruction to leave the scopes box empty. So the consent screen, not a scope string, is where you see what you are granting. Usefully for client authors, incident.io serves that descriptor at every path a client might try: the nested form under /mcp its own challenge header names, the RFC 9728 form with the well-known segment inserted before the resource path, and the bare host root all returned HTTP 200 with identical bodies on 2026-08-18.follow_up_update, follow_up_stats and resource_list as unconfirmed until you list tools against a live session.Yes. incident.io's documentation lists tools that create an incident, update its status and severity, acknowledge or decline a page, and create follow-ups. Its own example prompts include creating a P2 incident and moving one to resolved. This is a connector that acts on live production incident data, not a read-only reporting view.
Two ways, depending on who is connecting. incident.io documents OAuth for people using an AI assistant, where the client discovers the configuration from the server URL, and API keys for automated pipelines. We confirmed the requirement on 2026-08-18: an anonymous request returned HTTP 401 with a bearer authentication challenge.
Exactly what the authorising user can see. incident.io states an OAuth connection acts as the person who approves it, so it sees and acts on only what that user can. The company recommends approving with a dedicated service account. API keys instead carry the permissions you grant them at creation.
Twenty-eight days for OAuth. incident.io documents that the connection lasts 28 days, after which you re-approve it in the browser. API keys behave differently: incident.io states they authenticate as a service actor rather than a specific user and do not expire until you delete them, which suits unattended automation.
Because its redirect domain is not allowed yet. incident.io documents that built-in clients such as Claude, ChatGPT and Cursor are trusted automatically, while any other client's redirect host must first be added by an admin under Settings, up to five domains. The error names the exact domain to add.
Yes, through the observability platforms you have already connected to incident.io Investigations. incident.io names Datadog, Grafana, Splunk, Honeycomb, Elasticsearch and GCP Cloud Logging among them, and documents querying logs, metrics, traces and dashboards for ordinary debugging, not only during an active incident.
No, and installing it changes which server you use. incident.io states the macOS app ships a local MCP server providing all the same tools plus richer investigation support, with no extra setup. The remote server documented here exists for people connecting from a browser, ChatGPT, or automated agent pipelines instead.
.md variant incident.io publishes for AI clients). Its robots.txt carries Content-Signal: ai-train=yes, search=yes, ai-input=yes — the publisher expressly permits AI synthesis of this content · retrieved 2026-08-18initialize against https://mcp.incident.io/mcp — HTTP 401, response body no bearer token, with WWW-Authenticate: Bearer resource_metadata=... naming the server's own protected-resource descriptor (2026-08-18) · retrieved 2026-08-18scopes_supported field (retrieved 2026-08-18) · retrieved 2026-08-18S256 code challenges, dynamic client registration, token endpoint auth method none (retrieved 2026-08-18) · retrieved 2026-08-18partner tier, endpoint and categories above are read from our committed directory snapshot dated 2026-08-16; the directory page itself blocks automated fetches, so we did not retrieve it directly · retrieved 2026-08-16https://incident.io/privacy 307-redirects here; both checked 2026-08-18) · retrieved 2026-08-18Connect incident.io once and your agents call these tools on their own: on a schedule, in a workflow, with nobody at the keyboard.