Connect an MCP client
Team, Business, and Enterprise accounts can point Cursor, Claude, or another MCP client at allthestatus.com/mcp and read their status pages.
Create a token
Sign in, open MCP in Settings, name the token, and create it. The secret is shown once. We store only a hash, so a leak is fixed by revoking that token. A browser sign-in is the wrong credential: it expires, and it can change dashboards.
Add the server
In Cursor, add a remote MCP server. The URL is https://allthestatus.com/mcp. Put the token in an Authorization header as Bearer. A client config looks like this:
{
"mcpServers": {
"allthestatus": {
"url": "https://allthestatus.com/mcp",
"headers": {
"Authorization": "Bearer ats_…"
}
}
}
}Claude Code uses the same URL. Some clients want a type of http next to the URL. The token still goes in that Authorization header.
What it can read
The server lists this account's status pages, returns the current status of a page (components, open incidents, monitors), and returns the board of public services that page watches. It does not create incidents or change a page. Anyone with the token can read private pages the account can see, so treat it like a password.
Why a token, not a login popup
MCP's hosted-connector spec uses OAuth 2.1 with PKCE when a chat product opens a browser. Cursor and Claude Code keep a config file and send a header. A hashed, revocable token matches that, stays read-only, and stops working if the account leaves Team. OAuth for ChatGPT or Claude.ai can sit on top of the same /mcp URL later without changing how tokens work.