Instatus MCP integration for AI agents.
Connect AI agents to Instatus through 15 structured actions, including get component, create component, and delete component. Review authentication, inputs…
- ACTION CONTRACTS
- 15
- AUTHENTICATION
- API key
- SOURCE STATUS
- Provider-backed
CATALOG SOURCE REVIEWED AUGUST 23, 2026 / ACTION NAMES AND SCHEMAS DERIVED FROM WORKING MACHINES PROVIDER SOURCE
CAPABILITY PROFILE
What the Instatus integration exposes
The Instatus Agent App exposes 15 provider-backed actions for developer tools and productivity work. Its current contract lets an authorized agent get one instatus component by id, create one component on an instatus status page, and delete one instatus component by id. These operations are called through Working Machines as typed capabilities rather than through browser navigation or copied UI steps.
A connection uses API key. Before execution, the agent can inspect the selected action, its required fields, declared scopes, and expected output contract. Provider credentials remain inside the Working Machines runtime; the calling agent receives the capability and its structured result, not the underlying secret.
For reliable operation, start with the narrowest action that satisfies the task, resolve stable provider identifiers before changing state, and validate the returned object or status after execution. Availability still depends on the connected Instatus account, granted provider permissions, workspace policy, region, plan, and upstream API behavior.
VERIFIED ACTION SAMPLE
Real Instatus capabilities.
Showing 12 of 15 actions. Risk labels are conservative signals based on operation names, not substitutes for provider documentation or runtime policy.
get_componentREADGet one Instatus component by ID.
INPUTS: pageId / componentId
create_componentWRITECreate one component on an Instatus status page.
INPUTS: pageId / name / description / status / order
delete_componentHIGH IMPACTDelete one Instatus component by ID.
INPUTS: pageId / componentId
create_incidentWRITECreate one incident on an Instatus status page.
INPUTS: pageId / name / message / components / started
create_incident_updateWRITECreate one update on an Instatus incident.
INPUTS: pageId / incidentId / message / components / started
delete_incidentHIGH IMPACTDelete one Instatus incident by ID.
INPUTS: pageId / incidentId
delete_incident_updateHIGH IMPACTDelete one Instatus incident update by ID.
INPUTS: pageId / incidentId / incidentUpdateId
get_incidentREADGet one Instatus incident by ID.
INPUTS: pageId / incidentId
get_incident_updateREADGet one Instatus incident update by ID.
INPUTS: pageId / incidentId / incidentUpdateId
list_componentsREADList components on an Instatus status page.
INPUTS: pageId / page / perPage
list_incidentsREADList incidents on an Instatus status page.
INPUTS: pageId / page / perPage / statuses / excludedStatuses
list_status_pagesREADList Instatus status pages in the authenticated account.
INPUTS: page / perPage
INPUT CONTRACTS
Know what the action needs before it runs.
get_component
pageIdOPTIONAL- The ID of the Instatus status page.
componentIdOPTIONAL- The ID of the Instatus component.
create_component
pageIdREQUIRED- The ID of the Instatus status page.
nameREQUIRED- The name of the component.
descriptionOPTIONAL- The component description.
statusOPTIONAL- The status of an Instatus component.
orderOPTIONAL- The order of the component on the status page.
delete_component
pageIdOPTIONAL- The ID of the Instatus status page.
componentIdOPTIONAL- The ID of the Instatus component.
create_incident
pageIdREQUIRED- The ID of the Instatus status page.
nameREQUIRED- The name of the incident.
messageOPTIONAL- The initial incident message.
componentsOPTIONAL- The IDs of components affected by the incident.
startedOPTIONAL- The date and time when the incident started.
PROVIDER-SPECIFIC WORKFLOWS
Jobs this Agent App can support
Inspect Get Component
Get one Instatus component by ID. Use this as a bounded discovery step, retain the returned identifier, and avoid expanding the read beyond the task's stated scope.
get_componentControl Create Component
Create one component on an Instatus status page. Resolve the target first, present material changes for confirmation, and make retries idempotent where the provider supports it.
create_componentVerify with Get Incident
Get one Instatus incident by ID. Compare the returned provider state with the intended outcome and preserve stable IDs or canonical links in the run record.
get_incidentSAFETY BOUNDARY
Operate Instatus with explicit limits
- Authorize Instatus with API key and grant only the provider access required by the selected actions.
- 9 actions are change-capable by name. Confirm the target identity and material parameters before allowing a write.
- Treat `delete_component`, `delete_incident`, and `delete_incident_update` as high-impact operations and require an explicit approval boundary.
- No provider scope string is declared on the sampled actions. Verify the connected account's actual permissions in Instatus rather than assuming unrestricted access.
- After a call, inspect the structured result and execution record before reporting that the Instatus task completed successfully.
CONNECTION MODEL
API key
Instatus API key sent as a Bearer token in the Authorization header. Create or view it in User settings developer settings: https://dashboard.instatus.com/developer
Working Machines stores provider credentials behind the execution boundary. An agent can use an authorized connection identity, but catalog discovery alone does not reveal OAuth tokens, API keys, or provider secrets.
- READ SIGNALS
- 6
- WRITE SIGNALS
- 6
- HIGH IMPACT
- 3
- REVIEW SIGNALS
- 0
EVIDENCE AND AVAILABILITY
Provider reference
Action names, input fields, authentication types, and counts on this page are generated from the Working Machines provider catalog. Provider behavior, quotas, object semantics, account eligibility, and regional availability remain governed by Instatus.