mcp-acdc-server

Agent Content Discovery Companion (ACDC) MCP Server

A high-performance Model Context Protocol (MCP) server for AI agents to discover and search local content. Features full-text search powered by Bleve, dual transport support (stdio/SSE), and flexible authentication.

🌐 Why ACDC?

ACDC solves the challenge of managing team-specific knowledge in the AI agent space. While general-purpose LLMs are powerful, they lack the context of your team's specific tools, patterns, and standards.

ACDC provides a bridge between your content repositories and AI agents, making it easy to manage and develop relevant context at scale.

Deployment Patterns

• Centralized (SSE): For large teams, deploy ACDC as a central service. Agents across the organization can connect via the SSE interface, making knowledge management transparent and consistent.
• Localized (stdio): For smaller teams or individual developers, running ACDC locally might be good enough. Point it at a Git-managed content repository and pull changes as needed.

Docker (Quick Start):

cd examples/docker-local-content
docker-compose up -d

Homebrew (macOS):

brew install sha1n/tap/acdc-mcp
acdc-mcp

Or point it at a dedicated content repository:

acdc-mcp --content-dir ./content

✨ Features

• Full-Text Search — Fast indexing with stemming, fuzzy matching, and configurable boosting
• Dynamic Resource Discovery — Automatic scanning of content directories
• Dynamic Prompt Discovery — Automatic scanning of prompt templates
• MCP Compliant — Seamless integration with AI agents
• Dual Transport — stdio for local agents, sse for remote/Docker
• Authentication — Optional basic auth or API key protection
• Cross-Platform — Linux, macOS, and Windows

� Installation

Docker

docker pull sha1n/mcp-acdc-server:latest

Homebrew (macOS)

brew install sha1n/tap/acdc-mcp

Linux and Windows users can download a release archive or use the Docker image.

Build from Source

See Development Guide for build instructions.

🏃 Running

Stdio Transport (default)

acdc-mcp

Or point it at a dedicated content repository:

acdc-mcp --content-dir ./content

SSE Transport

acdc-mcp --transport sse --content-dir ./content

Docker

The image defaults to the stdio transport, so serving over HTTP requires setting ACDC_MCP_TRANSPORT=sse — publishing the port alone is not enough:

docker run -p 8080:8080 \
  -e ACDC_MCP_TRANSPORT=sse \
  -v $(pwd)/content:/app/content \
  sha1n/mcp-acdc-server:latest

Health Check (SSE Only)

The SSE server exposes an unauthenticated /health endpoint that returns 200 OK. This can be used as a liveness or readiness probe in Kubernetes:

livenessProbe:
  httpGet:
    path: /health
    port: 8080
readinessProbe:
  httpGet:
    path: /health
    port: 8080

⚙️ Configuration