Skip to content
actionlake
Start free

Connectors · Observability & analytics

Atlassian Statuspage MCP server for AI agents.

actionlake is an MCP gateway: one remote MCP server that connects Claude and other MCP clients to Atlassian Statuspage and the rest of your systems. It gives your agent 112 Atlassian Statuspage actions (38 reads, 53 writes and 21 that wait for a confirmation) and holds the Atlassian Statuspage credential itself, so the agent never does. It paces Atlassian Statuspage's limits and records every call.

Connect Atlassian Statuspage freeSee pricing

100,000 free calls a month. No card, no email, no password: press Start a free sandbox on the next screen and keep the key it shows you.

claude mcp add --transport http actionlake https://connect.actionlake.com/mcp
the first call
do {  action: "atlassian_statuspage.pages.list",  intent: "check which Atlassian Statuspage account is connected"}# Get a list of pages · read · 1 upstream call
  • 112actionsin one signed file
  • 38readlook, never change
  • 53writecreate and update
  • 21wait for a yesdestructive, confirmed first

Set up

Connect Atlassian Statuspage in three steps.

  1. 01

    Add actionlake to Claude.

    Run the command once in Claude Code; its consent page can create a free sandbox: 100,000 calls a month, no card. In the Claude app, add a custom connector with the URL below and paste your key on the consent page. Creating a new sandbox from the Claude app is not yet tested by us.

    https://connect.actionlake.com/mcp
  2. 02

    Connect Atlassian Statuspage.

    API key. No consent screen: your agent can connect it for you, but the key then passes through your chat. To keep it out of the model's context, paste it in the console instead. actionlake stores what you paste write-only, sealed under your tenant's key.

    • api_keyStatuspage API key: manage.statuspage.io > your avatar (bottom left) > API info
    account { op: "connections.requirements", service: "atlassian_statuspage" }
# free: exactly what to paste, and what is found for you
  3. 03

    Make the first call. Check before a write.

    Ask in plain words; Claude picks the action. Before anything changes, check validates the call and prices it, for free.

    do    { action: "atlassian_statuspage.pages.list" }# get a list of pages · read · 1 upstream callcheck { action: "atlassian_statuspage.incidents.create", input: { … } }# free: inputs, permissions, cost and confirmations, nothing sent

Atlassian Statuspage at a glance

Sign-in
API key. No consent screen: your agent can connect it for you, but the key then passes through your chat. To keep it out of the model's context, paste it in the console instead.
You provide
api_key
Limits we pace to
60 calls a minute, per connection
API covered
Statuspage REST API v1 (OpenAPI 3, embedded in developer.statuspage.io)api.statuspage.io
Built from
Atlassian Statuspage's documentation, read 23 October 2026developer.statuspage.io
Service file
Version 1.0.0, signed (Ed25519)
Cached reads
38 of 38 reads, for up to 5 minutes; a write clears what it affects
Shared entities
4, so ask can line Atlassian Statuspage up with your other systems
Data
Processed and stored in Sydney, Australia. No US region yet

Capabilities

What an AI agent can do in Atlassian Statuspage.

112 actions in 20 areas. Every one carries its effect, so a key can allow the reads and hold the rest.

  • 38readlook, never change
  • 53writecreate and update
  • 21destructivewait for a confirmation

  1. Subscribers

    12

    5 read · 5 write · 2 destructive

    Get a list of subscribers · Get a subscriber · Update a subscriber · Create a subscriber

  2. Components

    11

    3 read · 5 write · 3 destructive

    Get a list of components · Create a component · Get a component · Update a component

  3. Incidents

    10

    6 read · 3 write · 1 destructive

    Get a list of incidents · Create an incident · Get an incident · Update an incident

  4. Metrics

    8

    2 read · 4 write · 2 destructive

    Add data to a metric · Add data points to metrics · Get a list of metrics · Get a metric

  5. Component groups

    7

    3 read · 3 write · 1 destructive

    Create a component group · Get a list of component groups · Get a component group · Update a component group

  6. Metrics providers

    6

    2 read · 3 write · 1 destructive

    Create a metric provider · Get a list of metric providers · Get a metric provider · Update a metric provider

  7. Page access group components

    6

    1 read · 3 write · 2 destructive

    Replace components for a page access group · List components for a page access group · Add components to page access group · Add components to page access group

  8. Page access groups

    6

    2 read · 3 write · 1 destructive

    Create a page access group · Get a list of page access groups · Get a page access group · Update a page access group

