1. Conduid
  2. Developer Tools
  3. consul-mcp
MCP server · Developer Tools

consul-mcp

A consul MCP Server (modelcontextprotocol)

Unclaimed MIT last commit a year ago devtools
54Fair

Scored 13 days ago · breakdown

About consul-mcp

consul-mcp is an MCP server published by kocierik in the Developer Tools category: a consul MCP Server (modelcontextprotocol).

The repository has 18 stars and 4 forks, with the last commit a year ago. Six months or more without a commit doesn't mean the server is broken, but check the open issues before depending on it in production.

Install

From source
git clone https://github.com/kocierik/consul-mcp-server

This server has no ConduID identity, so agent calls to it are not receipted. Pin the version you install and review the source before granting it credentials.

Ask AI

✦

Ask AI about consul-mcp

Powered by Claude · Grounded in docs

I know everything about consul-mcp. Ask me about installation, configuration, usage, or troubleshooting.

Security checks

Static checks derived from the repository 6 days ago. Heuristics on the source, not an audit.

  • ✓README presentThe repository ships documentation.
  • ✓License declaredUsable under a stated license.
  • !Tests presentNo tests found. Behaviour changes may go unnoticed between versions.
  • ✓Dependencies pinnedA lockfile pins dependency versions.
  • ✓No dynamic code executionSource scan found no eval, dynamic Function, or shell execution.
  • !Scoped permissionsDoesn't declare a permission scope. Assume it can do anything its process can.

README

MseeP.ai Security Assessment Badge

Consul MCP Server 🚀

smithery badge

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

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

README fetched from the repository 6 days ago. The original is authoritative.

Questions

About consul-mcp

How do I install consul-mcp?

No package has been published for this server, so install it from source: clone the repository and follow its README.

Is consul-mcp safe to use with an AI agent?

Its trust score is 54 out of 100 (fair). It passes 4 of the 6 static security checks run so far; the failures are listed above. It has no ConduID identity yet, so agent calls to it are not receipted.

Is consul-mcp still maintained?

The last commit was a year ago and 3 open issues. That's long enough that you should check whether the maintainer is responding to issues before depending on it.