> For the complete documentation index, see [llms.txt](https://docs.statuspal.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.statuspal.io/next/platform/mcp.md). # MCP ## Connecting AI Assistants to StatusPal Next (MCP) StatusPal Next provides a hosted **MCP server** that lets AI assistants — Claude, ChatGPT, Cursor, and any other [MCP](https://modelcontextprotocol.io)-compatible client — work with your status pages on your behalf. Once connected, you can ask your assistant to read and manage your status pages, services, incidents, maintenance notices, and webhooks using plain language. This guide covers everything you need to connect and start using it. *** ### What you can do After connecting, your assistant can: * **Status pages** — list, view, create, update, and delete status pages. * **Services & containers** — manage the services shown on a page and the groups they belong to. * **Notices (incidents & maintenance)** — open an incident or schedule maintenance, post timeline updates, edit details, and resolve or close them. * **Outgoing webhooks** — list, create, update, rotate secrets for, and delete webhooks. * **Search the API docs** — answer questions about the StatusPal Next API without making any changes. The server makes authenticated calls to the StatusPal Next API for you — it does **not** add any AI of its own. All the reasoning happens inside the assistant you already use. *** ### Before you start You need a **StatusPal Next API key**. 1. Sign in to your StatusPal Next account. 2. Go to your account/organization settings and open the **API keys** section. 3. Create a key and copy it somewhere safe — you will paste it once during setup. That key is the only credential required. The MCP server acts only on the status pages that key has access to. *** ### The connection URL There is a single endpoint for every client: ``` https://mcp.next.statuspal.io/mcp ``` How you provide your API key depends on the client: * **Web assistants** (Claude.ai, ChatGPT) — you paste your key once on a secure login page that appears automatically. There is nothing to configure by hand. * **Developer/desktop tools** (Claude Code, Cursor, custom clients) — you send the key in an `Authorization` header. Pick your client below. *** ### Claude (web or Desktop) 1. Open Claude. 2. In the sidebar, click **Customize**. 3. Click **Connectors**. 4. Click the **+** button at the top. 5. Select **Add custom connector**. 6. Fill the form: * **Name:** `StatusPal Next` * **URL:** `https://mcp.next.statuspal.io/mcp` * Leave the optional OAuth fields empty. * Keep **Individual sign-in** enabled. 7. Click **Add**. 8. Open the new **StatusPal Next** connector and click **Connect**. 9. A browser window opens. Paste your StatusPal Next API key and finish the sign-in flow by clicking **Authorize**. 10. Click **Open Claude** or **Open desktop app**, depending on where you're using Claude. After that, make sure the connector is enabled: 1. Open a chat. 2. Click the **+** button below the chat input. 3. Hover **Connectors**. 4. Make sure **StatusPal Next** is enabled. The StatusPal tools now appear in the tools menu. *** ### ChatGPT > Requires a plan that supports apps and developer mode (Plus, Pro, Business, or Enterprise). 1. Open **Settings → Apps**. 2. Click **Advanced settings** and enable **Developer mode**. 3. Click **Create app**. 4. Fill the app form: * **Name:** `StatusPal Next` * **Connection:** **Server URL** * **Server URL:** `https://mcp.next.statuspal.io/mcp` * **Authentication:** **Access token / API key** * **Header scheme:** **Bearer** 5. Accept each warning and click **Create**. 6. Enter your StatusPal Next API key and click **Connect StatusPal Next**. 7. The app is now available inside chats. *** ### Grok 1. Open Grok. 2. In the sidebar, click **Skills and Connectors**. 3. Click **Connectors**. 4. Click **New Connector**. 5. In the modal, click **Custom**. 6. Fill the form: * **Name:** `StatusPal Next` * **Server URL:** `https://mcp.next.statuspal.io/mcp` 7. Click **Add Connector**. 8. A browser window opens. Paste your StatusPal Next API key and finish the sign-in flow by clicking **Authorize**. The connector is now installed. Make sure it is enabled: 1. Open a chat. 2. Click the **+** button next to the chat input. 3. Hover **Connectors**. 4. Make sure **StatusPal Next** is enabled. *** ### Claude Code Claude Code can send the key directly in a header — no login page needed. Run: ```bash claude mcp add --transport http "StatusPal Next" \ https://mcp.next.statuspal.io/mcp \ --header "Authorization: Bearer YOUR_STATUSPAL_API_KEY" ``` Replace `YOUR_STATUSPAL_API_KEY` with your key. After adding it, enable it in the chat: click the **+** button below the input → **Connectors** → toggle **StatusPal Next** on. *** ### Codex for VS Code 1. Open Codex in VS Code. 2. Open **Codex Settings**. 3. Click **MCP servers**. 4. Click **Add server**. 5. Fill the form: * **Name:** `StatusPal Next` * **Transport:** **Streamable HTTP** * **URL:** `https://mcp.next.statuspal.io/mcp` * Leave the bearer token field empty. * Leave headers empty. 6. Click **Save**. 7. In the server list, click **Authenticate**. 8. A browser window opens. Paste your StatusPal Next API key and click **Authorize**. 9. Make sure the server is enabled. 10. Click **Restart extension**. Codex is now ready to use with StatusPal Next. *** ### Cursor and other developer clients Any MCP client that supports **Streamable HTTP** with a custom header works the same way. Point it at: ``` https://mcp.next.statuspal.io/mcp ``` and add the header: ``` Authorization: Bearer YOUR_STATUSPAL_API_KEY ``` Browser-based custom clients additionally need their origin allow-listed for CORS — contact StatusPal support if you're building one. *** ### Example prompts Once connected, just ask in natural language: * "Configure a new status page with services: API, Web Console, Support Portal and regions: EU, US, Asia." * "List my StatusPal status pages." * "What services are on the *Production* page, and what's their current status?" * "Open an incident on the *API* page: we're investigating elevated error rates." * "Post an update: the issue is identified, a fix is rolling out now." * "Mark the incident as resolved." * "Schedule maintenance on the *Database* service for this Sunday 02:00–04:00 UTC." * "Create an outgoing webhook pointing at ." The assistant will ask for confirmation before anything that changes or deletes data. *** ### Privacy & security * Your API key is **never stored on our servers**. For web assistants it's sealed (encrypted) inside the connection token your client holds; for header-based clients it's only ever sent on the request. It is used solely to call the StatusPal Next API on your behalf. * The server never logs your key or authorization headers. * The assistant only has access to what your API key can access. Revoke the key in your StatusPal Next settings at any time to immediately cut off access. *** ### Troubleshooting | Problem | Fix | | ------------------------------------------ | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | Connector won't authorize | Re-check the URL is exactly `https://mcp.next.statuspal.io/mcp`. For web clients, complete the login page; for header clients, confirm the `Authorization: Bearer ` header. | | "Tools not available" in chat | Enable the connector via the **+** button → **Connectors** toggle. | | Calls fail with an auth error | Your API key may be invalid or revoked — generate a fresh one in StatusPal Next settings and reconnect. | | Tools missing after a StatusPal API update | The tool list refreshes when you reconnect — remove and re-add the connector. | Need help? Contact StatusPal support.