Creativity · MCP — server

MCP Consul Server

HashiCorp Consul provides service discovery, health checking, and a distributed KV store. The MCP Consul Server turns those into tools for MCP clients: list registered services, check health status, read or write KV entries — handy for running chat-assisted troubleshooting on microservices estates.

MCP facts

Kind: server
Ecosystem: anthropic-mcp
Language: Go
Transports: stdio

Capabilities

Tools: list_services, list_nodes, health_checks, kv_get, kv_put
ACL-token authorization
Supports Consul 1.15+ and Consul Enterprise

Install

go install github.com/community/mcp-consul@latest

Configuration

{
  "mcpServers": {
    "consul": {
      "command": "mcp-consul",
      "env": {
        "CONSUL_HTTP_ADDR": "http://consul.service.consul:8500",
        "CONSUL_HTTP_TOKEN": "<acl-token>"
      }
    }
  }
}

Frequently asked questions

Should the model be allowed to write KV entries?

Only in non-production or with a tightly scoped ACL. KV drives config for many services — one wrong write can cascade into an outage.

Does it see Consul Connect service mesh data?

Yes — intentions and service mesh metadata are exposed where the Consul API surfaces them, subject to ACL policy.

What else do I need?

Pair it with a Kubernetes MCP or a logs MCP for richer incident-response workflows from the chat window.

Sources

Consul API Documentation — accessed 2026-04-20
Model Context Protocol — accessed 2026-04-20