litedocs-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| db | No | Index file. Default: <docs>/.litedocs-index.sqlite3. Corresponds to the --db CLI flag. | |
| docs | Yes | Folder of documentation to index. Required. Corresponds to the --docs CLI flag. | |
| exts | No | Comma-separated extensions. Default: .md,.markdown,.adoc,.asciidoc,.txt. Corresponds to the --exts CLI flag. |
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 | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| search_docsA | Full-text search over the local documentation knowledge base. Returns the best-matching sections with file path, line range, heading breadcrumb and a snippet. Prefer this over grepping or reading whole files: pass 3-6 distinctive keywords rather than a full sentence. Wrap a phrase in double quotes for an exact match. |
| list_docsA | List every indexed document as path plus title. Use when you need a map of the knowledge base rather than an answer. |
| reindex_docsA | Rescan the docs folder and refresh the index. Run after a git pull; it only reprocesses files whose content changed. |
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 3 tools
Each tool targets a distinct action on the docs index: search retrieves matching sections, list enumerates documents, reindex refreshes the index. Their boundaries are crisp and the descriptions reinforce when to prefer each over grep or file reads.
All three names follow the same verb_noun snake_case pattern (search_docs, list_docs, reindex_docs) with a shared '_docs' noun suffix. Fully predictable and readable.
Three tools is small but well-matched to a focused read-only documentation index; each tool clearly earns its place. It is on the lean side, with no room to trim and one arguably missing retrieval operation.
The surface covers search, listing, and index refresh, but there is no get_document tool to fetch a full document by path from a list_docs result. Agents can only see snippets or paths, creating a dead end when full content is needed.