knowledge_base_mcp

# Knowledge Base MCP An MCP Server for creating Knowledge Bases and searching them! ## 100% Local, Fast, and Easy to Use The MCP Server uses DuckDB by default which runs in-process and persists to disk. Everything from the vector store, to the embeddings, to the reranker, crawler, etc is all local. It does not require any cloud services or external dependencies. Even more important, the Knowledge Base MCP Server is very fast at indexing, embedding, searching, and reranking compared to other solutions. ## Quick Start Just add the following to your MCP Server configuration! ```json "Knowledge Base": { "command": "uvx", "args": [ "knowledge_base_mcp", "duckdb", "persistent", "run" ] } ``` # Features ## Search Features - **Knowledge Base Management**: Organize your data into knowledge bases. - **Semantic Search**: Query across one or more knowledge bases using semantic search. - **Multiple Vector Store Backends**: Works with DuckDB and Elasticsearch. Search results are automatically reranked using a reranker model to try to achieve the highest quality results. ## Document Ingestion Features - **Website Ingestion**: Crawl websites into a knowledge base. - **Git Repository Ingestion**: Load and ingest a Git repository into a knowledge base. - **Directory Ingestion**: Load and ingest a directory into a knowledge base. The Knowledge Base MCP Server uses advanced hierarchical + semantic chunking techniques to create embeddings for your data. ## Usage ### Command-Line Interface The CLI supports both DuckDB (in-memory or persistent) and Elasticsearch as vector store backends. #### DuckDB (Persistent) To run the server with a persistent DuckDB store, which will save your knowledge bases to disk: ```bash uv run knowledge_base_mcp duckdb persistent --docs-db-dir ./storage --docs-db-name documents.duckdb --code-db-dir ./storage --code-db-name code.duckdb run ``` - `--docs-db-dir`: Directory to store document knowled…