Build and publish the page
Create the page, rename it, publish it, and read back the current status or a badge for your README.
create_status_pageget_status_pageupdate_status_pageget_current_statusget_badge_markdown
Connect UpPage to the AI agent you already code with. It sets up your page, monitors and heartbeats in one go, and when something breaks it posts the incident update from the same chat where you’re shipping the fix.
> Checkout is throwing 500s. Tell customers
we’re on it.
→ get_current_status Checkout: degraded
→ create_incident Checkout errors
> Fix is deployed, errors are back to zero.
→ resolve_incident Checkout errors
✓ Status page shows all systems operational24 tools covering the whole page, with the same permission checks and plan limits as the dashboard.
Create the page, rename it, publish it, and read back the current status or a badge for your README.
create_status_pageget_status_pageupdate_status_pageget_current_statusget_badge_markdown
Add the API, web app and background jobs, reorder them, and set a status when your agent knows something you verified.
list_componentsadd_componentupdate_componentset_component_status
Add website checks, MCP endpoint checks and heartbeats, then get a ready-made cron or CI snippet that pings UpPage.
create_monitorlist_monitorsupdate_monitorapply_fixcreate_heartbeatlist_heartbeatsupdate_heartbeatrotate_heartbeatget_heartbeat_snippet
Open an incident, post updates as the fix lands, resolve it, and run maintenance windows, all from the same chat as the fix.
create_incidentlist_incidentsupdate_incidentresolve_incidentstart_maintenanceend_maintenance
Pick your client and add UpPage. The first time your agent connects, UpPage opens in your browser so you can sign in and approve it. Clients without sign-in can use a scoped API token instead.
Opens Cursor to add UpPage, then you sign in.
Opens VS Code’s MCP install prompt, then you sign in.
Adds UpPage as a connector in Claude on web, desktop and mobile, then you sign in.
Paste one command, then sign in from /mcp.
Paste one command, then run codex mcp login uppage.
Any client with remote MCP and OAuth sign-in, or a custom header for an API token.
Remote MCP endpoint (Streamable HTTP): https://uppage.dev/mcp
Google, GitHub or an email link. No card, and the Free plan includes MCP.
Click your client in the dashboard’s AI agents tab, or just add the URL below. Your browser opens UpPage, you approve access, and the agent is connected.
“Set up a status page for this repo, check the homepage and add a heartbeat to the nightly job.” Your agent does the rest.
Before an app connects you see what it can and can’t do. Disconnect it any time in Settings → Connected apps.
Every tool call goes through the same authorization and plan limits as the dashboard and REST API.
A connected agent reaches one account, and a page-restricted token sees only its page.
Ship an MCP server yourself? Add an MCP check and UpPage connects like an agent, lists its tools, and shows the result on your page.
No. The MCP server is on every plan, including Free. Your agent works within the same plan limits as the dashboard.
An agent connected through the dashboard can manage pages, services, incidents and heartbeats. It can’t change billing, invite or remove members, create API tokens or delete the account.
Through OAuth. The first time it connects, UpPage opens in your browser; you sign in, see what the app is asking for and approve it. It then shows under Settings → Connected apps, where you can disconnect it. Clients without OAuth sign-in can use a scoped API token instead.
UpPage’s MCP server tells agents to read the current state before posting and never to invent causes, timelines or recoveries. Every update shows on your page and in the dashboard.
Token setup with Claude Code, end to end. Sign-in follows the MCP authorization spec, and we’re still testing it client by client; API tokens work in all of them in the meantime.
Start on Free with no card, then connect your agent from the dashboard.
Start free