Multi-Server MCP Documentation Search
A framework for building self-contained, searchable MCP servers from technical documentation. Create independent documentation servers with hybrid vector + keyword search, ready to distribute and deploy.
Potencialize seu agente
Instalação do publicador. Não é um endpoint do PlugMCP.
Host a copy with our keys and logs.
Ainda não há uma versão empacotada no registro. Siga o README do repositório.
URL remota ou um comando na sua máquina? Como as duas instalações diferem
Rodar no PlugMCP
A new server you create. It is not this listing's official endpoint. Use the publisher install when you want their URL and their credentials.
AbrirDo publicador
A framework for building self-contained, searchable MCP servers from technical documentation. Create independent documentation servers with hybrid vector + keyword search, ready to distribute and deploy.
A framework for building self-contained, searchable MCP servers from technical documentation. Create independent documentation servers with hybrid vector + keyword search, ready to distribute and deploy.
This framework enables you to:
This project supports multiple independent MCP servers, each serving different documentation sources:
/home/james/mcp/
├── servers/ # Standalone MCP servers
│ ├── mojo-manual-mcp/ # Mojo documentation server
│ │ ├── runtime/ # Server code + indexed database
│ │ │ ├── mojo_manual_mcp_server.py
│ │ │ ├── search.py
│ │ │ └── mojo_manual_mcp.db
│ │ ├── config/ # YAML configuration
│ │ │ ├── processing_config.yaml
│ │ │ └── server_config.yaml
│ │ ├── requirements.txt
│ │ └── README.md
│ │
│ └── [future-servers]/ # DuckDB, Python, etc.
│
├── shared/ # Build-time infrastructure (dev only)
│ ├── preprocessing/ # Document processing pipeline
│ ├── embedding/ # Embedding generation scripts
│ ├── templates/ # Templates for new servers
│ └── build/ # Ephemeral build artifacts
│
├── source-documentation/ # Documentation sources
│ ├── mojo/manual/ # Mojo docs (MDX files)
│ └── [other-sources]/
│
└── tools/ # Automation scripts
├── sync_documentation.sh # Sync from upstream repos
├── scaffold_new_mcp.sh # Create new server structure
└── build_mcp.sh # Build server database
Key Design Principles:
/servers/{name}/ is completely self-contained and distributable/shared/ is for development only (not packaged with servers)Get the Mojo documentation MCP server running in 3 steps:
git clone jpotter80/mcp
cd mcp/servers/mojo-manual-mcp
pixi install
Add the Mojo-Manual MCP server, by adding the config to your VS Code settings via mcp.json for global settings. Replace /absolute/path/to/mojo-manual-mcp with your actual server path.
{
"servers": {
"mojo-manual": {
"type": "stdio",
"command": "pixi",
"args": ["run", "serve"],
"cwd": "/absolute/path/to/mojo-manual-mcp"
}
}
}
Note: Pre-built databases are included in the repository. No build step required to run the server.
📖 Detailed guides: See docs/QUICKSTART.md for complete setup instructions.
Environment Variables:
MOJO_DB_PATH: Path to the indexed databaseMAX_SERVER_URL: Embedding server endpoint (automatically started if AUTO_START_MAX=1)EMBED_MODEL_NAME: Sentence transformer model nameAUTO_START_MAX: Set to 1 to auto-start MAX server (recommended)If you want to rebuild the database from scratch or create a new MCP server:
# Full pipeline (all steps)
pixi run mojo-build
# Or step-by-step
pixi run mojo-process # Process documentation
pixi run mojo-generate-embeddings # Generate vectors
pixi run mojo-consolidate # Consolidate data
pixi run mojo-load # Load to DuckLake
pixi run mojo-index # Create indexes
# 1. Scaffold new server structure
./tools/scaffold_new_mcp.sh --name duckdb --doc-type docs --format markdown
# 2. Add documentation to source-documentation/duckdb/docs/
# 3. Build the server
./tools/build_mcp.sh --mcp-name duckdb
# 4. Test the server
python servers/duckdb-docs-mcp/runtime/duckdb_docs_mcp_server.py
📖 Developer guides:
docs/CREATING_NEW_MCP.md - Create new serversCurrently implemented:
User: "How do I declare a variable in Mojo?" ↓
Copyright 2025 James Potter
Licensed under the Apache License, Version 2.0 (the "License");
you may not use this file except in compliance with the License.
You may obtain a copy of the License at
http://www.apache.org/licenses/LICENSE-2.0
Unless required by applicable law or agreed to in writing, software
distributed under the License is distributed on an "AS IS" BASIS,
WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
See the License for the specific language governing permissions and
limitations under the License.
Built with inspiration from Modular, DuckDB, and the Model Context Protocol communities - powered by open-source tools.
A framework for building self-contained, searchable MCP servers from technical documentation. Create independent documentation servers with hybrid vector + keyword search, ready to distribute and depl
Visão geral
A framework for building self-contained, searchable MCP servers from technical documentation. Create independent documentation servers with hybrid vector + keyword search, ready to distribute and deploy.
Ferramentas
Ainda não há lista de ferramentas. Servidores remotos recebem uma após a primeira verificação de saúde.
Perguntas frequentes
Copie nesta página a configuração stdio para Cursor, Claude Desktop, Claude Code ou VS Code. Ela usa a instalação do publicador, não um proxy do PlugMCP.
Este registro não lista nenhuma variável de ambiente obrigatória.
Jpotter80 roda localmente via stdio.
Última verificação: 2026-10-28. A framework for building self-contained, searchable MCP servers from technical documentation. Create independent documentation servers with hybrid vector + keyword search, ready to distribute and deploy.