Skip to main content
Glama
Consul MCP Server
by kocierik

Consul MCP 服务器

模型上下文协议 (MCP) 服务器通过标准化接口提供对 Consul 功能的访问。

特征

该服务器提供对以下 Consul 功能的访问:

服务管理

  • 列出正在运行的服务

  • 注册和注销服务

  • 获取服务信息

  • 列出目录服务

  • 获取目录服务信息

健康检查

  • 注册健康检查

  • 取消注册健康检查

  • 获取服务健康检查

键值存储

  • 从 KV 存储获取值

  • 列出 KV 存储中的键

  • 将值放入 KV 存储中

  • 从 KV 存储中删除键

会议

  • 列出会话

  • 销毁会话

活动

  • 火灾事件

  • 列出事件

准备好的查询

  • 创建准备好的查询

  • 执行准备好的查询

地位

  • 获取当前领导者

  • 获取当前同行

代理人

  • 获取代理成员

  • 获取座席自身信息

系统

  • 获取系统健康服务信息

Related MCP server: Tailscale MCP Server

配置

可以使用环境变量来配置服务器:

  • CONSUL_HOST :Consul 服务器主机(默认值:localhost)

  • CONSUL_PORT :Consul 服务器端口(默认值:8500)

用法

  1. 启动服务器:

node build/index.js
  1. 该服务器将连接到 Consul 并通过 MCP 接口提供所有功能。

发展

  1. 安装依赖项:

npm install
  1. 构建项目:

npm run build
  1. 运行检查器:

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

克劳德配置

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

执照

麻省理工学院

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…

    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

    ActivityInactive
    ResponsivenessNo recent community issues

    Related MCP Connectors

    Related MCP Servers