12 more areas · 46 actions
  • Page access user components 6
  • Page access user metrics 6
  • Page access users 6
  • Incident subscribers 5
  • Postmortems 5
  • Pages 4
  • Organization users 3
  • Status embed config 3
  • Incident templates 2
  • Incident updates 2
  • Metrics provider metrics 2
  • Organization permissions 2

Top actions

The Atlassian Statuspage API, shaped for agents.

The ids your agent types, what each does, and the one name it shares with other systems. 17 of Atlassian Statuspage's 17 action names are shared with at least one other connector, so an agent learns them once.

ActionWhat it doesEffectSame name in
atlassian_statuspage.incidents.listGet a list of incidentsGet a list of incidents.readmonitoring.incident.list19 connectors
atlassian_statuspage.components.listGet a list of componentsGet a list of components.readmonitoring.service.list12 connectors
atlassian_statuspage.subscribers.listGet a list of subscribersGet a list of subscribers.readcomm.audience_member.list23 connectors
atlassian_statuspage.organization_users.listGet a list of usersGet a list of users.readidentity.user.list474 connectors
atlassian_statuspage.incidents.createCreate an incidentCreate an incident.writemonitoring.incident.create13 connectors
atlassian_statuspage.components.createCreate a componentCreate a component.writemonitoring.service.create11 connectors
atlassian_statuspage.organization_users.createCreate a userCreate a user.writeidentity.user.create262 connectors
atlassian_statuspage.components.deleteDelete a componentDelete a component.destructivemonitoring.service.delete10 connectors
atlassian_statuspage.subscribers.getGet a subscriberGet a subscriber.readcomm.audience_member.get17 connectors
atlassian_statuspage.incident_updates.updateUpdate a previous incident updateUpdate a previous incident update.writemonitoring.incident_note.update12 connectors
atlassian_statuspage.pages.listGet a list of pagesGet a list of pages.readthis connector
atlassian_statuspage.subscribers.createCreate a subscriberCreate a subscriber.writethis connector

Try it

Prompts to paste into Claude.

Each one names the Atlassian Statuspage actions it will call, so you know what it reads and what it changes before you send it.

  1. Readread

    Which Atlassian Statuspage incidents are open, and how long has each been open?

    callsatlassian_statuspage.incidents.list

  2. Writewrite

    Create an incident in Atlassian Statuspage. Show me exactly what you will send before you save it.

    callsatlassian_statuspage.incidents.create

Governance for Atlassian Statuspage

Destructive actions wait for a yes.

