KnowledgeBase MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| KB_VOLUME | Yes | Path to the knowledge base Database directory on external storage, e.g. /Volumes/KnowledgeBase/Database. | |
| KB_ENABLE_SEMANTIC | No | Set to "1" to enable optional FastEmbed local vector semantic retrieval. | 0 |
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 |
|---|---|
| kb_statusA | Report whether the drive is mounted and basic index statistics. |
| kb_searchA | Search the knowledge base and return the most relevant text chunks. :param query: Natural-language question or keywords (Chinese/English). :param top_k: Number of chunks to return (1-30). :param mode: "keyword" (BM25/substring), "semantic" (embeddings), or "hybrid" (both, rank-fused). "hybrid" is recommended. |
| kb_reindexA | Scan the volume and update the search index incrementally. :param full: When true, re-extract every file instead of only changed ones. |
| kb_read_documentA | Return the extracted plain text of one document (for quoting/summarising). :param relpath: Path relative to the volume root, e.g. |
| kb_list_treeC | List the directory tree under |
| kb_scan_inboxA | List files in Use the previews to decide a target category and a new name, then call
:func: |
| kb_create_directoryB | Create a directory (and parents) under the volume root. |
| kb_move_fileB | Move (and optionally rename) a file into a category directory. The search index is updated in place — no reindex needed afterwards. :param src_rel: Current path, e.g. |
| kb_rename_fileA | Rename a file in place (same directory). Index is kept in sync. |
| kb_logB | Append a line to the organize log ( |
| kb_update_index_mdA | Regenerate the root Writes atomically (temp file + rename) so an interrupted run never leaves a truncated index. |
| kb_health_checkA | Audit the knowledge base for common problems. Reports: files still in |
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
Most tools target a clearly distinct operation (search, read, move, rename, status, health check). Minor overlap exists between kb_move_file and kb_rename_file (move also renames), and the three 'index' concepts (kb_reindex, kb_update_index_md, kb_status) could be momentarily confused, but descriptions draw the boundaries well.
All tools share a consistent kb_ prefix with mostly verb_noun snake_case names (kb_search, kb_read_document, kb_create_directory, kb_move_file). A couple of names are noun-only (kb_status, kb_log) but they remain readable and predictable.
Twelve tools is well within the healthy range and each earns its place: search, read, browse, organize, index maintenance, and auditing. Nothing feels padded or redundant at the set level.
The lifecycle is covered for browsing, reading, moving, renaming, and index upkeep, plus a health audit. However there is no delete/archive operation and no way to create or write a document/file (only directories), which are noticeable gaps for a file-organizing knowledge base workflow.