Skip to main content
Watch: I Built an AI App Without Leaving Databricks

Cloud and hosting - official HashiCorp (Terraform, Vault) server

Consul MCP server

Self-hosted, read-oriented MCP server that lets agents query a Consul cluster: catalog services and nodes, health checks, KV store, ACLs, service mesh intentions and CA, peering, sessions, and operator status. It runs locally from docker.io/hashicorp/consul-mcp-server (oci) with API key auth.

Last verified 15 tools4 sources

Install

VS Code

JSON
{
  "servers": {
    "consul": {
      "command": "docker",
      "args": [
        "run",
        "-i",
        "--rm",
        "-e", "CONSUL_HTTP_ADDR=http://host.docker.internal:8500",
        "hashicorp/consul-mcp-server"
      ]
    }
  }
}

Tools

get_catalog_services
Catalog toolset: list services in the Consul catalog.
get_catalog_nodes
Catalog toolset: list nodes in the catalog.
get_catalog_datacenters
Catalog toolset: list datacenters.
get_agent_members
Agent toolset: list agent members.
get_health_service
Health toolset: health information for a service.
get_health_checks
Health toolset: health checks.
get_kv
KV toolset: read a key from the key-value store.
get_kv_keys
KV toolset: list keys.
get_acl_tokens
ACL toolset: list ACL tokens.
get_acl_policies
ACL toolset: list ACL policies.
get_connect_intentions
Connect toolset: list service mesh intentions.
get_connect_ca_roots
Connect toolset: service mesh CA roots.
get_status_leader
Status toolset: current cluster leader.
get_peerings
Peering toolset: list cluster peering relationships.
get_discovery_chain
Discovery toolset: query a service discovery chain.

As documented on October 17, 2026. A running server reports its current list through tools/list.

Notes and caveats

  • No developer.hashicorp.com page was found; the official GitHub README is the main documentation.
  • Licensed under the Business Source License (BUSL-1.1), not an OSI license.
  • README says it is intended for local use only in trusted networks.
  • Since 0.1.4 the Streamable HTTP server requires TLS by default (opt out with --insecure-no-tls for development only).
  • Consul ACL tokens are needed when ACLs are enabled (X-Consul-Token header in HTTP mode).
  • Namespace tools are Consul Enterprise only.
  • No beta/GA label.

More MCP servers for cloud and hosting

Related reading

FAQ

What does the Consul MCP server do?

Self-hosted, read-oriented MCP server that lets agents query a Consul cluster: catalog services and nodes, health checks, KV store, ACLs, service mesh intentions and CA, peering, sessions, and operator status. The vendor documents 15 tools, including get_catalog_services, get_catalog_nodes, get_catalog_datacenters and get_agent_members.

How do I add the Consul MCP server to VS Code?

HashiCorp (Terraform, Vault) documents a VS Code config; copy it from the VS Code section of this page.

Does the Consul MCP server need authentication?

Yes, API key. Transport: stdio, Streamable HTTP. Status: Unlabelled, last checked October 17, 2026.

Sources

Last verified against 4 HashiCorp (Terraform, Vault) pages, then re-checked independently.

Newsletter

New MCP servers, the week they ship

One email per week. New official MCP servers, the coding tools that support them and how developers wire them up.