Skip to main content
Activation required. AI access management must be enabled for your tenant before you can use it. To get started, contact the C1 support team for a walkthrough.
The Statuspage MCP server lets you govern access to Statuspage — pages, components, incidents, maintenances, metrics, and subscribers — as tools your AI clients can call through C1. Statuspage authenticates with an API key. A single key authenticates everyone, so all tool calls reach Statuspage as one shared identity.

​
How C1 connects to Statuspage

C1 hosts the Statuspage MCP server, so your users’ AI clients only ever see MCP tools — they never call Statuspage directly. When an AI client calls one of these tools, C1 makes the matching request to the Statuspage API using the credentials you configure here, then returns the result to the AI client. The credentials you set up below are what C1 uses to call Statuspage on your users’ behalf.

​
Before you begin

  • AI access management must be enabled for your tenant. See Enable AI access management.
  • A Statuspage account with access to the pages you want to govern and permission to create an API key.
If you don’t see Statuspage in your MCP server catalog, contact the C1 support team to enable it for your tenant.

​
Create a Statuspage API key

Create an API key in your Statuspage account to authenticate C1’s requests.
1
Sign in to the Statuspage management dashboard and open your account’s API settings. For details, see Statuspage’s Create and manage API keys documentation.
2
Generate a new API key.
3
Copy the generated key. Treat it as a high-value credential.
For a shared production setup, create the API key from a dedicated service account so activity is attributable to C1 rather than a person.

​
How Statuspage credentials are shared

Every user’s tool calls use the one API key you provided, so Statuspage sees a single shared identity. C1 still attributes each call to the individual user in the AI tool usage audit log. For a shared setup, use a dedicated service account so activity is attributable to C1 rather than a person. For how shared and per-user credentials work across MCP servers, see Configure authentication.

​
Register the Statuspage MCP server in C1

With your API key ready, register the server and provide your credentials.
1
Follow Register an MCP server and select Statuspage from the catalog.
2
When you configure authentication, choose Custom header. Set the header name to Authorization and the value to OAuth followed by your API key (for example, OAuth abc123).
3
Save your changes. C1 starts a sync that discovers the tools the Statuspage server exposes.

​
Discover and govern tools

After you register the server, C1 runs tool discovery against Statuspage. Discovered tools appear on the server’s Tools tab. Each tool starts as either Pending review or automatically Approved, depending on the option chosen when the server was set up or your tenant’s default tool settings in Settings > AI Connections. See Require tool approval and Default tool classification. Before anyone can call a Statuspage tool, it must be approved, added to a toolset, and bound to an access profile. Continue to Govern tools and toolsets to set this up.
Tool discovery runs even if your credentials are incorrect, so seeing discovered tools doesn’t confirm that authentication is working. You confirm your Statuspage credentials when an approved user successfully calls a Statuspage tool from their AI client.

​
Manage your Statuspage credentials

  • Rotate the API key by generating a new key in your Statuspage account settings and updating it in C1, then removing the old one.
  • Adjust access by managing the account the key belongs to in Statuspage.