consul

This MCP server exposes Consul functionality through the MCP interface, allowing you to manage services, health checks, KV store operations, sessions, events, prepared queries, and more against a connected Consul cluster. After starting the server, you can issue MCP requests to list and register services, query catalog information, manage health checks, perform KV read/write/delete operations, and interact with Consul’s sessions, events, and system data. The server connects to a Consul endpoint defined by CONSUL_HOST and CONSUL_PORT, and translates MCP operations into corresponding Consul API calls.

To use it, ensure your MCP client points to the server and that CONSUL_HOST/CONSUL_PORT are set so the server can reach Consul. Typical workflows include listing services, registering a temporary service, pushing KV values, creating prepared queries, and inspecting agent information. The included Claude integration demonstrates how to embed this MCP server in Claude via the mcpServers configuration, enabling Claude to route MCP requests to Consul through this server.

Prerequisites:

• Node.js (LTS) and npm installed
• Access to a running Consul cluster (or a reachable Consul agent)

Installation steps:

1. Clone the repository or download the package containing the Consul MCP server.

2. Install dependencies:

npm install

3. Build the project (if required by the project structure):

npm run build

4. Run the server locally (example, adjust paths as needed):

node build/index.js

5. Verify the server is running and reachable by your MCP client. If you are using Claude, you can reference the Claude config example to embed the server.

Optional: Run with inspector for debugging:

npm run build && npx @modelcontextprotocol/inspector node build/index.js

Environment variables can be provided to point to your Consul instance:

• CONSUL_HOST: your Consul host (default: localhost)
• CONSUL_PORT: your Consul port (default: 8500)

If you change Consul connection details, restart the MCP server for the changes to take effect.

Notes and tips:

• The server relies on a running Consul instance; ensure network access between the MCP server and Consul.
• If you encounter connection issues, verify CONSUL_HOST and CONSUL_PORT, and confirm that Consul is listening on the expected interface.
• For Claude integration, use the provided Claude config example to map the MCP server into Claude’s environment.
• When deploying, consider setting up proper authentication/ACLs in Consul and securing MCP endpoints if exposed publicly.
• The environment variables are documented in the README; placeholders in the mcpConfig should be replaced with actual host/port values in production.