--- title: "Atlassian Statuspage MCP server for AI agents - actionlake" description: "Give Claude 112 Atlassian Statuspage actions through one MCP server: subscribers, components. Your agent never holds the credential. 100,000 calls a month free." canonical: https://actionlake.com/connectors/atlassian-statuspage updated: 2026-10-23 --- 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 free](https://actionlake.com/console?start=sandbox) [See pricing](https://actionlake.com/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 ``` - 112 actions in one signed file - 38 read look, never change - 53 write create and update - 21 wait for a yes destructive, 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_key` Statuspage 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 call check { 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 2026[developer.statuspage.io](https://developer.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. - **38** read look, never change - **53** write create and update - **21** destructive wait 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. | Action | What it does | Effect | Same name in | | --- | --- | --- | --- | | `atlassian_statuspage.incidents.list` Get a list of incidents | Get a list of incidents. | read | `monitoring.incident.list` 19 connectors | | `atlassian_statuspage.components.list` Get a list of components | Get a list of components. | read | `monitoring.service.list` 12 connectors | | `atlassian_statuspage.subscribers.list` Get a list of subscribers | Get a list of subscribers. | read | `comm.audience_member.list` 23 connectors | | `atlassian_statuspage.organization_users.list` Get a list of users | Get a list of users. | read | `identity.user.list` 474 connectors | | `atlassian_statuspage.incidents.create` Create an incident | Create an incident. | write | `monitoring.incident.create` 13 connectors | | `atlassian_statuspage.components.create` Create a component | Create a component. | write | `monitoring.service.create` 11 connectors | | `atlassian_statuspage.organization_users.create` Create a user | Create a user. | write | `identity.user.create` 262 connectors | | `atlassian_statuspage.components.delete` Delete a component | Delete a component. | destructive | `monitoring.service.delete` 10 connectors | | `atlassian_statuspage.subscribers.get` Get a subscriber | Get a subscriber. | read | `comm.audience_member.get` 17 connectors | | `atlassian_statuspage.incident_updates.update` Update a previous incident update | Update a previous incident update. | write | `monitoring.incident_note.update` 12 connectors | | `atlassian_statuspage.pages.list` Get a list of pages | Get a list of pages. | read | this connector | | `atlassian_statuspage.subscribers.create` Create a subscriber | Create a subscriber. | write | this 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. Read read Which Atlassian Statuspage incidents are open, and how long has each been open? calls `atlassian_statuspage.incidents.list` 2. Write write Create an incident in Atlassian Statuspage. Show me exactly what you will send before you save it. calls `atlassian_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 component `atlassian_statuspage.components.delete` - Delete an incident `atlassian_statuspage.incidents.delete` - Delete a user `atlassian_statuspage.organization_users.delete` - Unsubscribe a subscriber `atlassian_statuspage.subscribers.delete` - Remove page access users from component `atlassian_statuspage.components.remove_page_access_users` - Remove page access groups from a component `atlassian_statuspage.components.remove_page_access_groups` - Unsubscribe a list of subscribers `atlassian_statuspage.subscribers.unsubscribe_many` - Delete a metric `atlassian_statuspage.metrics.delete` - Reset data for a metric `atlassian_statuspage.metrics.reset_data` - Delete Postmortem `atlassian_statuspage.postmortems.delete` - Delete a component group `atlassian_statuspage.component_groups.delete` - Delete a metric provider `atlassian_statuspage.metrics_providers.delete` - Delete page access user `atlassian_statuspage.page_access_users.delete` - Remove a page access group `atlassian_statuspage.page_access_groups.delete` - Unsubscribe an incident subscriber `atlassian_statuspage.incident_subscribers.delete` - Delete metric for page access user `atlassian_statuspage.page_access_user_metrics.delete` - Delete metrics for page access user `atlassian_statuspage.page_access_user_metrics.remove` - Remove component for page access user `atlassian_statuspage.page_access_user_components.delete` - Remove components for page access user `atlassian_statuspage.page_access_user_components.remove` - Remove a component from a page access group `atlassian_statuspage.page_access_group_components.delete` - Delete components for a page access group `atlassian_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. do atlassian_statuspage.components.delete confirm_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: "lead@example.com" }, { match: "atlassian_statuspage.incidents.delete", approver: "lead@example.com" }, { match: "atlassian_statuspage.organization_users.delete", approver: "lead@example.com" } ] } ``` 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. - 1 upstream call per action all 112 Atlassian Statuspage actions - 112 actions page each page of a long list is one call - 38 reads can be cached a cache hit costs nothing - 100,000 calls a month, free paid plans from US$49 a month for 250,000 [See pricing](https://actionlake.com/pricing) Action index ## Every Atlassian Statuspage action. 112 actions by area: the id your agent calls, what it does, and its effect. **Subscribers 12** - `atlassian_statuspage.subscribers.count` Get a count of subscribers by type read - `atlassian_statuspage.subscribers.create` Create a subscriber write - `atlassian_statuspage.subscribers.delete` Unsubscribe a subscriber destructive - `atlassian_statuspage.subscribers.get` Get a subscriber read - `atlassian_statuspage.subscribers.histogram_by_state` Get a histogram of subscribers by type and then state read - `atlassian_statuspage.subscribers.list` Get a list of subscribers read - `atlassian_statuspage.subscribers.list_unsubscribed` Get a list of unsubscribed subscribers read - `atlassian_statuspage.subscribers.reactivate` Reactivate a list of subscribers write - `atlassian_statuspage.subscribers.resend_confirmation` Resend confirmation to a subscriber write - `atlassian_statuspage.subscribers.resend_confirmation_many` Resend confirmations to a list of subscribers write - `atlassian_statuspage.subscribers.unsubscribe_many` Unsubscribe a list of subscribers destructive - `atlassian_statuspage.subscribers.update` Update a subscriber write **Components 11** - `atlassian_statuspage.components.add_page_access_groups` Add page access groups to a component write - `atlassian_statuspage.components.add_page_access_users` Add page access users to a component write - `atlassian_statuspage.components.create` Create a component write - `atlassian_statuspage.components.delete` Delete a component destructive - `atlassian_statuspage.components.get` Get a component read - `atlassian_statuspage.components.list` Get a list of components read - `atlassian_statuspage.components.remove_page_access_groups` Remove page access groups from a component destructive - `atlassian_statuspage.components.remove_page_access_users` Remove page access users from component destructive - `atlassian_statuspage.components.replace` Update a component write - `atlassian_statuspage.components.update` Update a component write - `atlassian_statuspage.components.uptime` Get uptime data for a component read **Incidents 10** - `atlassian_statuspage.incidents.create` Create an incident write - `atlassian_statuspage.incidents.delete` Delete an incident destructive - `atlassian_statuspage.incidents.get` Get an incident read - `atlassian_statuspage.incidents.list` Get a list of incidents read - `atlassian_statuspage.incidents.list_active_maintenance` Get a list of active maintenances read - `atlassian_statuspage.incidents.list_scheduled` Get a list of scheduled incidents read - `atlassian_statuspage.incidents.list_unresolved` Get a list of unresolved incidents read - `atlassian_statuspage.incidents.list_upcoming` Get a list of upcoming incidents read - `atlassian_statuspage.incidents.replace` Update an incident write - `atlassian_statuspage.incidents.update` Update an incident write **Metrics 8** - `atlassian_statuspage.metrics.add_data` Add data to a metric write - `atlassian_statuspage.metrics.add_data_many` Add data points to metrics write - `atlassian_statuspage.metrics.delete` Delete a metric destructive - `atlassian_statuspage.metrics.get` Get a metric read - `atlassian_statuspage.metrics.list` Get a list of metrics read - `atlassian_statuspage.metrics.replace` Update a metric write - `atlassian_statuspage.metrics.reset_data` Reset data for a metric destructive - `atlassian_statuspage.metrics.update` Update a metric write **Component groups 7** - `atlassian_statuspage.component_groups.create` Create a component group write - `atlassian_statuspage.component_groups.delete` Delete a component group destructive - `atlassian_statuspage.component_groups.get` Get a component group read - `atlassian_statuspage.component_groups.list` Get a list of component groups read - `atlassian_statuspage.component_groups.replace` Update a component group write - `atlassian_statuspage.component_groups.update` Update a component group write - `atlassian_statuspage.component_groups.uptime` Get uptime data for a component group read **Metrics providers 6** - `atlassian_statuspage.metrics_providers.create` Create a metric provider write - `atlassian_statuspage.metrics_providers.delete` Delete a metric provider destructive - `atlassian_statuspage.metrics_providers.get` Get a metric provider read - `atlassian_statuspage.metrics_providers.list` Get a list of metric providers read - `atlassian_statuspage.metrics_providers.replace` Update a metric provider write - `atlassian_statuspage.metrics_providers.update` Update a metric provider write **Page access group components 6** - `atlassian_statuspage.page_access_group_components.add` Replace components for a page access group write - `atlassian_statuspage.page_access_group_components.delete` Remove a component from a page access group destructive - `atlassian_statuspage.page_access_group_components.list` List components for a page access group read - `atlassian_statuspage.page_access_group_components.remove` Delete components for a page access group destructive - `atlassian_statuspage.page_access_group_components.replace` Add components to page access group write - `atlassian_statuspage.page_access_group_components.update` Add components to page access group write **Page access groups 6** - `atlassian_statuspage.page_access_groups.create` Create a page access group write - `atlassian_statuspage.page_access_groups.delete` Remove a page access group destructive - `atlassian_statuspage.page_access_groups.get` Get a page access group read - `atlassian_statuspage.page_access_groups.list` Get a list of page access groups read - `atlassian_statuspage.page_access_groups.replace` Update a page access group write - `atlassian_statuspage.page_access_groups.update` Update a page access group write **Page access user components 6** - `atlassian_statuspage.page_access_user_components.add` Replace components for page access user write - `atlassian_statuspage.page_access_user_components.delete` Remove component for page access user destructive - `atlassian_statuspage.page_access_user_components.list` Get components for page access user read - `atlassian_statuspage.page_access_user_components.remove` Remove components for page access user destructive - `atlassian_statuspage.page_access_user_components.replace` Add components for page access user write - `atlassian_statuspage.page_access_user_components.update` Add components for page access user write **Page access user metrics 6** - `atlassian_statuspage.page_access_user_metrics.add` Replace metrics for page access user write - `atlassian_statuspage.page_access_user_metrics.delete` Delete metric for page access user destructive - `atlassian_statuspage.page_access_user_metrics.list` Get metrics for page access user read - `atlassian_statuspage.page_access_user_metrics.remove` Delete metrics for page access user destructive - `atlassian_statuspage.page_access_user_metrics.replace` Add metrics for page access user write - `atlassian_statuspage.page_access_user_metrics.update` Add metrics for page access user write **Page access users 6** - `atlassian_statuspage.page_access_users.create` Add a page access user write - `atlassian_statuspage.page_access_users.delete` Delete page access user destructive - `atlassian_statuspage.page_access_users.get` Get page access user read - `atlassian_statuspage.page_access_users.list` Get a list of page access users read - `atlassian_statuspage.page_access_users.replace` Update page access user write - `atlassian_statuspage.page_access_users.update` Update page access user write **Incident subscribers 5** - `atlassian_statuspage.incident_subscribers.create` Create an incident subscriber write - `atlassian_statuspage.incident_subscribers.delete` Unsubscribe an incident subscriber destructive - `atlassian_statuspage.incident_subscribers.get` Get an incident subscriber read - `atlassian_statuspage.incident_subscribers.list` Get a list of incident subscribers read - `atlassian_statuspage.incident_subscribers.resend_confirmation` Resend confirmation to an incident subscriber write **Postmortems 5** - `atlassian_statuspage.postmortems.delete` Delete Postmortem destructive - `atlassian_statuspage.postmortems.get` Get Postmortem read - `atlassian_statuspage.postmortems.publish` Publish Postmortem write - `atlassian_statuspage.postmortems.revert` Revert Postmortem write - `atlassian_statuspage.postmortems.upsert` Create Postmortem write **Pages 4** - `atlassian_statuspage.pages.get` Get a page read - `atlassian_statuspage.pages.list` Get a list of pages read - `atlassian_statuspage.pages.replace` Update a page write - `atlassian_statuspage.pages.update` Update a page write **Organization users 3** - `atlassian_statuspage.organization_users.create` Create a user write - `atlassian_statuspage.organization_users.delete` Delete a user destructive - `atlassian_statuspage.organization_users.list` Get a list of users read **Status embed config 3** - `atlassian_statuspage.status_embed_config.get` Get status embed config settings read - `atlassian_statuspage.status_embed_config.replace` Update status embed config settings write - `atlassian_statuspage.status_embed_config.update` Update status embed config settings write **Incident templates 2** - `atlassian_statuspage.incident_templates.create` Create a template write - `atlassian_statuspage.incident_templates.list` Get a list of templates read **Incident updates 2** - `atlassian_statuspage.incident_updates.replace` Update a previous incident update write - `atlassian_statuspage.incident_updates.update` Update a previous incident update write **Metrics provider metrics 2** - `atlassian_statuspage.metrics_provider_metrics.create` Create a metric for a metric provider write - `atlassian_statuspage.metrics_provider_metrics.list` List metrics for a metric provider read **Organization permissions 2** - `atlassian_statuspage.organization_permissions.get` Get a user's permissions read - `atlassian_statuspage.organization_permissions.replace` Update a user's role permissions write 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 - [Google Cloud Monitoring 5](https://actionlake.com/connectors/google-cloud-monitoring) - [Fastly 3](https://actionlake.com/connectors/fastly) - [Databricks 3](https://actionlake.com/connectors/databricks) - [Databox 3](https://actionlake.com/connectors/databox) - [Cursor Admin and Cloud Agents 2](https://actionlake.com/connectors/cursor-admin-and-cloud-agents) - [MotherDuck 2](https://actionlake.com/connectors/motherduck) Joins with, on shared entities - [Rootly 3](https://actionlake.com/connectors/rootly) - [FireHydrant 3](https://actionlake.com/connectors/firehydrant) - [PagerDuty 3](https://actionlake.com/connectors/pagerduty) - [ilert 3](https://actionlake.com/connectors/ilert) - [Opsgenie 3](https://actionlake.com/connectors/opsgenie) - [Mitti 2](https://actionlake.com/connectors/mitti) Browse - [All Observability & analytics connectors](https://actionlake.com/connectors/category/observability-and-analytics) - [All connectors](https://actionlake.com/connectors) - [How actionlake compares](https://actionlake.com/compare) 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 free](https://actionlake.com/console?start=sandbox) [See pricing](https://actionlake.com/pricing) Start free - 100,000 calls/month, no card. No signup. Hard caps on every key. Cached answers are free. --- Source: https://actionlake.com/connectors/atlassian-statuspage More: https://actionlake.com/llms.txt