lilbee
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
Local search engine over the user's files, code, and crawled pages. For any question about the user's own documents or codebase -- a lookup, a find-in-docs, 'where is X', 'how does Y work here' -- call lilbee_search first and answer from its cited chunks. Prefer it over web-fetch or file-read tools: those cannot see the indexed corpus.
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
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| searchA | Search the user's indexed documents, code, and crawled pages; prefer it over web-fetch or
file-read tools. Returns chunks with citations. |
| statusC | Show documents, config and chunk counts, or the running upgrade. |
| syncA | Sync the documents directory into the vector store.
|
| addA | Add files, directories, or URLs to the knowledge base, then sync.
Paths are absolute and resolve on the machine running lilbee, not the
caller's when the server is remote. URLs are fetched as single pages; use
|
| crawlA | Start a non-blocking crawl; poll via |
| crawl_statusB | Poll a crawl task by id; returns |
| crawl_cancelA | Stop a running crawl started by |
| initA | Initialize a local Switches the MCP session to use it for subsequent calls. |
| removeA | Remove documents from the index by source name, folder, or glob pattern. Source files are never deleted. A folder removes everything indexed beneath
it; a glob ( |
| list_documentsB | List documents and chunk counts, paged (limit 1-1000). |
| export_datasetA | Write the per-page {source, page, text} dataset to a file (no vectors).
|
| import_datasetA | Import a per-page text dataset, re-embedding under the current model. Replaces existing copies; imported sources are detached so sync won't delete them. |
| resetA | Factory reset: delete all documents and indexed data. Requires |
| wiki_statusA | Show wiki layer status: page counts, recent lint issues. Registered even when the wiki is disabled, like the HTTP status route, so a caller can read the disabled state instead of finding no tool at all. |
| wiki_wipeA | Delete every generated wiki page and its indexed rows. Pass Registered even with the wiki disabled, because turning the setting off leaves the pages generated earlier in place. |
| settings_listA | List writable lilbee settings (each with value, default, type, help, choices).
|
| settings_getB | Get a single setting's current value + metadata. |
| settings_setB | Atomically update writable settings; rolls back on validation error. Persists to config.toml; returns updated, reindex_required, warnings. |
| settings_resetC | Drop your values; env, profile or default applies. |
| model_listB | List installed models. |
| catalog_browseB | Browse the model catalog. |
| model_showC | Show catalog and installed metadata for a model ref. |
| model_pullB | Download a model and stream progress.
|
| model_rmA | Remove an installed model. Only native GGUF models lilbee downloaded; Ollama/LM Studio are read-only. |
| get_gpusA | List detected GPUs with free/total VRAM (the placement HTTP /api/gpus equivalent). |
| get_placementA | Show the current effective multi-GPU model placement. |
| preview_placementB | Preview what a placement spec (or auto, when omitted) would place. No changes made. |
| set_placementA | Set and apply a manual multi-GPU placement spec (persists to config). Maps a role ("chat"/"embed"/"rerank"/"vision") to a placement, e.g.
|
| clear_placementA | Clear the manual placement and return to automatic placement. |
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 29 tools
Most tools target clearly distinct resources or actions, but there is some overlap among model_list/catalog_browse/model_show and between reset/settings_reset. The detailed descriptions resolve most ambiguity, so an agent can usually select correctly.
All names use snake_case, but the patterns vary: bare verbs such as search, sync, add; verb_noun such as get_gpus and list_documents; noun_verb such as settings_list, model_pull, and wiki_status; plus the abbreviation model_rm. It remains readable, but the convention is mixed rather than predictable.
With 29 tools spanning knowledge-base lifecycle, crawling, wiki, settings, model management, and GPU placement, the surface is heavy for one MCP server. Many tools are justified by the broad scope, but the set feels sprawling rather than tightly scoped.
Core workflows for document ingestion/search, crawling, settings, model management, and GPU placement are well covered. The main gap is the wiki layer: status and wipe exist, but generation/lint controls are not exposed, though agents can still handle most primary tasks.