An HTML page
An agent can read it, expensively and unreliably: a design is not data.
AI agents
Agents read your status page and can run it: an MCP server, a Markdown version, and a log that shows what the assistant did.
More and more incident work does not happen in a browser:
An agent can read it, expensively and unreliably: a design is not data.
Either the agent gets full access or none. Neither is the right answer.
When an assistant publishes something, there has to be a record of who did it and when.
api.statusas.lt/mcp connects Claude, ChatGPT, Cursor and any Model Context Protocol client to your workspace.
Every publishing tool requires an explicit decision about notifying subscribers. A model cannot quietly mail a thousand people.
Append .md, or send Accept: text/markdown, and the page comes back as text an agent can read cheaply.
Every action lands in the audit log, marked as coming from an MCP client.
Create an API key with the access level you want
Connect the MCP server to your client — OAuth or a key in a header
Pick the workspace and approve the access
Let the agent read monitors and write status reports
Review the audit log — everything it did is there
The dashboard also shows which apps have access, and you can revoke it at any time.
No. Publishing tools require an explicit decision about notifying subscribers, and every action stays in the log.
Any Model Context Protocol client: Claude Desktop and Claude Code, ChatGPT, Cursor, opencode and others.
Yes. An API key carries a scope, and the scope decides which tools the server exposes at all.
One URL, one email address — and you will hear about the next outage from us, not from a customer.