Consul MCP Server
Provides tools for managing Consul services, health checks, key-value store, sessions, events, prepared queries, status, agent, and system health information.
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@Consul MCP Server List all running services in Consul"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
Consul MCP Server (Customized)
This is a customized version of the Consul MCP Server modified specifically to support Consul ACL Tokens.
What's Changed?
Added support for
CONSUL_TOKENenvironment 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.
Related MCP server: Consul MCP Server
Configuration in MCP / Claude / Cursor
Use the following configuration in your mcp_config.json (or equivalent IDE settings):
{
"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
Clone this repository
Run
npm installRun
npm run build
Available Tools
24 toolscreate-prepared-queryC
Create a new prepared query
Inputs: name, service, nearestN, datacenters.
delete-kvB
Delete a key from the KV store
Inputs: key.
deregister-health-checkC
Deregister a health check from Consul
Inputs: id.
deregister-serviceB
Deregister a service from Consul
Inputs: id.
destroy-sessionC
Destroy a session in Consul
Inputs: id.
execute-prepared-queryC
Execute a prepared query
Inputs: id.
fire-eventC
Fire a new event
Inputs: name, payload.
get-agent-membersC
Get agent members
Inputs: no named parameters.
get-agent-selfB
Get agent self information
Inputs: no named parameters.
get-catalog-nodesB
Get nodes from the catalog
Inputs: no named parameters.
get-catalog-serviceB
Get information about a specific service from the catalog
Inputs: service.
get-health-checksC
Get health checks for a service
Inputs: service.
get-kvB
Get a value from the KV store
Inputs: key.
get-leaderC
Get the current leader
Inputs: no named parameters.
get-peersB
Get the current peers
Inputs: no named parameters.
get-servicesB
Get running services
Inputs: no named parameters.
list-catalog-servicesA
List all services in the catalog
Inputs: no named parameters.
list-eventsC
List all events
Inputs: name.
list-kvC
List keys in the KV store
Inputs: prefix.
list-sessionsA
List all sessions in Consul
Inputs: no named parameters.
put-kvC
Put a value in the KV store
Inputs: key, value.
register-health-checkB
Register a health check with Consul
Inputs: id, ttl, http, name, +4 more.
register-serviceC
Register a service with Consul
Inputs: id, name, port, tags, +1 more.
reload-agentB
Reload agent configuration
Inputs: no named parameters.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
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.
Related MCP Connectors
Model Context Protocol server for the Apideck Unified API. Connect any MCP-compatible agent framework to 100+ accounting systems, HRIS platforms, file storage providers, and more through one integration. More information https://www.apideck.com/mcp-server
A Model Context Protocol server for Wix AI tools
A comprehensive Model Context Protocol (MCP) server that enables AI assistants to interact with yo…
The Mercado Pago MCP Server implements the Model Context Protocol to provide AI agents and LLMs with access to Mercado Pago's APIs and tools within compatible development environments. It acts as an intermediary that translates Mercado Pago resources into executable functions (tools) that AI applications can invoke to perform actions and automate flows. The server simplifies integration, enables using documentation to implement or improve code, and optimizes operations through natural language interactions without manual implementations.
Related MCP Servers
- AlicenseAqualityDmaintenanceA Model Context Protocol server that allows language models to manage Hetzner Cloud resources through structured functions, including servers, volumes, firewalls, and SSH keys.30153MIT
- AlicenseBqualityDmaintenanceProvides access to Consul functionality (services, health checks, KV store, sessions, events, queries, etc.) through a standardized Model Context Protocol interface.2418MIT
- AlicenseBqualityCmaintenanceA Model Context Protocol server that provides seamless integration with Coroot observability platform, enabling monitoring of applications, analysis of performance metrics, examination of logs and traces, and management of infrastructure through Coroot's comprehensive API.6147 PyPI16MIT
- AlicenseNot gradedqualityDmaintenanceModel Context Protocol server that standardizes tool discovery, execution, and context management for AI applications.MIT