kener-mcp

An MCP server for Kener v4 status pages. It lets an AI agent (Claude Code, Claude Desktop, or any MCP client) read monitors and incidents, and create, update, and resolve incidents.

Tested against Kener 4.1.7.

Tools

There is no delete tool. Delete incidents in the Kener dashboard.

The read tools have the MCP readOnlyHint annotation, so clients can allow them without a prompt and still ask before a write.

Configuration

One server serves one Kener instance. To use more than one instance, register one server per instance, each with its own URL and key.

The --url, --api-key-cmd, and --name flags override the matching variables. There is no --api-key flag, because process lists show command-line arguments.

API key command

Use KENER_API_KEY_CMD (or --api-key-cmd) to get the key from a secret manager, so that the key is not in your MCP config:

• The command runs on the first tool call, not at server start. A slow or locked secret manager does not block the MCP handshake.
• The key is kept in memory. If Kener rejects it (HTTP 401), the next tool call runs the command again, so a rotated key is picked up.
• The command is split like a shell command line (shlex) but does not run in a shell. Pipes, $VARS, and ~ are not expanded. For those, point it at a script.
• The command must print only the key. If it fails, the error shows its exit code and stderr, never its stdout.

Examples:

# 1Password
KENER_API_KEY_CMD='op read "op://Infra/Kener API key/api_key"'
# macOS Keychain
KENER_API_KEY_CMD='security find-generic-password -s kener -w'
# pass
KENER_API_KEY_CMD='pass show kener/api-key'

Install

uv tool install kener-mcp

Or run it without installing: uvx kener-mcp. With pip: pip install kener-mcp.

Then check the URL and key:

KENER_URL=https://status.example.com KENER_API_KEY=... kener-mcp check

Register with Claude Code

claude mcp add kener -s user \
  -e KENER_URL=https://status.example.com \
  -e KENER_API_KEY=your-key \
  -- kener-mcp

For two instances, add two servers:

claude mcp add kener-prod -s user -e KENER_URL=https://status.example.com -e KENER_API_KEY=... -- kener-mcp
claude mcp add kener-staging -s user -e KENER_URL=https://status-staging.example.com -e KENER_API_KEY=... -- kener-mcp

With a key command instead of a stored key:

claude mcp add kener -s user -- kener-mcp \
  --url https://status.example.com \
  --api-key-cmd 'op read "op://Infra/Kener API key/api_key"'

Register with Claude Desktop (or another MCP client)

{
  "mcpServers": {
    "kener": {
      "command": "kener-mcp",
      "env": {
        "KENER_URL": "https://status.example.com",
        "KENER_API_KEY": "your-key"
      }
    }
  }
}

Kener API notes

These notes describe Kener 4.1.7 as read from its source:

• An update is POST /api/v4/incidents/{id}/comments with {"comment": "...", "state": "..."}. The Kener docs show message and status. The server rejects those names.
• There is no resolve endpoint. A comment with state RESOLVED sets the incident state and its end time. PATCH /api/v4/incidents/{id} cannot change the state.
• API-created incidents start in state INVESTIGATING.
• Updates posted through the API do not email subscribers (rajnandan1/kener#886). Updates made in the dashboard do.

Development

uv sync
uv run pytest
uv run ruff check . && uv run ruff format --check .

The tests use respx to check the HTTP request shapes. They call no real Kener instance.

Releasing

1. Bump the version: uv version --bump patch (or minor / major).
2. Move the Unreleased notes in CHANGELOG.md under the new version.
3. Commit, push, and wait for CI to pass.
4. Publish a GitHub release with the tag v<version>, for example gh release create v0.1.1 --generate-notes.

The Release workflow then checks that the tag matches the version in pyproject.toml, runs the tests, builds the package, and publishes it to PyPI with Trusted Publishing.

License

MIT. See LICENSE.