Is this an official Checkmk MCP server?

No. It is Memtro's MCP server with Memtro's Checkmk connector behind it: the connector reads Checkmk through its API with the credentials you connect on Dashboard → Connections, and Checkmk 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 Checkmk?

Only when you ask, and only what it has been granted: acknowledge a host problem; acknowledge a service problem; remove an acknowledgement from a host or service; start a service discovery (refresh) on a host. 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

Checkmk MCP server

Checkmk in any MCP client, through Memtro: Checkmk does not publish this server. Memtro's Checkmk connector reads Checkmk 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

Checkmk monitoring on your own site: services in WARN, CRIT or UNKNOWN across the site or one host, with output, last check, hard or soft, acknowledged and in-downtime flags, one host's services with counts per state, one service, and the site's version; when you ask, can acknowledge a host or service problem (notifying its contacts if you say so), remove an acknowledgement, and start a service discovery on a host.

Reads

checkmk_site_infoThe Checkmk site's name, edition and version.
checkmk_problem_servicesServices that are not OK on the Checkmk site right now: host, service, state (WARN, CRIT, UNKNOWN), its output, last check, hard or soft state…
checkmk_host_servicesEvery service monitored on one Checkmk host, worst first, with state, output, last check and acknowledged or downtime flags, and a count per state.
checkmk_serviceOne service on one Checkmk host: state, hard or soft, and when it was last checked.

Acts, when you ask

These change something in Checkmk. 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.

checkmk_acknowledge_host_problemAcknowledges the current problem on one Checkmk host (it must be DOWN or UNREACHABLE), with your comment, so it stops alerting as unhandled.
checkmk_acknowledge_service_problemAcknowledges the current problem on one service of one Checkmk host (it must be WARN, CRIT or UNKNOWN), with your comment.
checkmk_remove_acknowledgementRemoves the acknowledgement from one Checkmk host, or from one of its services when service_description is given…
checkmk_run_service_discoveryStarts a service discovery (mode refresh) on one Checkmk host as a background job on the site.

Connect it

First connect Checkmk on Dashboard → Connections, then add Memtro to your client once. The Checkmk 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 Checkmk 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

› What is critical in Checkmk right now?
› Which problems on db01 are unacknowledged?
› Show me every service on web02, worst first.
› When was the backup service on db01 last checked?
› Acknowledge the disk space problem on db01 with a note that Tom is on it.

Questions

Is this an official Checkmk MCP server?: No. It is Memtro's MCP server with Memtro's Checkmk connector behind it: the connector reads Checkmk through its API with the credentials you connect on Dashboard → Connections, and Checkmk 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 Checkmk?: Only when you ask, and only what it has been granted: acknowledge a host problem; acknowledge a service problem; remove an acknowledgement from a host or service; start a service discovery (refresh) on a host. 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.