HashiCorp Consul MCP Logo

About HashiCorp Consul MCP

HashiCorp's Consul MCP server puts a running Consul datacenter behind a Model Context Protocol interface. An agent can read the service catalog to see which services are registered, which nodes they run on, and what tags and metadata they carry, then check the health status reported by the checks attached to any service or node instance. That turns a question like whether a given service is healthy across a datacenter into one call instead of a CLI session. The key value store is exposed as well, so configuration keys can be listed and read, and written where the token permits. Service mesh users can reach mesh objects such as intentions and configuration entries, which describe who is allowed to talk to whom. Access is governed by a Consul ACL token: the agent sees exactly what that token's policies allow, and nothing is bypassed for convenience. The server is published as open source by HashiCorp and targets platform and SRE teams. It is useful during incident triage, when the question is which instances are failing their checks, during onboarding, when someone needs a map of what services exist and how they connect, and inside a coding assistant that needs to read the configuration values an application expects at runtime.