Skip to main content
Glama
youngitn

Consul MCP Server

by youngitn

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
CONSUL_HOSTNoConsul server hostlocalhost
CONSUL_PORTNoConsul server port8500

Instructions

Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.

This server publishes no instructions, or was last inspected before Glama recorded them.

Capabilities

Features and capabilities supported by this server

Protocol revision2025-11-25

CapabilityDetails
tools
{
  "listChanged": true
}

Tools

Functions exposed to the LLM to take actions

NameDescription
get-servicesB

Get running services

register-health-checkB

Register a health check with Consul

deregister-health-checkC

Deregister a health check from Consul

get-health-checksC

Get health checks for a service

get-catalog-nodesB

Get nodes from the catalog

list-catalog-servicesA

List all services in the catalog

get-catalog-serviceB

Get information about a specific service from the catalog

register-serviceC

Register a service with Consul

deregister-serviceB

Deregister a service from Consul

get-kvB

Get a value from the KV store

list-kvC

List keys in the KV store

put-kvC

Put a value in the KV store

delete-kvB

Delete a key from the KV store

list-sessionsA

List all sessions in Consul

destroy-sessionC

Destroy a session in Consul

fire-eventC

Fire a new event

list-eventsC

List all events

create-prepared-queryC

Create a new prepared query

execute-prepared-queryC

Execute a prepared query

get-leaderC

Get the current leader

get-peersB

Get the current peers

get-agent-membersC

Get agent members

reload-agentB

Reload agent configuration

get-agent-selfB

Get agent self information

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

B3.2/5.0

Scored across 24 tools

Disambiguation5/5

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.

Naming Consistency5/5

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.

Tool Count4/5

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.

Completeness4/5

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.

Maintenance

ActivityInactive
ResponsivenessNo issues