Skip to main content
Glama
Consul MCP Server
by kocierik

Consul MCP 서버 🚀

표준화된 인터페이스를 통해 Consul 기능에 대한 액세스를 제공하는 MCP(모델 컨텍스트 프로토콜) 서버입니다.

특징

서버는 다음 Consul 기능에 대한 액세스를 제공합니다.

서비스 관리

  • 실행 중인 서비스 목록

  • 서비스 등록 및 등록 취소

  • 서비스 정보를 얻으세요

  • 카탈로그 서비스 목록

  • 카탈로그 서비스 정보 받기

건강 검진

  • 건강 검진 등록

  • 건강 검진 등록 취소

  • 서비스에 대한 건강 검진을 받으세요

키-값 저장소

  • KV 저장소에서 값 가져오기

  • KV 스토어의 키 목록

  • KV 저장소에 값을 넣으세요

  • KV 스토어에서 키 삭제

세션

  • 세션 목록

  • 세션 파괴

이벤트

  • 화재 발생

  • 이벤트 목록

준비된 쿼리

  • 준비된 쿼리를 만듭니다

  • 준비된 쿼리 실행

상태

  • 현재 리더 가져오기

  • 현재 동료를 얻으세요

대리인

  • 에이전트 멤버를 얻으세요

  • 에이전트 자기 정보 받기

체계

  • 시스템 상태 서비스 정보 가져오기

Related MCP server: Tailscale MCP Server

구성

서버는 환경 변수를 사용하여 구성할 수 있습니다.

  • CONSUL_HOST : Consul 서버 호스트(기본값: localhost)

  • CONSUL_PORT : Consul 서버 포트(기본값: 8500)

용법

  1. 서버를 시작합니다:

지엑스피1

  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"
            ]
        }
    }
}

특허

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…

    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