semarcy-mcp
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@semarcy-mcp Explain xDM data modeling concepts"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
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-mcp2. 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 .envEdit .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 --clearThen 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.pyAvailable MCP Tools
Tool | Description |
| Search Semarchy documentation with a natural language query. Returns relevant chunks with source URLs. |
| List available topic areas across Semarchy products. Useful for discovering what documentation is indexed. |
Environment Variables
Variable | Required | Description |
| Yes | Voyage AI API key for embedding search queries |
| No | Override ChromaDB storage path (default: |
Available Tools
2 toolslist_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
Scored across 2 tools
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.
Both names follow a consistent verb_noun pattern (search_semarchy_docs, list_semarchy_topics) and use snake_case uniformly.
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.
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
Related MCP Connectors
MCP server unifying ERPs, CRMs, APIs and knowledge base for Claude, ChatGPT and Gemini.
MCP server for AI access to Swagger by SmartBear.
MCP server that lets AI assistants use all OneSchema features exposed via the public API.
Token-free MCP server for structured RevoGrid Core, Pro, and Enterprise knowledge retrieval.
Related MCP Servers
AlicenseNot gradedqualityDmaintenanceMCP server that exposes NetApp AI Data Engine's RAG search for semantic document retrieval.51 PyPIBSD 3-Clause- AlicenseAqualityDmaintenanceAn MCP server that serves documentation and enables AI-powered search, Q\&A, and document analysis for developer tools and guides.54MIT
- AlicenseNot gradedqualityBmaintenanceAn 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 npmMIT
- AlicenseNot gradedqualityDmaintenanceAn 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