Consul MCP Server
# Consul MCP Server (Customized)
This is a customized version of the [Consul MCP Server](https://github.com/kocierik/consul-mcp-server) modified specifically to support **Consul ACL Tokens**.
## What's Changed?
- Added support for `CONSUL_TOKEN` environment variable.
- The underlying Consul client now correctly authenticates to secure clusters (with ACL enabled), allowing it to fetch both Services and Key-Value (KV) configurations without being blocked as an anonymous user.
## Configuration in MCP / Claude / Cursor
Use the following configuration in your `mcp_config.json` (or equivalent IDE settings):
```json
{
"mcpServers": {
"consul-mcp": {
"command": "node",
"args": [
"C:/path/to/your/consul-mcp-server/build/index.js"
],
"env": {
"CONSUL_HOST": "10.4.0.53",
"CONSUL_PORT": "8500",
"CONSUL_TOKEN": "your-acl-token-here"
}
}
}
}
```
## Setup & Build
1. Clone this repository
2. Run `npm install`
3. Run `npm run build`
TDQS
Scored across 24 tools
Every tool targets a distinct resource and action (e.g., get-kv vs put-kv vs delete-kv, register-service vs deregister-service). Potential overlaps like get-services vs list-catalog-services are resolved by context (agent-local vs catalog-wide). No ambiguity.
All tool names follow a consistent verb-noun pattern with hyphens (e.g., get-kv, list-sessions, register-service). Verbs are uniformly imperative and resources are clearly named. No mixing of styles.
24 tools is slightly above the typical well-scoped range, but it covers the core Consul operations (KV, services, health checks, sessions, events, catalog, agent). The count is justified by the breadth of Consul's API.
The tool set covers most essential Consul operations: CRUD for KV, service and health check registration/deregistration, prepared queries, events, and agent info. Missing session creation (only destroy and list) is a minor gap, but overall the surface is comprehensive.