MCP server overview

The Alertee MCP (Model Context Protocol) server lets AI assistants — like Claude, Codex, and Cursor — create and manage Alertee checks as part of their workflow.

The use case

You’re debugging a bug in another project’s session. You notice a pattern that could cause problems in production. Instead of switching context to open the Alertee dashboard, you just ask your assistant:

“Create an Alertee check that alerts if failed payments exceed 10 in the last hour.”

It calls the create_check tool, connects to your organization, and creates the check — all without you leaving your current session. It also works the other way: an alert can fire a webhook that hands an AI agent the check, and the agent uses MCP to pull the SQL, recent history, and failing data and investigate on its own. See Investigate alerts with an AI agent.

Two ways to connect

	Remote (hosted)	Local (CLI)
Best for	Anyone — no install	CLI / terminal users
Setup	Paste a URL, sign in via browser	`alertee login` + `alertee link`
Auth	Browser sign-in (OAuth), per-user	Reuses your CLI token
Transport	Hosted HTTP at `https://app.alertee.app/mcp`	stdio subprocess (`npx @alertee/cli mcp`)

Most people should use the remote server — there’s nothing to install. If you already live in the CLI, the local server reuses your existing login. Both expose the same tools. Connect a client →

How the remote server works

You add the URL to your AI client and it opens a browser window to sign in to Alertee and approve access — the same OAuth flow you’d expect from any “Connect your account” button. Once approved, the client connects and can call tools on your behalf, against your default organization. Nothing to install.

How the local server works

The local server runs alongside your client and reuses your Alertee CLI login — no extra setup once you’ve run alertee login and alertee link.

Available tools

Tool	Description
`list_checks`	List all checks in your organization
`get_check`	Get a single check’s full detail
`get_check_history`	Get a check’s recent run history
`run_check`	Run a check immediately and return the result
`create_check`	Create a new check (single-value or multi-dimensional grid)
`update_check`	Update a check — rename, retune, pause, mute alerts, or change its schedule
`delete_check`	Delete a check
`snooze_check`	Temporarily silence a check’s alerts (auto-expires)
`set_check_schedule`	Set/clear a check’s custom active schedule (e.g. only run during market hours)
`list_connections`	List available database connections
`create_connection`	Add a database connection (tested before saving)
`test_connection`	Test an existing database connection
`preview_api_metric`	Probe a JSON API and list its extractable gjson paths (for authoring an api_metric check)
`list_organizations`	List organizations you belong to
`create_organization`	Create a new organization
`list_alert_groups`	List alert groups
`create_alert_group`	Create an alert group
`delete_alert_group`	Delete an alert group
`send_test_alert`	Send a test alert through a group’s real channels to verify delivery
`list_alert_recipients`	List a group’s recipients (channels)
`add_alert_recipient`	Add a webhook or email-group recipient to a group
`remove_alert_recipient`	Remove a recipient from a group
`list_email_groups`	List email groups (recipient lists)
`create_email_group`	Create an email group
`delete_email_group`	Delete an email group
`add_email_group_members`	Add email addresses to an email group
`remove_email_group_member`	Remove an email address from an email group
`list_inbox`	List inbox items (incidents)
`get_inbox_item`	Get a single incident + timeline
`acknowledge_inbox_item`	Acknowledge an incident
`resolve_inbox_item`	Resolve an incident
`get_inbox_digest`	Get the inbox digest (briefing + counts)
`list_webhook_receivers`	List inbound webhook receivers
`create_webhook_receiver`	Create an inbound webhook receiver
`delete_webhook_receiver`	Delete an inbound webhook receiver

See the tools reference for full parameter details.

Next step

Connect a client →

​The use case

​Two ways to connect

​How the remote server works

​How the local server works

​Available tools

​Next step