Workspaces
Start in the right customer or operational context.
- List the active workspaces linked to the signed-in account.
Monitoring.app for MCP gives compatible AI clients scoped access to investigate monitors, manage safe settings, and prepare status communication—with explicit controls around writes and publishing.
https://api.monitoring.app/mcpThe first MCP release focuses on the work that benefits most from context: monitor operations and customer-facing status communication.
Start in the right customer or operational context.
Investigate health and manage safe monitor settings.
Prepare and maintain customer-facing service communication.
Draft, publish, and resolve updates without losing the audit trail.
MCP requests pass through the same workspace permissions and product rules as the portal, with extra safeguards for machine-driven operations.
Remote clients authenticate with linked accounts and request only the scopes their tools need.
Every operation names a workspace. Membership and role checks are enforced again server-side.
Mutations require idempotency keys, with operation receipts retained for 24 hours.
Drafting and publishing are separate actions for status pages, incident updates, and postmortems.
Destructive tools require an exact current name and are marked destructive in the MCP catalog.
Journey headers, bodies, URLs, definitions, and request secrets stay out of MCP responses.
Your AI client decides how to present and combine tools. Monitoring.app supplies the typed operations, permissions, and structured results underneath.
Use the Monitoring.app MCP URL in a compatible client that supports remote Streamable HTTP.
Sign in with your linked account and approve only the workspace, monitor, and status-page scopes you need.
Start with a read request, then allow deliberate writes or publication actions when the workflow calls for them.
Connect a compatible MCP client to investigate faster, prepare clearer updates, and keep every action inside your workspace boundaries.
Essential cookies keep login, CSRF protection, OAuth, and workspace security working. Firebase Analytics is off until you allow analytics cookies.
Cookie policy