The API and the MCP server

Everything the dashboard does, over HTTPS with a key, or through an MCP server an agent can use. JSON in, JSON out, stable ids, ISO times. On every plan.

api/v1

# REST: list the pages the key reaches
curl https://statoss.com/api/v1/pages \
  -H "Authorization: Bearer sk_..."

# MCP: the same key, as a bearer token
https://statoss.com/api/v1/mcp

The first call with a key, and the MCP address that takes the same key. The key is a placeholder.

Keys and scopes

A key reads, or reads and writes, and reaches every page on the account or one page. Made under Settings, API keys, shown once, stored as a hash.

Setting up a whole account

Create pages, add monitors of every type, set alert destinations, invite the team, add a domain and post deploy markers with calls to /api/v1. The OpenAPI 3.1 document is at /api/v1/openapi.json.

The MCP server

https://statoss.com/api/v1/mcp with the same key does the same as tools: list_pages, get_status, create_monitor, open_incident and the rest. A read-only MCP endpoint with no key sits at /mcp next to every status page.

From CI

One POST after a release draws a dashed line on the response-time chart with the version. GitHub Actions needs the key in a repository secret.

Reference

The API reference lists every field and a working example per call; MCP and agents lists every tool.