Atlassian Statuspage (BYOK)

Atlassian Statuspage (BYOK) — connector documentation

• MCP endpoint: https://byok-statuspage.connectorbay.com/mcp
• REST API: POST https://byok-statuspage.connectorbay.com/v1/tools/{tool_name}, described by the OpenAPI 3.1 spec at https://byok-statuspage.connectorbay.com/openapi.json
• Transport: Streamable HTTP, stateless, MCP specification 2025-06-18 or later
• Authentication: your own Atlassian Statuspage Statuspage API key, sent in the X-Upstream-Key header of every request (never stored, logged or cached)
• Health: https://byok-statuspage.connectorbay.com/health · Tool schemas: https://byok-statuspage.connectorbay.com/tools.json
• Publisher: Unify Dynamics LLC · connectorbay.com/byok-statuspage · agent@connectorbay.com

What Atlassian Statuspage (BYOK) is for

Atlassian Statuspage (BYOK) lets an AI assistant read your own Atlassian Statuspage data through the Atlassian Statuspage API with a key you supply (Statuspage API key). Read-only: 10 tools (list_pages, list_components, list_component_groups, get_component_uptime, list_incidents, list_unresolved_incidents, list_scheduled_maintenances, get_incident, list_metrics, count_subscribers). The BYOK key travels with each request, is used for that one call only and is never stored, logged or cached; it is only ever sent to api.statuspage.io. Unofficial connector by Unify Dynamics LLC: not affiliated with, endorsed by or sponsored by Atlassian Statuspage. Atlassian Statuspage and its logos are trademarks of their owners and are used only to say which service the connector works with.

Ask your assistant things like:

• "Which Statuspage status pages do I have?"
• "Is anything degraded on my Statuspage?"
• "How are my Statuspage components grouped?"
• "What was the uptime of my Statuspage component last month?"
• "What incidents did my Statuspage have recently?"
• "Are there any open incidents on my Statuspage?"

What it does

• list_pages: List the status pages of the account with name, subdomain, custom domain, URL, time zone and last update. The id is needed by the other tools.
• list_components: List the components of a status page (services shown on it) with current status: operational, under_maintenance, degraded_performance, partial_outage or major_outage.
• list_component_groups: List the component groups of a status page with name, description and the ids of their components.
• get_component_uptime: Get the uptime percentage and outage minutes of one component over a date range (default: since its start date or the last 90 days).
• list_incidents: List incidents of a status page, newest first, with status (investigating, identified, monitoring, resolved), impact, timestamps and short link. Optional text search; 100 per page at most.
• list_unresolved_incidents: List incidents of a status page that are not resolved yet, with status, impact and timestamps.
• list_scheduled_maintenances: List scheduled maintenances of a status page with planned start and end.
• get_incident: Get one incident by id: name, status, impact, timestamps and short link.
• list_metrics: List the metrics shown on a status page with name, suffix, last data time and backfill state.
• count_subscribers: Count the subscribers of a status page by channel type (email, sms, slack, webhook, teams, integration_partner).

BYOK key