21 Atlassian Statuspage actions are destructive. These are all of them:

  • Delete a componentatlassian_statuspage.components.delete
  • Delete an incidentatlassian_statuspage.incidents.delete
  • Delete a useratlassian_statuspage.organization_users.delete
  • Unsubscribe a subscriberatlassian_statuspage.subscribers.delete
  • Remove page access users from componentatlassian_statuspage.components.remove_page_access_users
  • Remove page access groups from a componentatlassian_statuspage.components.remove_page_access_groups
  • Unsubscribe a list of subscribersatlassian_statuspage.subscribers.unsubscribe_many
  • Delete a metricatlassian_statuspage.metrics.delete
  • Reset data for a metricatlassian_statuspage.metrics.reset_data
  • Delete Postmortematlassian_statuspage.postmortems.delete
  • Delete a component groupatlassian_statuspage.component_groups.delete
  • Delete a metric provideratlassian_statuspage.metrics_providers.delete
  • Delete page access useratlassian_statuspage.page_access_users.delete
  • Remove a page access groupatlassian_statuspage.page_access_groups.delete
  • Unsubscribe an incident subscriberatlassian_statuspage.incident_subscribers.delete
  • Delete metric for page access useratlassian_statuspage.page_access_user_metrics.delete
  • Delete metrics for page access useratlassian_statuspage.page_access_user_metrics.remove
  • Remove component for page access useratlassian_statuspage.page_access_user_components.delete
  • Remove components for page access useratlassian_statuspage.page_access_user_components.remove
  • Remove a component from a page access groupatlassian_statuspage.page_access_group_components.delete
  • Delete components for a page access groupatlassian_statuspage.page_access_group_components.remove

A destructive action runs only with confirm: true. Under the human policy the agent cannot confirm for itself: the run stops until a named person approves, in the console or from a signed link in an email. The cap on a key is refused before the call is sent, never after.

doatlassian_statuspage.components.deleteconfirm_policy: human

Delete a component?

intent: the user asked me to delete a component

run suspended · waiting for a named person · key atlassian-statuspage-agent cannot confirm itself
In the console, or from an emailed signed link.
a key for this connector
account {  op: "keys.create", name: "atlassian-statuspage-agent",  allowed_actions: ["atlassian_statuspage.*"], cap_calls: 2000,  confirm_policy: "human_for_writes",  approval_rules: [    { match: "atlassian_statuspage.components.delete", approver: "[email protected]" },    { match: "atlassian_statuspage.incidents.delete", approver: "[email protected]" },    { match: "atlassian_statuspage.organization_users.delete", approver: "[email protected]" }  ]}
Illustrative. Scoped to Atlassian Statuspage only, capped at 2,000 upstream calls, every write confirmed, and the destructive ones approved by a named person.

Cost

What Atlassian Statuspage costs on actionlake.

Every Atlassian Statuspage action is one upstream call, the only thing actionlake bills. Searching, check, cost, account and any call Atlassian Statuspage refused with 401, 403, 429 or a 5xx are free. Paid plans start at US$49 a month for 250,000 calls, with overage from US$0.30 down to US$0.18 per 1,000.

  • 1upstream call per actionall 112 Atlassian Statuspage actions
  • 112actions pageeach page of a long list is one call
  • 38reads can be cacheda cache hit costs nothing
  • 100,000calls a month, freepaid plans from US$49 a month for 250,000

See pricing

Action index

Every Atlassian Statuspage action.

112 actions by area: the id your agent calls, what it does, and its effect.

Subscribers12
  • atlassian_statuspage.subscribers.countGet a count of subscribers by typeread
  • atlassian_statuspage.subscribers.createCreate a subscriberwrite
  • atlassian_statuspage.subscribers.deleteUnsubscribe a subscriberdestructive
  • atlassian_statuspage.subscribers.getGet a subscriberread
  • atlassian_statuspage.subscribers.histogram_by_stateGet a histogram of subscribers by type and then stateread
  • atlassian_statuspage.subscribers.listGet a list of subscribersread
  • atlassian_statuspage.subscribers.list_unsubscribedGet a list of unsubscribed subscribersread
  • atlassian_statuspage.subscribers.reactivateReactivate a list of subscriberswrite
  • atlassian_statuspage.subscribers.resend_confirmationResend confirmation to a subscriberwrite
  • atlassian_statuspage.subscribers.resend_confirmation_manyResend confirmations to a list of subscriberswrite
  • atlassian_statuspage.subscribers.unsubscribe_manyUnsubscribe a list of subscribersdestructive
  • atlassian_statuspage.subscribers.updateUpdate a subscriberwrite
