MCP server

Canary9 exposes an MCP (Model Context Protocol) server so you can manage monitoring straight from Claude, Cursor, or any other MCP-compatible client. No dashboard required.

What you can do

Endpoints

List, create, update, delete, pause, and resume monitored endpoints; check uptime % and recent results.

Alerts

Manage alert policies and review the alert event history.

Integrations

Create and manage Slack, Microsoft Teams, Discord, PagerDuty, Jira, email, and webhook integrations.

Connect

The MCP server speaks the streamable-http transport at:

https://mcp.canary9.com

Pick your tool below. In every case, connecting opens your browser: sign in to Canary9, approve the access request, and you're done. No tokens to copy.

One command:

claude mcp add --transport http canary9 https://mcp.canary9.com

Run /mcp inside Claude Code to authenticate (your browser opens to approve the connection) and to browse the tools.

Add to .cursor/mcp.json in your project (or ~/.cursor/mcp.json for all projects), then approve the sign-in prompt Cursor shows:

{
  "mcpServers": {
    "canary9": {
      "url": "https://mcp.canary9.com"
    }
  }
}

Add to ~/.codex/config.toml (or run codex mcp add); Codex runs the browser sign-in on first use:

[mcp_servers.canary9]
url = "https://mcp.canary9.com"

Add to .vscode/mcp.json:

{
  "servers": {
    "canary9": {
      "type": "http",
      "url": "https://mcp.canary9.com"
    }
  }
}

Enable the server from Copilot Chat's tools menu (agent mode); VS Code walks you through the browser sign-in the first time.

Add to ~/.codeium/windsurf/mcp_config.json (note Windsurf's field is serverUrl):

{
  "mcpServers": {
    "canary9": {
      "serverUrl": "https://mcp.canary9.com"
    }
  }
}

Any client that supports remote streamable-http servers works. Point it at the URL and it discovers the sign-in flow on its own (OAuth 2.1 with dynamic client registration):

{
  "canary9": {
    "url": "https://mcp.canary9.com"
  }
}

Clients without OAuth support can send a Canary9 bearer token in an Authorization header instead; see Authentication.

Claude.ai and ChatGPT connectors: add https://mcp.canary9.com as a custom connector and complete the browser sign-in, the same OAuth flow the IDE clients use.

Authentication

Connecting uses OAuth 2.1: your client registers itself, your browser opens to the Canary9 sign-in, and a consent screen shows exactly which client is asking before any access is granted. Approved clients get short-lived access tokens that refresh automatically and can be revoked at any time, and the MCP server never trusts a token on its own: every call is re-validated against the same backend services the Canary9 web app uses.

For headless or scripted use (CI jobs, cron), the server also accepts a Canary9 bearer token sent directly in an Authorization header. Treat any such token like a password.

Scoped to your organization: tool calls only ever see and change the endpoints, alerts, and integrations your account already has access to, with exactly the same scoping the web app enforces.

Available tools

Your MCP client discovers the tool catalogue automatically when it connects: every tool is published with its name, description, and input/output schema, so whatever your client shows you is always current. Broadly, tools cover monitored endpoints (create, update, pause/resume, uptime, recent results), alert policies and event history, notification integrations, and a whoami identity check. List tools accept page and page_size for organizations with a lot of data.

← Integrations Next: Account & team →