docs-navigation-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| DOCNAV_REPOSITORIES | No | One or more documentation repository paths, separated by ':' on Linux/macOS. Defaults to ~/.docs-navigation-mcp/repository. | ~/.docs-navigation-mcp/repository |
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
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_sourcesA | List available documentation sources across configured local repositories. |
| list_childrenA | List immediate child nodes under a source root or documentation node. |
| fetch_docsC | Fetch raw documentation content for one or more exact node IDs. |
| create_sourceC | Create an empty documentation source in the primary configured repository. |
| add_nodesA | Add one or more documentation nodes to an existing source. |
| update_nodesB | Update content, metadata, or hierarchy parents for existing nodes. |
| remove_nodesB | Remove nodes. Recursive removal preserves descendants that still have another parent. |
| remove_sourceA | Remove a documentation source and all of its stored nodes. |
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 8 tools
Each tool targets a distinct resource (sources vs nodes) with a clear action (list, fetch, create, add, update, remove). No overlapping purposes; an agent can reliably select the right tool.
All tool names follow a consistent verb_noun pattern (list_sources, add_nodes, remove_source, etc.). The convention is uniform and predictable.
8 tools is well within the ideal range for a docs navigation server. Each tool serves a distinct purpose and the set is neither sparse nor bloated.
The surface covers source and node lifecycle (create, list, fetch, add, update, remove). Minor gap: no explicit source metadata update, but remove_source covers deletion and list_sources provides enumeration. Overall, core workflows are supported.