KOVA MCP

Talk to your myGEKKO. An open-source MCP server that connects Claude (and any other MCP client) to myGEKKO building controllers — via the official myGEKKO Query API. Talk to your myGEKKO building controller from Claude — English quickstart below.

"How warm is it in the living room?" · "Which lights are still on?" · "Lower the blinds in the south." — in your own words, straight to your house.

KOVA MCP is the tool for tinkerers and power users. If you want that every day, on your phone and for the whole family — without a terminal: that's the KOVA App (gekkobrain.beikma.com).

Try it in 2 minutes — without your own controller

The public myGEKKO demo controller ("Mustermann") is there for exactly these kinds of tests:

claude mcp add mygekko \
  --env GEKKO_USERNAME=mustermann@my-gekko.com \
  --env GEKKO_KEY=HjR9j4BrruA8wZiBeiWXnD \
  --env GEKKO_GEKKOID=K999-7UOZ-8ZYZ-6TH3 \
  -- uvx --from git+https://github.com/joeexafionbot-dev/kova-mcp mygekko-mcp

Then in Claude Code: "Which systems does my building have? Show me the lights in the living room."

With your own myGEKKO

Prerequisite: controller registered on my-gekko.com and the Plus service "myGEKKO Query API" activated (included in the Home Bundle; generate key under Settings → Globe → Plus Advanced → Plus Query API → Management → Regenerate).

claude mcp add mygekko \
  --env GEKKO_USERNAME=deine@mail.de \
  --env GEKKO_KEY=DEIN-QUERY-API-KEY \
  --env GEKKO_GEKKOID=XXXX-XXXX-XXXX-XXXX \
  -- uvx --from git+https://github.com/joeexafionbot-dev/kova-mcp mygekko-mcp

Claude Desktop (claude_desktop_config.json):

{
  "mcpServers": {
    "mygekko": {
      "command": "uvx",
      "args": ["--from", "git+https://github.com/joeexafionbot-dev/kova-mcp", "mygekko-mcp"],
      "env": {
        "GEKKO_USERNAME": "deine@mail.de",
        "GEKKO_KEY": "DEIN-QUERY-API-KEY",
        "GEKKO_GEKKOID": "XXXX-XXXX-XXXX-XXXX"
      }
    }
  }
}

Also possible locally (LAN instead of cloud): GEKKO_MODE=local + GEKKO_LOCAL_HOST — all variables in .env.example.

What the server can do

Security (deliberately conservative)

• Read-only by default. Controlling requires explicitly GEKKO_ALLOW_WRITE=true.

• Deny-list always stays closed: alarm system, doors/access, cameras are locked even with write permission; critical actions require a second confirmation.

• Credentials only via environment variables, never in files/logs (key is redacted in logs).

• Controller-friendly: rate limits and backoff on 429/470 — otherwise, erroneous requests end up in the controller's alarm log.

Details: SECURITY.md.

English quickstart

MCP server for myGEKKO building controllers (official Query API, cloud or LAN). Read-only by default; writes are opt-in (GEKKO_ALLOW_WRITE=true) and policy-gated (alarm/access/cameras always denied). Try it instantly against the public demo controller using the credentials in the first snippet above, or set GEKKO_USERNAME / GEKKO_KEY / GEKKO_GEKKOID for your own controller. Run via uvx --from git+https://github.com/joeexafionbot-dev/kova-mcp mygekko-mcp.

Development

uv sync && uv run pytest          # Tests
uv run mygekko-mcp --transport stdio
uv run dump-inventory             # read-only Inventar-Dump als JSON

This repo is the release mirror of the KOVA monorepo (that's where CI runs); issues and PRs are still welcome here and will be ported back.

License & Trademarks

MIT. myGEKKO is a trademark of myGEKKO | Ekon GmbH — KOVA MCP is an independent community project and is not published by myGEKKO. The demo credentials above belong to myGEKKO's public demo controller.