> 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 **Settings → Connectors → Add custom connector**. 2. Give it a name, e.g. `StatusPal Next`. 3. Paste the URL: ``` https://mcp.next.statuspal.io/mcp ``` 4. Click **Add**. Claude opens a StatusPal login page — **paste your API key** there and confirm. 5. You're redirected back and the connector goes live. To use it in a conversation, click the **+** button below the chat input, open **Connectors**, and make sure **StatusPal Next** is enabled. The StatusPal tools then appear in the tools menu. *** ### ChatGPT > Requires a plan that supports connectors / developer mode (Plus, Pro, Business, or Enterprise). 1. Open **Settings → Connectors → Add**. 2. Paste the URL: ``` https://mcp.next.statuspal.io/mcp ``` 3. Complete the prompt — **paste your StatusPal API key** on the login page that appears. 4. The connector is now available to select inside a chat. *** ### 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. *** ### 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. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://docs.statuspal.io/next/platform/mcp.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.