Components11
  • atlassian_statuspage.components.add_page_access_groupsAdd page access groups to a componentwrite
  • atlassian_statuspage.components.add_page_access_usersAdd page access users to a componentwrite
  • atlassian_statuspage.components.createCreate a componentwrite
  • atlassian_statuspage.components.deleteDelete a componentdestructive
  • atlassian_statuspage.components.getGet a componentread
  • atlassian_statuspage.components.listGet a list of componentsread
  • atlassian_statuspage.components.remove_page_access_groupsRemove page access groups from a componentdestructive
  • atlassian_statuspage.components.remove_page_access_usersRemove page access users from componentdestructive
  • atlassian_statuspage.components.replaceUpdate a componentwrite
  • atlassian_statuspage.components.updateUpdate a componentwrite
  • atlassian_statuspage.components.uptimeGet uptime data for a componentread
Incidents10
  • atlassian_statuspage.incidents.createCreate an incidentwrite
  • atlassian_statuspage.incidents.deleteDelete an incidentdestructive
  • atlassian_statuspage.incidents.getGet an incidentread
  • atlassian_statuspage.incidents.listGet a list of incidentsread
  • atlassian_statuspage.incidents.list_active_maintenanceGet a list of active maintenancesread
  • atlassian_statuspage.incidents.list_scheduledGet a list of scheduled incidentsread
  • atlassian_statuspage.incidents.list_unresolvedGet a list of unresolved incidentsread
  • atlassian_statuspage.incidents.list_upcomingGet a list of upcoming incidentsread
  • atlassian_statuspage.incidents.replaceUpdate an incidentwrite
  • atlassian_statuspage.incidents.updateUpdate an incidentwrite
Metrics8
  • atlassian_statuspage.metrics.add_dataAdd data to a metricwrite
  • atlassian_statuspage.metrics.add_data_manyAdd data points to metricswrite
  • atlassian_statuspage.metrics.deleteDelete a metricdestructive
  • atlassian_statuspage.metrics.getGet a metricread
  • atlassian_statuspage.metrics.listGet a list of metricsread
  • atlassian_statuspage.metrics.replaceUpdate a metricwrite
  • atlassian_statuspage.metrics.reset_dataReset data for a metricdestructive
  • atlassian_statuspage.metrics.updateUpdate a metricwrite
Component groups7
  • atlassian_statuspage.component_groups.createCreate a component groupwrite
  • atlassian_statuspage.component_groups.deleteDelete a component groupdestructive
  • atlassian_statuspage.component_groups.getGet a component groupread
  • atlassian_statuspage.component_groups.listGet a list of component groupsread
  • atlassian_statuspage.component_groups.replaceUpdate a component groupwrite
  • atlassian_statuspage.component_groups.updateUpdate a component groupwrite
  • atlassian_statuspage.component_groups.uptimeGet uptime data for a component groupread
Metrics providers6
  • atlassian_statuspage.metrics_providers.createCreate a metric providerwrite
  • atlassian_statuspage.metrics_providers.deleteDelete a metric providerdestructive
  • atlassian_statuspage.metrics_providers.getGet a metric providerread
  • atlassian_statuspage.metrics_providers.listGet a list of metric providersread
  • atlassian_statuspage.metrics_providers.replaceUpdate a metric providerwrite
  • atlassian_statuspage.metrics_providers.updateUpdate a metric providerwrite
Page access group components6
  • atlassian_statuspage.page_access_group_components.addReplace components for a page access groupwrite
  • atlassian_statuspage.page_access_group_components.deleteRemove a component from a page access groupdestructive
  • atlassian_statuspage.page_access_group_components.listList components for a page access groupread
  • atlassian_statuspage.page_access_group_components.removeDelete components for a page access groupdestructive
  • atlassian_statuspage.page_access_group_components.replaceAdd components to page access groupwrite
  • atlassian_statuspage.page_access_group_components.updateAdd components to page access groupwrite
