MCP server

Tallwatch hosts the MCP server. There is no npm package, no npx, and no local process (Claude Desktop is the exception below). Point the client at https://api.tallwatch.com/mcp with a Bearer . The agent can check org status, list monitors, triage incidents, and (with a write key) pause or ack. Same surface as the for ops work. The app UI still uses your session cookie.

Setup

Create a key in . The tw_live_… secret is shown once.
Copy prompt on that page pastes setup into the agent, or pick your client below.
Keep the key in user-level config, not a committed project file.

Each client has its own config shape. The wrong URL field or transport type is ignored, or it falls back to SSE and never reaches /mcp.

User: ~/.cursor/mcp.json. Project: .cursor/mcp.json. Remote entries use url and headers. Do not set type.

{
  "mcpServers": {
    "tallwatch": {
      "url": "https://api.tallwatch.com/mcp",
      "headers": {
        "Authorization": "Bearer tw_live_your_key_here"
      }
    }
  }
}

You can put the secret in the environment instead: "Authorization": "Bearer ${env:TALLWATCH_API_KEY}". Reload MCP in Cursor Settings.

User: Command Palette → MCP: Open User Configuration. Project: .vscode/mcp.json. MCP: Add Server also works.VS Code uses servers, not mcpServers. "type": "http" is required.

{
  "servers": {
    "tallwatch": {
      "type": "http",
      "url": "https://api.tallwatch.com/mcp",
      "headers": {
        "Authorization": "Bearer tw_live_your_key_here"
      }
    }
  }
}

For a committed workspace file, prompt for the key instead of pasting it:

{
  "inputs": [
    {
      "type": "promptString",
      "id": "tallwatch-key",
      "description": "Tallwatch API key",
      "password": true
    }
  ],
  "servers": {
    "tallwatch": {
      "type": "http",
      "url": "https://api.tallwatch.com/mcp",
      "headers": {
        "Authorization": "Bearer ${input:tallwatch-key}"
      }
    }
  }
}

--scope user writes to ~/.claude.json for every project. Without it, the default is this project only. A JSON entry with url and no type is skipped.

claude mcp add --scope user --transport http \
  --header "Authorization: Bearer tw_live_your_key_here" \
  tallwatch https://api.tallwatch.com/mcp

Or merge this into ~/.claude.json (user) or .mcp.json (project):

{
  "mcpServers": {
    "tallwatch": {
      "type": "http",
      "url": "https://api.tallwatch.com/mcp",
      "headers": {
        "Authorization": "Bearer tw_live_your_key_here"
      }
    }
  }
}

Settings → Connectors is OAuth-only and will not send a Bearer key. claude_desktop_config.json only runs local stdio servers. A url / headers block is ignored. Bridge with mcp-remote:macOS ~/Library/Application Support/Claude/claude_desktop_config.json; Windows %APPDATA%\Claude\claude_desktop_config.json; Linux ~/.config/Claude/claude_desktop_config.json.

{
  "mcpServers": {
    "tallwatch": {
      "command": "npx",
      "args": [
        "-y",
        "mcp-remote",
        "https://api.tallwatch.com/mcp",
        "--header",
        "Authorization:${AUTH_HEADER}"
      ],
      "env": {
        "AUTH_HEADER": "Bearer tw_live_your_key_here"
      }
    }
  }
}

Restart the app.

Prefer an env var. bearer_token_env_var is the name of the variable, not the token.

export TALLWATCH_API_KEY=tw_live_your_key_here
codex mcp add tallwatch \
  --url https://api.tallwatch.com/mcp \
  --bearer-token-env-var TALLWATCH_API_KEY

Or ~/.codex/config.toml (ChatGPT desktop, Codex CLI, and the IDE extension share this file):

[mcp_servers.tallwatch]
url = "https://api.tallwatch.com/mcp"
bearer_token_env_var = "TALLWATCH_API_KEY"

