Hosted MCP

Hosted MCP is the supported MCP connector for the StatiBeat application. Remote MCP clients such as Claude, Cursor, and other OAuth-capable clients connect directly to StatiBeat without a local binary or a page API token.

Hosted MCP provides operational resources, prompts, and tools with explicit page selection, OAuth scopes, existing page permissions, write auditing, and connector revoke controls.

Use MCP Reference for the complete resource, prompt, and tool inventory.

What Hosted MCP is for

Hosted MCP is designed for:

• remote MCP clients that support hosted HTTP transport and OAuth
• real-user consent and attribution
• multi-page discovery with explicit page selection
• incident, maintenance, and Beat operational workflows
• auditable writes and product-managed revoke controls

Hosted MCP complements the other StatiBeat integration surfaces:

• use Slack for chat-native approvals and coordination
• use Terraform for durable configuration and governance
• use the REST API for custom automation outside MCP

Setup flow

1. Open the page admin UI and go to Hosted MCP.
2. Copy the Resource URL shown there.
3. Add that URL in your MCP client.
4. Sign in with your StatiBeat account when the client redirects you to OAuth consent.
5. Approve the requested scopes.
6. Return to Hosted MCP to confirm the client appears under connected clients.

You do not need to install a StatiBeat MCP executable or create an API token for this connection.

Hosted MCP routes are enabled per environment. When the hosted connector is not enabled, the admin page shows an unavailable state instead of endpoint, consent, and connection controls.

The OAuth flow uses authorization code with PKCE S256, no client secret, 10-minute authorization codes, 1-hour access tokens, and 30-day refresh tokens. Redirect URIs must be https except for http loopback redirects such as localhost or another loopback address. Non-loopback redirect URIs are fail-closed and must be registered with HOSTED_MCP_ALLOWED_CLIENT_REDIRECTS as exact client_id=redirect_uri entries separated by commas, whitespace, or new lines.

OAuth scopes

Hosted MCP supports:

• mcp.pages.read
• mcp.beats.read
• mcp.beats.write
• mcp.incidents.read
• mcp.incidents.write
• mcp.maintenances.read
• mcp.maintenances.write
• mcp.analytics.read
• mcp.subscribers.read

Effective access is always the approved OAuth scopes intersected with the signed-in user's existing page permissions. OAuth approval never grants more page access than the user already has.

OAuth scope	Page permission requirement
mcp.pages.read	Page read plus the relevant read permission for status definitions, lifecycle stages, maintenance lifecycle stages, hierarchy, settings, or embeds
mcp.beats.read	Synthetic monitor read; pending Beat actions additionally require synthetic monitor manage
mcp.beats.write	Synthetic monitor manage
mcp.incidents.read	Incident read
mcp.incidents.write	Incident manage
mcp.maintenances.read	Maintenance read
mcp.maintenances.write	Maintenance manage
mcp.analytics.read	Analytics read
mcp.subscribers.read	Subscriber read

Page scoping

Hosted MCP is multi-page aware:

• statibeat://pages lists pages available to the signed-in user
• page-bound resources use statibeat://pages/{page_id}/...
• prompts require a page_id
• mutating tools require an explicit page_id
• the backend checks both OAuth scope and page permission for every page-bound operation

Clients should discover pages first and reuse the selected page_id for subsequent reads, prompts, and writes.

Operational surface

Hosted MCP includes:

• page summary, catalogs, hierarchy, embed information, and subscriber summary reads
• active and historical incident reads with detail and timelines
• active, upcoming, past, and scheduled maintenance reads with detail and timelines
• bounded analytics summaries
• Beats, Beat Groups, pending actions, recent failures, and per-Beat evidence
• drafting and review prompts for incident, maintenance, and Beat workflows
• full incident lifecycle tools, including historical backfill, update, acknowledge, resolve, reopen, and delete
• full maintenance lifecycle tools, including update, complete, cancel, and delete
• manual Beat runs and pending Beat action approval or rejection

Hosted MCP remains intentionally page-operational. It does not expose broad settings changes, subscriber bulk mutations, branding changes, secret-bearing admin routes, or Terraform governance changes.

Audit, rate limits, and revoke behavior

Hosted MCP is designed to be attributable:

• each connector approval is tied to a real StatiBeat user and client identity
• the admin UI shows approved clients and granted scopes
• revoking a connection invalidates its active connector tokens
• writes and revokes carry Hosted MCP audit context
• write tools use Hosted MCP-specific rate limits
• effective page permissions are checked again when each operation runs

Read, list, and prompt calls record operational metrics, but they are not presented as a full audit-feed history.

Rollout guidance

For a production rollout:

1. start with read-focused workflows and prompt-assisted drafting
2. connect one or two trusted clients first
3. review granted scopes and recent activity in the Hosted MCP page
4. grant write scopes only for workflows the user is already authorized to perform
5. use draft_change, validate_change, and confirmed apply_change when the client does not already provide a trusted confirmation interface
6. keep broad configuration automation in Terraform or the REST API

Hosted MCP is the single supported MCP product path.