Statuspage MCP integration for AI agents.
Connect AI agents to Statuspage through 13 structured actions, including get automation email, create component, and delete component. Review authentication…
- ACTION CONTRACTS
- 13
- 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 Statuspage integration exposes
The Statuspage Agent App exposes 13 provider-backed actions for developer tools and communication work. Its current contract lets an authorized agent get the inbound automation email address for a statuspage page, create a component on a statuspage page, and delete a statuspage component. 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 Statuspage account, granted provider permissions, workspace policy, region, plan, and upstream API behavior.
VERIFIED ACTION SAMPLE
Real Statuspage capabilities.
Showing 12 of 13 actions. Risk labels are conservative signals based on operation names, not substitutes for provider documentation or runtime policy.
get_automation_emailREADGet the inbound automation email address for a Statuspage page.
INPUTS: pageId
create_componentWRITECreate a component on a Statuspage page.
INPUTS: pageId / component
delete_componentHIGH IMPACTDelete a Statuspage component.
INPUTS: pageId / componentId
create_incidentWRITECreate an incident on a Statuspage page.
INPUTS: pageId / incident
delete_incidentHIGH IMPACTDelete a Statuspage incident.
INPUTS: pageId / incidentId
get_incidentREADGet one Statuspage incident by id.
INPUTS: pageId / incidentId
get_pageREADGet one Statuspage page by id.
INPUTS: pageId
list_componentsREADList components for a Statuspage page.
INPUTS: pageId
list_eventsREADList activity events for a Statuspage page.
INPUTS: pageId / limit / page / q
list_incidentsREADList incidents for a Statuspage page.
INPUTS: pageId / limit / page / q
list_pagesREADList Statuspage pages available to the API token.
update_componentWRITEUpdate a Statuspage component.
INPUTS: pageId / componentId / component
INPUT CONTRACTS
Know what the action needs before it runs.
get_automation_email
pageIdREQUIRED- The Statuspage page identifier.
create_component
pageIdREQUIRED- The Statuspage page identifier.
componentREQUIRED- The component fields sent to Statuspage when creating a component.
delete_component
pageIdREQUIRED- The Statuspage page identifier.
componentIdREQUIRED- The Statuspage component identifier.
create_incident
pageIdREQUIRED- The Statuspage page identifier.
incidentREQUIRED- The incident fields sent to Statuspage when creating an incident.
PROVIDER-SPECIFIC WORKFLOWS
Jobs this Agent App can support
Inspect Get Automation Email
Get the inbound automation email address for a Statuspage page. Use this as a bounded discovery step, retain the returned identifier, and avoid expanding the read beyond the task's stated scope.
get_automation_emailControl Create Component
Create a component on a Statuspage 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 Statuspage 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 Statuspage with explicit limits
- Authorize Statuspage with API key and grant only the provider access required by the selected actions.
- 6 actions are change-capable by name. Confirm the target identity and material parameters before allowing a write.
- Treat `delete_component` and `delete_incident` 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 Statuspage rather than assuming unrestricted access.
- After a call, inspect the structured result and execution record before reporting that the Statuspage task completed successfully.
CONNECTION MODEL
API key
Statuspage API token sent with the Authorization: OAuth header. Create or copy tokens from your Statuspage account API info page.
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
- 7
- WRITE SIGNALS
- 4
- HIGH IMPACT
- 2
- 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 Statuspage.