document-manager-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| DOCS_PROJECT_NAME | No | Short label for this project, used to differentiate multiple Document Manager MCP instances in the client. | |
| DOCS_PROJECT_ROOT | No | Absolute or relative path to the project root containing the docs/ directory. Defaults to current working directory if not set. | |
| DOCS_EMBEDDING_MODEL | No | Optional Hugging Face model ID for feature extraction, e.g., 'Xenova/all-mpnet-base-v2'. | |
| DOCS_EMBEDDING_PROVIDER | No | Set to 'local' to enable semantic search using Transformers.js. |
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": true
} |
| resources | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_docsA | List documentation files. Optionally filter by doc type (feature-specs, jtbd, user-stories, api). |
| read_docA | Read the content of a documentation file by type and slug (filename without path). |
| write_docA | Write or overwrite a documentation file. Content must be markdown. Creates parent folder if needed. |
| create_docB | Create a new documentation file with optional initial content. Use docType to choose category. |
| delete_docA | Delete a documentation file by type and slug. |
| search_docsA | Search documentation by text. Use semantic search (by meaning) when local embeddings are enabled (DOCS_EMBEDDING_PROVIDER=local), otherwise keyword (case-insensitive) search. |
| product_vision_and_strategyA | View the product vision and strategy document. Creates the file with a default template (docs/product-vision-and-strategy.md) if it does not exist. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| product-vision-and-strategy |
TDQS
Scored across 7 tools
Most tools are distinct (list, read, delete, search), but write_doc and create_doc both can create files, and product_vision_and_strategy overlaps with read/create for a specific doc. The descriptions help differentiate, but an agent might misselect for creation tasks.
The verb_noun pattern (list_docs, read_doc, write_doc, create_doc, delete_doc, search_docs) is consistent, though singular/plural varies. product_vision_and_strategy breaks the pattern as a noun phrase.
Seven tools is appropriate for a document manager, covering core operations without bloat.
The set provides full CRUD (create via create_doc/write_doc, read, update via write_doc, delete), plus list and search. No obvious gaps for the domain.