Page access groups6
  • atlassian_statuspage.page_access_groups.createCreate a page access groupwrite
  • atlassian_statuspage.page_access_groups.deleteRemove a page access groupdestructive
  • atlassian_statuspage.page_access_groups.getGet a page access groupread
  • atlassian_statuspage.page_access_groups.listGet a list of page access groupsread
  • atlassian_statuspage.page_access_groups.replaceUpdate a page access groupwrite
  • atlassian_statuspage.page_access_groups.updateUpdate a page access groupwrite
Page access user components6
  • atlassian_statuspage.page_access_user_components.addReplace components for page access userwrite
  • atlassian_statuspage.page_access_user_components.deleteRemove component for page access userdestructive
  • atlassian_statuspage.page_access_user_components.listGet components for page access userread
  • atlassian_statuspage.page_access_user_components.removeRemove components for page access userdestructive
  • atlassian_statuspage.page_access_user_components.replaceAdd components for page access userwrite
  • atlassian_statuspage.page_access_user_components.updateAdd components for page access userwrite
Page access user metrics6
  • atlassian_statuspage.page_access_user_metrics.addReplace metrics for page access userwrite
  • atlassian_statuspage.page_access_user_metrics.deleteDelete metric for page access userdestructive
  • atlassian_statuspage.page_access_user_metrics.listGet metrics for page access userread
  • atlassian_statuspage.page_access_user_metrics.removeDelete metrics for page access userdestructive
  • atlassian_statuspage.page_access_user_metrics.replaceAdd metrics for page access userwrite
  • atlassian_statuspage.page_access_user_metrics.updateAdd metrics for page access userwrite
Page access users6
  • atlassian_statuspage.page_access_users.createAdd a page access userwrite
  • atlassian_statuspage.page_access_users.deleteDelete page access userdestructive
  • atlassian_statuspage.page_access_users.getGet page access userread
  • atlassian_statuspage.page_access_users.listGet a list of page access usersread
  • atlassian_statuspage.page_access_users.replaceUpdate page access userwrite
  • atlassian_statuspage.page_access_users.updateUpdate page access userwrite
Incident subscribers5
  • atlassian_statuspage.incident_subscribers.createCreate an incident subscriberwrite
  • atlassian_statuspage.incident_subscribers.deleteUnsubscribe an incident subscriberdestructive
  • atlassian_statuspage.incident_subscribers.getGet an incident subscriberread
  • atlassian_statuspage.incident_subscribers.listGet a list of incident subscribersread
  • atlassian_statuspage.incident_subscribers.resend_confirmationResend confirmation to an incident subscriberwrite
Postmortems5
  • atlassian_statuspage.postmortems.deleteDelete Postmortemdestructive
  • atlassian_statuspage.postmortems.getGet Postmortemread
  • atlassian_statuspage.postmortems.publishPublish Postmortemwrite
  • atlassian_statuspage.postmortems.revertRevert Postmortemwrite
  • atlassian_statuspage.postmortems.upsertCreate Postmortemwrite
Pages4
  • atlassian_statuspage.pages.getGet a pageread
  • atlassian_statuspage.pages.listGet a list of pagesread
  • atlassian_statuspage.pages.replaceUpdate a pagewrite
  • atlassian_statuspage.pages.updateUpdate a pagewrite
Organization users3
  • atlassian_statuspage.organization_users.createCreate a userwrite
  • atlassian_statuspage.organization_users.deleteDelete a userdestructive
  • atlassian_statuspage.organization_users.listGet a list of usersread
Status embed config3
  • atlassian_statuspage.status_embed_config.getGet status embed config settingsread
  • atlassian_statuspage.status_embed_config.replaceUpdate status embed config settingswrite
  • atlassian_statuspage.status_embed_config.updateUpdate status embed config settingswrite
Incident templates2
  • atlassian_statuspage.incident_templates.createCreate a templatewrite
  • atlassian_statuspage.incident_templates.listGet a list of templatesread