http_headers is for extra static headers, not the secret. Do not put the token in bearer_token_env_var.

Devin Desktop (Cascade, formerly Windsurf): ~/.codeium/windsurf/mcp_config.json. The URL field is serverUrl. url is ignored.

{
  "mcpServers": {
    "tallwatch": {
      "serverUrl": "https://api.tallwatch.com/mcp",
      "headers": {
        "Authorization": "Bearer tw_live_your_key_here"
      }
    }
  }
}

Devin CLI / Devin Local: user ~/.config/devin/mcp_config.json (Windows %APPDATA%\devin\mcp_config.json). Project key: .devin/mcp_config.local.json (gitignored). This client uses url, not serverUrl.

{
  "mcpServers": {
    "tallwatch": {
      "url": "https://api.tallwatch.com/mcp",
      "headers": {
        "Authorization": "Bearer tw_live_your_key_here"
      }
    }
  }
}

Gemini CLI: url is SSE. Streamable HTTP is httpUrl. Default scope is this project; -s user writes ~/.gemini/settings.json.

gemini mcp add --scope user --transport http \
  --header "Authorization: Bearer tw_live_your_key_here" \
  tallwatch https://api.tallwatch.com/mcp

{
  "mcpServers": {
    "tallwatch": {
      "httpUrl": "https://api.tallwatch.com/mcp",
      "headers": {
        "Authorization": "Bearer tw_live_your_key_here"
      }
    }
  }
}

Antigravity uses serverUrl (same as Devin Desktop) in ~/.gemini/config/mcp_config.json or .agents/mcp_config.json.

CLI: ~/.cline/mcp.json. IDE: MCP Servers → Configure. "type": "streamableHttp" is required. Omit it and Cline uses SSE.

{
  "mcpServers": {
    "tallwatch": {
      "type": "streamableHttp",
      "url": "https://api.tallwatch.com/mcp",
      "headers": {
        "Authorization": "Bearer tw_live_your_key_here"
      }
    }
  }
}

config.yaml, or a file under .continue/mcpServers/. Transport is streamable-http. Headers go under requestOptions, not a top-level headers key.

mcpServers:
  - name: tallwatch
    type: streamable-http
    url: https://api.tallwatch.com/mcp
    requestOptions:
      headers:
        Authorization: Bearer tw_live_your_key_here

Continue also loads a Cursor-style JSON file dropped into .continue/mcpServers/.

Settings → MCP → add a remote server. URL https://api.tallwatch.com/mcp. If the UI asks for headers, set Authorization to Bearer tw_live_your_key_here. T3 Chat does not publish a config-file schema.

Tools

Same ops surface as the (minus browser login / browse). Prefer get_status when the user asks what is broken. UptimeRobot import is in the app (Monitors → Import) and CLI — not an MCP tool.

Tools	Scope
`get_status`, `whoami`, `list_monitors`, `get_monitor`, `list_incidents`, `get_incident`, `get_incident_evidence`, `list_oncall_now`, `list_status_pages`, `get_status_page`	`read`
`create_monitor`, `update_monitor`, `pause_monitor`, `resume_monitor`, `trigger_test_check`, `acknowledge_incident`, `resolve_incident`, `reopen_incident`, `add_postmortem`	`write`

Create / update monitors

create_monitor and update_monitor use the shared CreateMonitor contract:

Non-heartbeat: at least three regions.
Fields: name, type, config, regions, interval_sec (optional notify_after_sec, escalation_policy_id, project_id).
Consensus is fixed (m=1 / k=2). Do not send consensus.
Removed fields (depends_on_monitor_ids, tags) are rejected / ignored — do not send them.

MCP uses the same key as the REST API, so apply. Prefer one list_monitors over many get_monitor calls. . . .

Monitors

Alerts

Status pages

Developers

Setup

Tools

Create / update monitors

​Setup

​Tools

​Create / update monitors

​Related

Setup

Tools

Create / update monitors

Related