Hosted MCP server for AlertsDown

Let your AI coding tool manage AlertsDown monitors.

AlertsDown exposes your monitoring workspace through a hosted MCP server, so Claude Code, Codex, Cursor, Windsurf, and compatible LLM clients can create checks, review status, and help investigate downtime without leaving your development workflow.

Create Your Account Need MCP Alerts?
Hosted endpoint Streamable HTTP
https://api.alertsdown.com/api/mcp
What connects
Your AI client connects to AlertsDown.
Authentication
Authorization: Bearer <api-key> or x-api-key
Key location
Account dashboard after upgrading to a supported paid plan

What it is

Monitoring as a tool your LLM can call

MCP, or Model Context Protocol, gives AI assistants a standard way to call external tools. Instead of copying URLs, screenshots, and incident details into a chat, you connect your LLM client to AlertsDown once. After that, the assistant can use live monitoring context while it helps you ship code or respond to outages.

The hosted AlertsDown MCP server removes the operational work. There is no local bridge to deploy, no custom script to keep alive, and no separate reliability layer to maintain. Your AI client connects to the AlertsDown endpoint, authenticates with your API key, and works with the same monitoring data you use in the dashboard.

What you can do

Give your assistant operational context

Create and manage monitors

Ask your AI tool to add monitors for a new API, update check intervals, review monitor configuration, or remove checks that no longer matter.

Investigate incidents faster

Let the assistant pull monitor status, recent failures, and response history while it reads logs, checks code changes, or prepares a recovery plan.

Keep releases honest

After a deploy, ask the LLM to verify the public website, API health check, checkout flow, or status page monitor before you move on.

Document reliability work

Use live monitor data to draft incident notes, maintenance summaries, follow-up tasks, or customer updates with less manual copying.

Setup

Connect AlertsDown to your LLM client

Hosted MCP is available on supported paid plans. Once your account has access, create an MCP API key from your account dashboard and use the configuration for your client.

1

Upgrade or choose a plan with MCP

Pick a supported paid plan so your account can create a per-user hosted MCP API key.

2

Create an MCP API key

Open your account dashboard, create the key, and store the secret in an environment variable such as ALERTSDOWN_MCP_API_KEY.

3

Add the MCP server to your client

Use the hosted endpoint and pass your key as a bearer token. Restart desktop clients after changing environment variables.

Claude Code

Use the HTTP transport and pass the AlertsDown key as a bearer token.

export ALERTSDOWN_MCP_API_KEY="admcp_your_secret_here"
claude mcp add --transport http alertsdown https://api.alertsdown.com/api/mcp \
  --header "Authorization: Bearer $ALERTSDOWN_MCP_API_KEY" \
  --scope user

Codex

Point Codex at the hosted endpoint and keep the secret in an environment variable.

export ALERTSDOWN_MCP_API_KEY="admcp_your_secret_here"
codex mcp add alertsdown \
  --url https://api.alertsdown.com/api/mcp \
  --bearer-token-env-var ALERTSDOWN_MCP_API_KEY

Cursor

Add this to .cursor/mcp.json or ~/.cursor/mcp.json after setting ALERTSDOWN_MCP_API_KEY.

{
  "mcpServers": {
    "alertsdown": {
      "url": "https://api.alertsdown.com/api/mcp",
      "headers": {
        "Authorization": "Bearer ${env:ALERTSDOWN_MCP_API_KEY}"
      }
    }
  }
}

Windsurf

Add this to ~/.codeium/windsurf/mcp_config.json and restart Windsurf.

{
  "mcpServers": {
    "alertsdown": {
      "serverUrl": "https://api.alertsdown.com/api/mcp",
      "headers": {
        "Authorization": "Bearer ${env:ALERTSDOWN_MCP_API_KEY}"
      }
    }
  }
}

Generic Streamable HTTP clients

Use endpoint https://api.alertsdown.com/api/mcp with Authorization: Bearer <api-key>. Clients that prefer headers can also send x-api-key: <api-key>.

How to use it

Prompts to try after connecting

"Add uptime monitoring for the production API and alert me if it stops returning 200."
"Show me which monitored endpoints failed after the last deployment."
"Review my monitors and suggest missing checks for this SaaS project."
"Check whether the checkout, webhook receiver, and status page are healthy before I announce this release."

Want alerts for your own MCP server?

Hosted MCP lets AI clients use AlertsDown. MCP Server Monitoring is the separate alerts feature for checking your own or vendor MCP endpoints, expected tools, resources, prompts, and safe probes.

View MCP Alerts Create Your Account

Hosted MCP FAQ

What is the AlertsDown hosted MCP server?

It is an AlertsDown-hosted Model Context Protocol endpoint that lets AI coding tools manage your AlertsDown monitoring workspace through authenticated tools.

How is hosted MCP different from MCP alerts?

Hosted MCP lets your AI client connect to AlertsDown. MCP alerts are a separate feature for monitoring your own or vendor MCP servers and receiving alerts when they break.

Which AI tools can use it?

AlertsDown supports clients that can connect to a Streamable HTTP MCP server, including Claude Code, Codex, Cursor, Windsurf, and other compatible MCP clients.

Do I need to run a local bridge?

No. AlertsDown hosts the MCP endpoint. Create an MCP API key in your account and configure your client to send it as a bearer token.

What can my AI assistant do after setup?

Your assistant can help create monitors, review status, inspect downtime history, and use live uptime context while you work on incidents or deployments.