Incident updates2
  • atlassian_statuspage.incident_updates.replaceUpdate a previous incident updatewrite
  • atlassian_statuspage.incident_updates.updateUpdate a previous incident updatewrite
Metrics provider metrics2
  • atlassian_statuspage.metrics_provider_metrics.createCreate a metric for a metric providerwrite
  • atlassian_statuspage.metrics_provider_metrics.listList metrics for a metric providerread
Organization permissions2
  • atlassian_statuspage.organization_permissions.getGet a user's permissionsread
  • atlassian_statuspage.organization_permissions.replaceUpdate a user's role permissionswrite

Questions

The Atlassian Statuspage MCP server, answered.

Is there an Atlassian Statuspage MCP server for Claude?

Yes. actionlake is an MCP gateway: a remote MCP server that gives Claude, or another MCP client, 112 Atlassian Statuspage actions across subscribers, components, incidents and metrics, through the same eight tools it uses for every other connector. actionlake is independent; it is not made or endorsed by Atlassian Statuspage.

What do I need to connect Atlassian Statuspage?

Statuspage API key: manage.statuspage.io > your avatar (bottom left) > API info. The free call account { op: "connections.requirements", service: "atlassian_statuspage" } lists exactly what to paste.

Can an AI agent delete or change things in Atlassian Statuspage?

Only if its key allows it, and only with an explicit confirmation. 21 Atlassian Statuspage actions are destructive, including delete a component, delete an incident and delete a user. Each runs only with confirm: true. Under the human confirm policy, or an approval rule on the key, the run waits until a named person approves it.

Will an AI agent use up my Atlassian Statuspage API limit?

actionlake paces every call to the limits in the Atlassian Statuspage service file: 60 calls a minute per connection. Repeated reads are answered from cache (38 Atlassian Statuspage actions can be), which never reaches Atlassian Statuspage.

What does an Atlassian Statuspage action cost?

One upstream call, the only unit actionlake bills. A list that pages bills one call per page (112 Atlassian Statuspage actions page). Cache hits, searches, dry runs and calls Atlassian Statuspage refused with 401, 403, 429 or a 5xx are free. The Free plan includes 100,000 calls a month with no card. Paid plans start at US$49 a month for 250,000 calls, with overage from US$0.30 down to US$0.18 per 1,000.

Which Atlassian Statuspage API does it cover?

The Statuspage REST API v1 (OpenAPI 3, embedded in developer.statuspage.io) at api.statuspage.io. It is built from Atlassian Statuspage's documentation as read on 23 October 2026. 112 actions in 20 areas, each one in the signed service file (version 1.0.0).

Does actionlake keep my Atlassian Statuspage data, and where?

actionlake processes and stores data in Sydney, Australia; there is no US region yet. Reads may be cached for up to 5 minutes, and a write clears the reads it affects. Each run's request and response is kept, sealed, for your plan's trace window: 1 day on Free, 3 days on Starter, 7 days on Pro, 14 days on Team, 30 days on Business and 30 days on Enterprise. Your Atlassian Statuspage credential is sealed under your tenant's key, never logged and never returned. Your traffic is not used to train models.

Which AI clients can use it?

Claude Code, tested by us end to end, and the Claude app as a custom connector, tested by us with an existing key. Other MCP clients that support remote servers over Streamable HTTP (MCP revisions 2025-06-18 and 2025-11-25) and OAuth dynamic client registration, or a bearer header, should connect the same way; we have not tested them. Or plain REST, under the same action names.

More connectors like Atlassian Statuspage

Shares the most action names with

Joins with, on shared entities

Browse

actionlake is independent. It is not made or endorsed by Atlassian Statuspage; the name is the vendor's own. Counts are from the Atlassian Statuspage service file, version 1.0.0.

Give your agent Atlassian Statuspage today.

Connect Atlassian Statuspage freeSee pricing

Start free - 100,000 calls/month, no card. No signup. Hard caps on every key. Cached answers are free.