Skip to main content
Glama
Sign In
deenesjakoruzh
Consul MCP Server

Consul MCP Server

by kocierik
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript

Consul MCP Server 🚀

A Model Context Protocol (MCP) server that provides access to Consul's functionality through a standardized interface.

Features

The server provides access to the following Consul functionality:

Service Management

  • List running services

  • Register and deregister services

  • Get service information

  • List catalog services

  • Get catalog service information

Health Checks

  • Register health checks

  • Deregister health checks

  • Get health checks for services

Key-Value Store

  • Get values from KV store

  • List keys in KV store

  • Put values in KV store

  • Delete keys from KV store

Sessions

  • List sessions

  • Destroy sessions

Events

  • Fire events

  • List events

Prepared Queries

  • Create prepared queries

  • Execute prepared queries

Status

  • Get current leader

  • Get current peers

Agent

  • Get agent members

  • Get agent self information

System

  • Get system health service information

Related MCP server: Tailscale MCP Server

Configuration

The server can be configured using environment variables:

  • CONSUL_HOST: Consul server host (default: localhost)

  • CONSUL_PORT: Consul server port (default: 8500)

Usage

  1. Start the server:

node build/index.js

  1. The server will connect to Consul and make all functionality available through the MCP interface.

Development

  1. Install dependencies:

npm install

  1. Build the project:

npm run build

  1. Run inspector:

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

Claude config

{
    "mcpServers": {
        "consul-mcp": {
            "command": "node",
            "args": [
                "/ABSOLUTE/PATH/TO/PARENT/FOLDER/consul-mcp-server/build/index.js"
            ]
        }
    }
}

Installing via Smithery

To install Consul Server for Claude Desktop automatically via Smithery:

npx -y @smithery/cli install @kocierik/consul-mcp-server --client claude

License

MIT

Available Tools

24 tools
create-prepared-queryC

Create a new prepared query

Inputs: datacenters, name, nearestN, service.

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-nodesC

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-peersC

Get the current peers

Inputs: no named parameters.

get-servicesC

Get running services

Inputs: no named parameters.

list-catalog-servicesB

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-sessionsB

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: http, id, interval, name, +4 more.

register-serviceC

Register a service with Consul

Inputs: address, id, name, port, +1 more.

reload-agentC

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…

    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    B3/5.0

    Scored across 24 tools

    Disambiguation5/5

    Each tool has a distinct purpose targeting specific Consul resources and actions, with clear boundaries between operations like KV store management (get-kv, put-kv, delete-kv), service registration/deregistration, health checks, catalog queries, and agent operations. No overlapping or ambiguous tool purposes exist.

    Naming Consistency5/5

    All tools follow a consistent verb-noun naming pattern with hyphens (e.g., get-kv, register-service, list-events), maintaining perfect uniformity throughout the set. The naming convention is predictable and enhances readability across all 24 tools.

    Tool Count3/5

    With 24 tools, the count is borderline high for a single server, potentially feeling heavy for agents to navigate. However, given Consul's broad scope (service discovery, KV store, health checks, events, sessions, etc.), it covers multiple domains comprehensively, making the count reasonable though on the upper edge of typical scoping.

    Completeness5/5

    The tool set provides complete coverage for Consul's core functionalities, including full CRUD operations for KV store (put, get, delete, list), service lifecycle (register, deregister, get, list), health checks (register, deregister, get), catalog queries, events, sessions, and agent management. No obvious gaps exist for the inferred domain.

    Maintenance

    ActivityNo data
    ResponsivenessOutdated data

    Resources

    Related MCP Connectors

    Related MCP Servers

    Appeared in Searches