mcp-knowledge-server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| API_KEY | No | API key for authentication | |
| CHUNK_SIZE | No | Chunk size (default: 1000) | |
| QDRANT_URL | No | Qdrant server URL (default: http://localhost:6333) | |
| ENABLE_AUTH | No | Enable authentication (true/false) | |
| DATABASE_URL | No | Database URL (default: sqlite:///./knowledge.db) | |
| GROQ_API_KEY | No | Groq API key | |
| LLM_PROVIDER | No | LLM provider (ollama, openai, anthropic, gemini, groq, together, openrouter, lmstudio, llamacpp, openai_compatible) | |
| OLLAMA_MODEL | No | Ollama model (default: qwen3:8b) | |
| OPENAI_MODEL | No | OpenAI model (default: gpt-4.1) | |
| CHUNK_OVERLAP | No | Chunk overlap (default: 200) | |
| CHUNK_STRATEGY | No | Chunking strategy (recursive, token, markdown, semantic) | |
| GEMINI_API_KEY | No | Gemini API key | |
| OPENAI_API_KEY | No | OpenAI API key | |
| QDRANT_API_KEY | No | Qdrant API key | |
| EMBEDDING_MODEL | No | Embedding model (default: all-MiniLM-L6-v2) | |
| OLLAMA_BASE_URL | No | Ollama base URL (default: http://localhost:11434) | |
| TOGETHER_API_KEY | No | Together AI API key | |
| ANTHROPIC_API_KEY | No | Anthropic API key | |
| EMBEDDING_PROVIDER | No | Embedding provider (sentence_transformers, openai, ollama, voyage, cohere) | |
| OPENROUTER_API_KEY | No | OpenRouter API key |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| health_checkA | Check the health status of the knowledge server. |
| search_documentsA | Search documents by semantic similarity. |
| rag_answerA | Generate a RAG answer with citations from the knowledge base. |
| add_documentA | Add a document to the knowledge base. |
| update_documentA | Update an existing document by re-ingesting it. |
| delete_documentA | Delete a document from the knowledge base. |
| list_documentsC | List documents in the knowledge base. |
| get_documentA | Get a document by ID. |
| similar_documentsA | Find documents similar to a given chunk. |
| create_collectionA | Create a new document collection. |
| delete_collectionA | Delete a collection and all its vectors. |
| list_collectionsA | List all document collections. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 12 tools
Each tool targets a distinct action on either documents or collections. search_documents and similar_documents are differentiated by input (query text vs. chunk ID), and rag_answer is clearly for answer generation, so there is no ambiguity.
Most tools follow a verb_noun pattern with snake_case (add_document, delete_document, list_collections). However, 'add' and 'create' are used interchangeably for creation, and 'similar_documents' uses an adjective instead of a verb, creating minor inconsistencies.
With 12 tools, the server covers document CRUD, collection management, search/retrieval, and health monitoring. This is well-scoped for a knowledge server and each tool earns its place without redundancy.
The tool surface provides full document lifecycle (add, get, update, delete, list), collection management (create, delete, list), semantic search, similar-document lookup, and RAG. Minor gaps such as missing get_collection or update_collection exist, but core workflows are fully covered.