Reading the catalogue and KV is the everyday case, but registration, deregistration and key deletion are here too — this is an operator's tool, not a dashboard. There is no auth setting in the configuration, so the reachable Consul endpoint is the security boundary; point it at a cluster you are comfortable letting an agent modify.
An MCP server that exposes Consul's HTTP functionality — service catalogue, health checking, key-value store, sessions, events, prepared queries and agent status — so an agent can inspect and change a Consul cluster in conversation.
- Services — list running services, register and deregister, read service information, browse the catalog
- Health — register and deregister health checks, and read the checks for a service
- Key-value store — get a value, list keys, put a value, delete a key
- Sessions and events — list and destroy sessions; fire and list events
- Prepared queries — create and execute
- Cluster status — current leader, current peers, agent members, agent self information, and system health service information
Node.js and a reachable Consul agent. Clone the repo, `npm install`, `npm run build`, then register `node build/index.js` with your client — Smithery can install it for Claude Desktop. Point it at your cluster with `CONSUL_HOST` (default localhost) and `CONSUL_PORT` (default 8500). No account or key of its own; whatever the Consul endpoint permits is what it can do. Package version 1.0.0. MIT.
One command — npx -y @smithery/cli install @kocierik/consul-mcp-server --client claude