Skip to main content
Glama

semarcy-mcp

MCP server that provides AI assistants with RAG-powered access to Semarchy documentation (xDM, xDI, xDG). Connect it to Claude Desktop or any MCP-compatible client to search and retrieve relevant Semarchy docs.

Prerequisites

Related MCP server: Dedalus MCP Documentation Server

Quick Start (Docker)

1. Clone the repo

git clone <repo-url> && cd semarcy-mcp

2. Build the Docker image

The image includes pre-ingested documentation, so it's ready to use immediately.

docker build -t semarcy-mcp .

3. Set up your API key

cp .env.example .env

Edit .env and replace the placeholder with your actual Voyage AI key. This file is used by Docker (--env-file) and by local development (loaded automatically via python-dotenv).

4. Configure Claude Desktop

Add the server to your Claude Desktop config (~/Library/Application Support/Claude/claude_desktop_config.json on macOS):

{
  "mcpServers": {
    "semarcy-docs": {
      "command": "docker",
      "args": [
        "run", "-i", "--rm",
        "--env-file", "/absolute/path/to/semarcy-mcp/.env",
        "semarcy-mcp"
      ]
    }
  }
}

Replace /absolute/path/to/semarcy-mcp/.env with the actual path to your .env file.

5. Restart Claude Desktop

You can now ask Claude questions about Semarchy xDM, xDI, and xDG.

Updating the Documentation Index

The Docker image includes pre-ingested documentation, so most users never need to re-ingest. If Semarchy updates their docs and you want the latest content:

docker run --rm --env-file .env -v semarcy-data:/data/chroma semarcy-mcp \
  ingest --db-path /data/chroma --clear

Then update your Claude Desktop config to mount the same volume:

{
  "mcpServers": {
    "semarcy-docs": {
      "command": "docker",
      "args": [
        "run", "-i", "--rm",
        "--env-file", "/absolute/path/to/semarcy-mcp/.env",
        "-v", "semarcy-data:/data/chroma",
        "semarcy-mcp"
      ]
    }
  }
}

Local Development (without Docker)

# Install dependencies
uv sync

# Set up your API key (python-dotenv loads this automatically)
cp .env.example .env
# Edit .env with your actual key

# Ingest docs (takes a while on first run)
uv run semarcy-mcp ingest

# Run the MCP server
uv run semarcy-mcp serve

# Test with MCP Inspector
mcp dev src/semarcy_mcp/server.py

Available MCP Tools

Tool

Description

search_semarchy_docs

Search Semarchy documentation with a natural language query. Returns relevant chunks with source URLs.

list_semarchy_topics

List available topic areas across Semarchy products. Useful for discovering what documentation is indexed.

Environment Variables

Variable

Required

Description

VOYAGE_API_KEY

Yes

Voyage AI API key for embedding search queries

SEMARCY_DB_PATH

No

Override ChromaDB storage path (default: ./chroma_data locally, /data/chroma in Docker)

Available Tools

2 tools
list_semarchy_topicsA

List available Semarchy documentation topics and products.

Returns an overview of what documentation has been indexed, including products and page counts.

Inputs: no named parameters. Returns: result

search_semarchy_docsB

Search Semarchy documentation (xDM, xDI, xDG) using semantic search.

Args:
    query: Natural language search query about Semarchy products.
    product: Filter by product: "xdm", "xdi", or "xdg". Omit to search all.
    max_results: Maximum number of results to return (default 5).

Inputs: query (required), product, max_results. Returns: result

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    TDQS

    A3.6/5.0

    Scored across 2 tools

    Disambiguation5/5

    The two tools have clearly distinct purposes: one performs semantic searching, the other lists available topics/products for browsing. An agent can easily choose between them.

    Naming Consistency5/5

    Both names follow a consistent verb_noun pattern (search_semarchy_docs, list_semarchy_topics) and use snake_case uniformly.

    Tool Count3/5

    Two tools is quite thin for a documentation server; while search and topic listing cover the core, a third tool (e.g., get page by ID) would make the surface more useful.

    Completeness3/5

    Search and topic listing cover discovery, but there is no way to retrieve a full documentation page by identifier, which is a common need after finding a result. This notable gap limits depth of use.

    Maintenance

    ActivityInactive
    ResponsivenessNo recent community issues

    Related MCP Connectors

    Related MCP Servers

    • A
      license
      Not graded
      quality
      D
      maintenance
      MCP server that exposes NetApp AI Data Engine's RAG search for semantic document retrieval.
      51 PyPI
      BSD 3-Clause
    • A
      license
      Not graded
      quality
      B
      maintenance
      An MCP server that provides tools for retrieving and processing documentation through vector search, enabling AI assistants to augment their responses with relevant documentation context.
      10 npm
      MIT
    • A
      license
      Not graded
      quality
      D
      maintenance
      An MCP server that gives AI coding assistants access to up-to-date API documentation via RAG by crawling documentation sites, indexing them into a vector store, and enabling semantic queries.
      MIT