Project RAG wiki
MCP server for searching, reading, listing, writing, and appending Markdown wiki content using RAG with ChromaDB.
README
Project RAG wiki
Repository-scoped MCP knowledge service for Markdown wiki content.
It indexes Markdown files from a mounted wiki folder, stores vectors in ChromaDB, and serves:
- MCP endpoint (streamable HTTP)
- health endpoint
The MCP surface is intentionally small at the moment:
- Active tools:
wiki_search,wiki_read,wiki_list,wiki_write,wiki_append
Agent Harness
For an agent consumer of this service, see @ihorleleka/harness.
What This Image Expects
- A wiki folder mounted at
/workspace/wiki - A writable KB state folder mounted at
/workspace/.kb - A shared models cache KB state folder mounted at
/root/.cache/huggingface/hub
Do not bake runtime .kb state into images.
Runtime Defaults
KB_WIKI_ROOT=/workspace/wikiKB_ROOT=/workspace/.kbKB_PORT=1111KB_MCP_PATH=/mcp/KB_HEALTH_PATH=/healthKB_EMBEDDING_MODEL=all-MiniLM-L6-v2KB_CHUNK_SIZE=500KB_CHUNK_OVERLAP=150KB_TOP_K=8KB_MERGE_ADJACENT_WINDOW=1KB_WATCH_INTERVAL_SECONDS=15
Run
docker run --rm \
-p 1111:1111 \
-v "$(pwd)/wiki:/workspace/wiki" \
-v "$(reponame)-kb-data:/workspace/.kb" \
-v "kb-models:/root/.cache/huggingface/hub" \
ihorleleka/project-rag-wiki:latest
Release Automation
Image versioning is driven from the Git tag.
- Tag releases as
X.Y.Z. - The GitHub Actions workflow at [
.github/workflows/docker-release.yml] builds and pushes the Docker image on tag pushes. - The workflow passes the tag name directly into the Docker build as
VERSION. - That same
VERSIONvalue is used for the OCI image label and the installed Python package version inside the image.
Set these repository settings before using the workflow:
- Secret
DOCKERHUB_USERNAME - Secret
DOCKERHUB_TOKEN
Endpoints
- Health:
GET /health - MCP:
POST /mcp/(also mounted at/mcp)
The health response is 200 only when the service startup reindex has completed successfully and the MCP session manager is running.
License
MIT. See LICENSE.
Recommended Servers
playwright-mcp
A Model Context Protocol server that enables LLMs to interact with web pages through structured accessibility snapshots without requiring vision models or screenshots.
Magic Component Platform (MCP)
An AI-powered tool that generates modern UI components from natural language descriptions, integrating with popular IDEs to streamline UI development workflow.
Audiense Insights MCP Server
Enables interaction with Audiense Insights accounts via the Model Context Protocol, facilitating the extraction and analysis of marketing insights and audience data including demographics, behavior, and influencer engagement.
VeyraX MCP
Single MCP tool to connect all your favorite tools: Gmail, Calendar and 40 more.
graphlit-mcp-server
The Model Context Protocol (MCP) Server enables integration between MCP clients and the Graphlit service. Ingest anything from Slack to Gmail to podcast feeds, in addition to web crawling, into a Graphlit project - and then retrieve relevant contents from the MCP client.
Kagi MCP Server
An MCP server that integrates Kagi search capabilities with Claude AI, enabling Claude to perform real-time web searches when answering questions that require up-to-date information.
E2B
Using MCP to run code via e2b.
Neon Database
MCP server for interacting with Neon Management API and databases
Exa Search
A Model Context Protocol (MCP) server lets AI assistants like Claude use the Exa AI Search API for web searches. This setup allows AI models to get real-time web information in a safe and controlled way.
Qdrant Server
This repository is an example of how to create a MCP server for Qdrant, a vector search engine.