You bring your own Atlassian Statuspage Statuspage API key (https://manage.statuspage.io/login). Your assistant sends it in the X-Upstream-Key header with each request. ConnectorBay uses it for that one call only: it is never stored, logged or cached, never shown in an answer, and it is only sent to api.statuspage.io over https, with no redirects followed. Create a key with the fewest permissions the tools need (read-only if the provider offers it), and revoke it at the provider whenever you like.

Data sources

• https://developer.statuspage.io/ (the API this connector calls, with a BYOK key)

Live from the Atlassian Statuspage API (api.statuspage.io) with a BYOK key; documentation: https://developer.statuspage.io/. Endpoints checked against that documentation on 2026-10-16.

What it is not

Unofficial connector by Unify Dynamics LLC: not affiliated with, endorsed by or sponsored by Atlassian Statuspage. Atlassian Statuspage and its logos are trademarks of their owners and are used only to say which service the connector works with. It is read-only: it never creates, changes, sends or deletes anything in your Atlassian Statuspage account.

Built for: Worldwide. Languages: English.

Atlassian Statuspage (BYOK) — Privacy Policy

Effective 24 October 2026. Unify Dynamics LLC ("we", "us"), Menlo Park, California.

What Atlassian Statuspage (BYOK) is. Atlassian Statuspage (BYOK) is a connector (an MCP server and REST API) that an AI assistant calls on your behalf to read your own Atlassian Statuspage data: Read your Atlassian Statuspage pages, components, component groups, incidents, maintenances and uptime with BYOK. You bring your own Atlassian Statuspage Statuspage API key; the assistant sends it to us with each request.

BYOK key. The key you supply is used to make the one Atlassian Statuspage call you asked for. Our application does not store it, write it to a log, put it in a cache, or share it. It is sent only to api.statuspage.io, over https, and is removed from any text we return to you or your assistant. We do not follow redirects with your key. If Atlassian Statuspage rejects it, we say so without repeating it.

What we receive. The arguments of each tool call, the BYOK key (for that call only), the technical headers needed to serve the request (an IP address or a client identifier supplied by the assistant) and standard server logs. What Atlassian Statuspage receives. The request we make on your behalf, including the key and the arguments, under Atlassian Statuspage's own terms and privacy policy. Atlassian Statuspage acts at your direction and is the only recipient of the data of your request besides our hosting provider.

What we return. The answer Atlassian Statuspage gives for your request, trimmed to the fields the tool documents. We do not keep it: it is returned to your assistant and not stored, cached or used to train anything.

What we do not do. We do not build a profile, sell or share personal information, or keep your Atlassian Statuspage data. Rate-limit counters (a client identifier and timestamps) are held in memory for at most 24 hours. Hosting access logs (IP addresses, request paths and status codes) are kept for up to 30 days for security and abuse prevention; our application adds no request headers or bodies to them.

Sub-processors. Atlassian Statuspage (the API you call with a BYOK key, at your direction). Hosting: Vercel (United States regions).

Your rights. Because we store no personal data beyond short-lived logs, requests to access, correct or delete data are usually satisfied automatically; you can still contact agent@connectorbay.com and we will respond within 30 days. Revoke your key at Atlassian Statuspage at any time to end all access.

Children. Atlassian Statuspage (BYOK) is a general-audience service operated by the adult using the assistant, under Atlassian Statuspage's own age rules.

Changes. We will post changes here with a new effective date.

Atlassian Statuspage (BYOK) — Terms of Service

Effective 24 October 2026. These terms govern use of the Atlassian Statuspage (BYOK) connector ("the Service") operated by Unify Dynamics LLC ("we", "us").

1. The Service. Atlassian Statuspage (BYOK) provides: Read your Atlassian Statuspage pages, components, component groups, incidents, maintenances and uptime with BYOK. It is accessed through an AI assistant or directly over MCP or HTTP, and is read-only.
2. Your own key, your own account. You must use your own Atlassian Statuspage credentials and only access data you are allowed to access. Atlassian Statuspage's terms apply to your use of Atlassian Statuspage; you are responsible for complying with them, including any rate limits and permitted uses. Do not share a key you do not own.
3. Independent. Unofficial connector by Unify Dynamics LLC: not affiliated with, endorsed by or sponsored by Atlassian Statuspage. Atlassian Statuspage and its logos are trademarks of their owners and are used only to say which service the connector works with.
4. No advice, no guarantees. Output is the data Atlassian Statuspage returns, lightly trimmed; it may be incomplete, delayed or changed by Atlassian Statuspage. Check important facts at the source.
5. Read-only. The Service does not create, change, send or delete anything in your Atlassian Statuspage account.
6. Acceptable use. Automated use within the published rate limits is welcome. Do not use the Service to access data you are not entitled to, to circumvent Atlassian Statuspage's controls, or to attack any system.
7. Availability. The Service is provided "as is" without warranty. We may change, limit or discontinue it at any time; Atlassian Statuspage may change or end its API at any time.
8. Data. Our Privacy Policy describes what we process. In short: the BYOK key is used for the one call and not stored or logged.
9. Pro keys. Optional ConnectorBay Pro API keys are issued at our discretion and are separate from your Atlassian Statuspage key.
10. Liability. To the fullest extent permitted by law, Unify Dynamics LLC is not liable for any loss arising from use of or reliance on the Service, including any action Atlassian Statuspage takes on your account. Our total liability is limited to US $100.
11. Governing law. California law; venue in San Mateo County, California.
12. Contact. Unify Dynamics LLC · agent@connectorbay.com · https://connectorbay.com/byok-statuspage

Atlassian Statuspage (BYOK) support

Email agent@connectorbay.com. We answer within two business days.

• MCP endpoint: https://byok-statuspage.connectorbay.com/mcp
• REST API: https://byok-statuspage.connectorbay.com/openapi.json
• Live status: https://byok-statuspage.connectorbay.com/health

When you report a problem, include the question you asked your agent, roughly when, and which agent you used (for example Claude, ChatGPT or Gemini). Never send us passwords, account numbers or ID numbers. Atlassian Statuspage (BYOK) never asks for them.