Connector guide4-minute read9 MCP tools7 languages

Connect Checkmk to Microsoft Copilot via MCP

Checkmk monitoring: hosts and their configuration, live service states, acknowledged and unhandled problems, host groups and downtimes. REST API on your own site, bearer-style automation user auth.

HCBy HelpCode teamUpdated 4 min read Open-source on GitHub

No credit card · 7-day trial · Self-host alternative available

Checkmk

Checkmk

Checkmk monitoring: hosts and their configuration, live service states, acknowledged and unhandled problems, host groups and downtimes. REST API on your own site, bearer-style automation user auth.

tools

9

Region

DE

Category

Monitoring

Authentication

API Key

Required env vars

CHECKMK_URLCHECKMK_USERNAMECHECKMK_SECRET
Install in one click on Cloud

7-day free trial · No credit card

  • 7-day free trial
    No credit card required
  • GDPR & SOC 2 ready
    EU data residency, audit logs
  • Open-source on GitHub
    Open source · AGPL-3.0
  • Works with ChatGPT, Claude, Gemini
    Any MCP-compatible client

Summary

Checkmk monitoring: hosts and their configuration, live service states, acknowledged and unhandled problems, host groups and downtimes. REST API on your own site, bearer-style automation user auth.

Guided setup

Connect Checkmk to Microsoft Copilot in 2 minutes

Start a free trial on AnythingMCP Cloud, connect Checkmk in the guided setup, then add your MCP URL to Microsoft Copilot. No code and no server to run.

No credit card · 7-day trial · Self-host alternative available

Try asking

Example prompts for Checkmk

Click any prompt to copy it. Paste into Claude, ChatGPT, Cursor, Gemini, Copilot or OpenClaw to run it against this connector.

Checkmk · live via MCP
Share
Opus 4.7

Claude is AI and can make mistakes. Please double-check responses.

💡 No install? Use cloud.anythingmcp.com directly. Sign in, click Connectors → Checkmk, paste your credentials, mint an MCP API key — done. No Docker, no git clone, no local server.

Checkmk + Microsoft Copilot

Checkmk monitoring: hosts and their configuration, live service states, acknowledged and unhandled problems, host groups and downtimes. REST API on your own site, bearer-style automation user auth.

Prerequisites

See the full setup instructions baked into the connector (visible in the in-app store when you select the connector). The required environment variables for this connector are:

CHECKMK_URL, CHECKMK_USERNAME, CHECKMK_SECRET

Step 1 — Get credentials

Setup

  1. In Checkmk create an automation user: Setup → Users → Add user, tick Automation secret for machine accounts, and copy the secret. Give it the guest role for read-only access, or admin if you want the configuration endpoints.
  2. Set CHECKMK_URL to your site root including the site name — https://monitoring.example.com/mysite — with no trailing slash. The site name is part of the path and leaving it out is the usual cause of a 404 that looks like a wrong version.
  3. Set CHECKMK_USERNAME to the automation user and CHECKMK_SECRET to its secret.

…(continued in the in-app connector instructions)

Step 2 — Install the adapter

curl -fsSL https://raw.githubusercontent.com/HelpCode-ai/anythingmcp/main/docker-compose.quickstart.yml -o docker-compose.yml
printf 'JWT_SECRET=%s\nENCRYPTION_KEY=%s\n' "$(openssl rand -hex 32)" "$(openssl rand -hex 32)" > .env
docker compose up -d

Step 3 — Add the connector in Microsoft Copilot

Your server URL: in AnythingMCP, open MCP Servers → the server this connector is on, and copy its URL (https://cloud.anythingmcp.com/mcp/…). Use it wherever this guide shows YOUR_SERVER_ID.

Microsoft Copilot uses MCP servers through agents built in Copilot Studio: you add AnythingMCP to an agent as a tool, then publish the agent to Microsoft 365 Copilot and Teams. Copilot Studio connects from Microsoft's cloud over Streamable HTTP, which AnythingMCP supports.

  1. In Copilot Studio, open your agent (or create one), go to Tools and choose Add a tool → New tool → Model Context Protocol.
  2. Enter a Server name (for example AnythingMCP), a Server description that says what the connector does, and the Server URL https://cloud.anythingmcp.com/mcp/YOUR_SERVER_ID. Copilot Studio uses the description to decide when to call the server.
  3. Under authentication, choose API key, set Type to Header and the header name to X-API-Key, then select Create.
  4. In Add tool, choose Create a new connection, paste an MCP API key from AnythingMCP (MCP Servers → your server → API keys) and select Add to agent.
  5. Try it in the agent's Test pane: ask for something that needs the Checkmk tools.
  6. Select Publish, then Channels → Microsoft 365 and Microsoft Teams, keep Make agent available in Microsoft Copilot selected and choose Add channel. See agent in Teams installs it for you; in Microsoft 365 Copilot, type @ and pick the agent.

Prefer per-user sign-in? Choose OAuth 2.0 → Dynamic discovery instead of an API key: each user then signs in to AnythingMCP the first time the agent calls it.

Self-hosting? Use your instance's public HTTPS address instead of https://cloud.anythingmcp.com. Copilot Studio connects from Microsoft's cloud, so localhost does not work.

Available tools

ToolWhat it does
checkmk_get_versionRead the Checkmk version and edition of this site
checkmk_list_hostsList hosts from the configuration: what has been set up for monitoring, with folder, attributes and effective settings
checkmk_get_host_configRead one host's configuration: its folder, IP address, tags, labels and the attributes it inherits
checkmk_list_host_statesRead the live state of hosts: up, down or unreachable, with the check output and how long each has been that way
checkmk_list_service_statesRead the live state of services — the red, amber and green checks
checkmk_list_host_servicesRead every service on one host with its current state and check output — the drill-down after a host has been flagged
checkmk_list_host_groupsList the host groups configured on this site with their alias, so a query can be scoped to a part of the estate
checkmk_list_downtimesList scheduled downtimes with their host, service, comment, author and window — the explanation for why an alert did not fire
checkmk_list_foldersList the Checkmk folder tree with each folder's title, path and attributes — how hosts are organised and where settings are inherited from

FAQ

Which Copilot is this for? Microsoft 365 Copilot at work, through agents built in Copilot Studio. The Microsoft Copilot app for personal accounts has no option to add your own MCP server.

What do I need? A work account with access to Copilot Studio (a license or a trial) to build the agent. People who use it in Microsoft 365 Copilot or Teams need access to the agent: share it with them, or ask an admin to publish it to the organization. If your organization applies data policies to Power Platform connectors, they cover MCP servers too.

The agent doesn't call the tools. Check that the header name is exactly X-API-Key and that the key belongs to the same MCP server as the URL, and make the server description specific: Copilot Studio uses it to decide when to call the server. Publish the agent again after each change; in an open chat, type "start over" to get the new version.

Next steps

Was this guide helpful?

Connect Checkmk to Microsoft Copilot in 2 minutes

Start a free trial on AnythingMCP Cloud, connect Checkmk in the guided setup, then add your MCP URL to Microsoft Copilot. No code and no server to run.

Related guides