Connect an MCP Client

Probed exposes an MCP server at https://api.probed.dev/mcp using Streamable HTTP. Configure a remote HTTP server in your MCP client; this endpoint is not a local executable or a legacy SSE URL.

Open Agents → MCP in the dashboard for the Probed setup snippets for your client, including its OAuth or API-key options. The snippets are specific to the remote Probed endpoint.

Connect with an API key

1. Create an API key in the workspace you want the assistant to access. Start with read-only scope for inspection.
2. Add a remote MCP server with URL https://api.probed.dev/mcp and Streamable HTTP transport.
3. Configure the client's secret/header mechanism to send x-openstatus-key with your key. Authorization: Bearer with the API key is also accepted; use one credential mechanism.
4. Connect and let the client initialize the server and discover its tools.
5. Ask it to list your monitors or status pages, and verify that the results belong to the intended workspace.

Client configuration formats differ. Put the actual key in the client's secret store or supported environment mechanism, rather than a committed JSON configuration or a chat message. The issuing workspace determines access; tool calls do not select an arbitrary workspace.

Clients that support OAuth discovery can also follow the server's authentication challenge and complete Probed's consent flow. An initial HTTP 401 without a credential starts that discovery flow. Review the workspace and scopes on the consent screen; do not substitute an API key into OAuth client-ID or client-secret fields.

Inspect before changing anything

Start with a request such as:

List my status pages and monitors. Do not change anything. Identify the page and component IDs needed to investigate the affected service.

The server provides read tools for monitors, current status, summaries, response logs, status pages, page configuration, page components, status reports, maintenance, notification channels, and private locations. Audit tools are available only when the workspace has the audit-log entitlement.

For example, the client's tools/call arguments for a bounded monitor listing are:

{
  "name": "list_monitors",
  "arguments": { "page": 1, "perPage": 10 }
}

Use list_status_pages to discover page IDs and list_page_components to discover the components on the chosen page. Use discovered IDs rather than guessing them.

Update a status page or incident

Write scope exposes the supported mutation tools as well as reads. A read-only connection omits write tools from discovery. Supported writes include status-page rendering configuration, creating and updating status reports, adding report updates, resolving reports, and creating maintenance windows. MCP does not expose every dashboard or API mutation: monitor and private-location management tools on this server are read-only.

For the status-page builder, ask the assistant to call get_status_page_configuration before proposing a change. Review the exact change and affected page before allowing update_status_page_configuration. These changes affect the saved page rendering; they are not isolated preview drafts.

Configuration updates preserve omitted fields. An empty links or relatedPageIds array clears that list, and null clears latencyMonitorId. Custom CSS is separately validated and plan-gated; writing new CSS requires custom-theme and white-label entitlements. Arbitrary HTML and unrestricted JSON are not accepted.

For customer communication, a useful workflow is:

Inspect this monitor's recent status and the page's components. Draft a status report with the affected components and customer impact. Show me the message and notification choice before publishing it.

Use the report workflow and maintenance workflow to understand the public result. The MCP tools apply the same workspace boundaries and service validation as other Probed entry points. Your MCP client's confirmation behavior remains a client setting; connecting with write scope permits public changes.

Troubleshoot a connection

When reporting a failure, include the tool name, time, and safe error details. Remove API keys, OAuth tokens, private target details, and customer payloads.

The server also exposes the Probed OpenAPI specification as an MCP resource. For direct scripting rather than assistant tool calls, use the API reference.