Setup - Alertee

There are two ways to connect, depending on whether you use the CLI. Both expose the same tools.

Remote server (recommended)

Nothing to install — point your client at the hosted URL and sign in through the browser. The first time you connect, a browser window opens to sign in to Alertee and approve access. After that the client stays connected, and tool calls run against your default organization. URL

https://app.alertee.app/mcp

Pick your client:

claude mcp add --transport http alertee https://app.alertee.app/mcp

Add --scope user to make it available in every project instead of just the current one. Then run /mcp inside Claude Code to trigger the browser sign-in.

codex mcp add alertee --url https://app.alertee.app/mcp

Then authenticate:

codex mcp login alertee

Add to ~/.cursor/mcp.json (global) or .cursor/mcp.json in your project:

{
  "mcpServers": {
    "alertee": {
      "url": "https://app.alertee.app/mcp"
    }
  }
}

Settings → Connectors → Add custom connector, give it the name Alertee, paste the URL, and follow the browser sign-in.

https://app.alertee.app/mcp

code --add-mcp '{"name":"alertee","type":"http","url":"https://app.alertee.app/mcp"}'

Prefer a file you can commit? Add to .vscode/mcp.json in your project:

{
  "servers": {
    "alertee": {
      "type": "http",
      "url": "https://app.alertee.app/mcp"
    }
  }
}

Add to ~/.codeium/windsurf/mcp_config.json:

{
  "mcpServers": {
    "alertee": {
      "serverUrl": "https://app.alertee.app/mcp"
    }
  }
}

Local server (CLI users)

If you already use the Alertee CLI, run the MCP server locally — it reuses your existing login, so there’s no separate browser sign-in. Prerequisites

Claude Code
Codex
JSON config

claude mcp add alertee -- npx @alertee/cli mcp

If you installed the CLI globally, use claude mcp add alertee -- alertee mcp.

codex mcp add alertee -- npx @alertee/cli mcp

If you installed the CLI globally, use codex mcp add alertee -- alertee mcp.

Add to .mcp.json in your project root (or globally at ~/.claude/mcp.json, ~/.cursor/mcp.json, etc.):

{
  "mcpServers": {
    "alertee": {
      "command": "npx",
      "args": ["@alertee/cli", "mcp"]
    }
  }
}

If you’ve installed the CLI globally, use "command": "alertee" with "args": ["mcp"].

The local server uses the same credentials as the CLI, stored at ~/.config/alertee/config.json. To switch organizations, run alertee link; to switch between multiple Alertee accounts, run alertee auth switch — the server picks up the active account on the next tool call, no restart needed. To pin a server to one account, add "env": {"ALERTEE_ACCOUNT": "[email protected]"} to its config block.

Verify

Start a new session in your client. You should see Alertee listed as an available MCP server. Ask it:

“List my Alertee checks.”

It will call list_checks and return your current checks.

​Remote server (recommended)

​Local server (CLI users)

​Verify

Remote server (recommended)

Local server (CLI users)

Verify