Is this an official Pingdom MCP server?

No. It is Memtro's MCP server with Memtro's Pingdom connector behind it: the connector reads Pingdom through its API with the credentials you connect on Dashboard → Connections, and Pingdom publishes nothing here. The same endpoint carries every other system you connect and Memtro's memory tools.

Nothing on top of Memtro. One price per organisation by its number of users, from $50 a month for up to 10 users after a 7-day free trial, with every connector, the MCP server, jobs and memory included. You bring your own model keys.

Can it change anything in Pingdom?

Only when you ask, and only what it has been granted: create an uptime check; change a check's settings or who it alerts; pause or resume chosen checks; delete a check and its history (permanent); schedule a maintenance window that silences alerts; change a maintenance window; delete a future maintenance window. Every other tool reads, searches or lists. An administrator grants each acting tool by name per team, and a personal connection acts only after its owner allows it.

Any MCP client that speaks Streamable HTTP: Claude Code, Cursor, Claude Desktop, OpenCode, Codex, Zed, Windsurf, Cline and the Anthropic and OpenAI SDKs. There is no local process to run; the server is remote and authenticated with your key.

MCP server · Engineering and operations

Pingdom MCP server

Pingdom in any MCP client, through Memtro: Pingdom does not publish this server. Memtro's Pingdom connector reads Pingdom through its API with the credentials you connect, and one endpoint hands those tools, every other system you connect and Memtro's memory tools to Claude Code, Cursor, Claude Desktop or anything else that speaks Streamable HTTP, as you.

What the model can do

Pingdom uptime monitoring: checks and whether each is up or down, outage history for a check, uptime percentage and average response time over a period, and the alerts Pingdom sent. Can create, change, pause and delete checks and schedule maintenance windows.

Reads

pingdom_list_checksUptime checks in Pingdom: name, hostname, type, status (up, down, paused…), how often it runs, last test, last error, last response time…
pingdom_check_outagesThe up and down history of one check over a period (default the last 7 days)…
pingdom_check_uptimeUptime percentage and average response time of one check over a period (default the last 30 days), with seconds up, down and unknown.
pingdom_alertsAlerts Pingdom sent over a period (default the last 7 days), newest first: which check, when, how it was sent (email, sms, webhook…)…

Acts, when you ask

These change something in Pingdom. The model is told to use them only when you ask for exactly that, and each one is granted by name: per team on a shared connection, by the owner on a personal one.

pingdom_create_checkCreate a new Pingdom uptime check that starts testing the host straight away and alerts the users, teams or integrations named (none unless named).
pingdom_update_checkChange one Pingdom check's settings.
pingdom_pause_checksPause or resume the named Pingdom checks.
pingdom_delete_checkPermanently delete one Pingdom check and all the uptime and outage history it collected.
pingdom_create_maintenance_windowSchedule a Pingdom maintenance window in the future, during which the named checks raise no down alerts.
pingdom_update_maintenance_windowChange a future Pingdom maintenance window: its description, times, recurrence or the checks it silences (check_ids replaces the list).
pingdom_delete_maintenance_windowDelete a future Pingdom maintenance window, so its checks alert as normal in that period.

Connect it

First connect Pingdom on Dashboard → Connections, then add Memtro to your client once. The Pingdom tools appear alongside the tools of everything else you have connected; nothing is configured per connector.

Claude Code

The Memtro plugin registers the server and a skill for when to use it; the tools are then available in every session.

claude plugin marketplace add memtro-org/claude-memtro
claude plugin install memtro@memtro --config api_key=sk-memtro-...

Cursor

Add the server to .cursor/mcp.json in the project, or to the global file under ~/.cursor/.

{
  "mcpServers": {
    "memtro": {
      "url": "https://platform.memtro.com/api/mcp",
      "headers": {
        "Authorization": "Bearer sk-memtro-..."
      }
    }
  }
}

Claude Desktop

Create a personal API key on Dashboard → Profile → API keys. In Claude Desktop add an MCP server of type HTTP with URL https://platform.memtro.com/api/mcp and the header Authorization: Bearer sk-memtro-…

OpenCode

A remote server in opencode.json.

{
  "mcp": {
    "memtro": {
      "type": "remote",
      "url": "https://platform.memtro.com/api/mcp",
      "headers": {
        "Authorization": "Bearer sk-memtro-..."
      }
    }
  }
}

Pi

One command: pi mcp add memtro --url https://platform.memtro.com/api/mcp --bearer-token-env-var MEMTRO_API_KEY. Tools arrive as mcp__memtro__*. The pi-memtro extension registers it for you, alongside Memtro as the model.

Any other client

Add an MCP server of type HTTP (Streamable HTTP, stateless) at https://platform.memtro.com/api/mcp with the header Authorization: Bearer sk-memtro-.... Codex, Zed, Windsurf, Cline and the SDKs all take a remote server this way.

Who may use it

The key identifies the person, and the server offers that person the tools they may use everywhere else in Memtro. A shared Pingdom connection is used by the teams an administrator granted it to, tool by tool, on the Permissions page; a personal connection is used by its owner alone, and its tools that act stay off until the owner allows them. See Teams and permissions and Connectors.

Ask it like this

› Is the website up right now?
› How much downtime did the site have last month?
› When was the API down this week, and for how long?
› Which alerts went out yesterday, and for which checks?
› Schedule a maintenance window for the checkout checks on Sunday from 02:00 to 04:00

Questions

Is this an official Pingdom MCP server?: No. It is Memtro's MCP server with Memtro's Pingdom connector behind it: the connector reads Pingdom through its API with the credentials you connect on Dashboard → Connections, and Pingdom publishes nothing here. The same endpoint carries every other system you connect and Memtro's memory tools.
What does it cost?: Nothing on top of Memtro. One price per organisation by its number of users, from $50 a month for up to 10 users after a 7-day free trial, with every connector, the MCP server, jobs and memory included. You bring your own model keys.
Can it change anything in Pingdom?: Only when you ask, and only what it has been granted: create an uptime check; change a check's settings or who it alerts; pause or resume chosen checks; delete a check and its history (permanent); schedule a maintenance window that silences alerts; change a maintenance window; delete a future maintenance window. Every other tool reads, searches or lists. An administrator grants each acting tool by name per team, and a personal connection acts only after its owner allows it.
Which clients work?: Any MCP client that speaks Streamable HTTP: Claude Code, Cursor, Claude Desktop, OpenCode, Codex, Zed, Windsurf, Cline and the Anthropic and OpenAI SDKs. There is no local process to run; the server is remote and authenticated with your key.