MCP Documentation Service
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| path | Yes | The absolute path to the documentation directory that the service will manage. | |
| MCP_NPX_WRAPPER | No | An environment variable used to indicate if the service is running within an npx wrapper context. |
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
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| read_documentA | Read a markdown document from the docs directory. Returns the document content including frontmatter. Use this tool when you need to examine the contents of a single document. |
| write_documentA | Create a new markdown document or completely overwrite an existing document with new content. Use with caution as it will overwrite existing documents without warning. Can create parent directories if they don't exist. |
| edit_documentA | Make line-based edits to a markdown document. Each edit replaces exact line sequences with new content. Returns a git-style diff showing the changes made. |
| list_documentsC | List all markdown documents in the docs directory or a subdirectory. Returns the relative paths to all documents. |
| search_documentsC | Search for markdown documents containing specific text in their content or frontmatter. Returns the relative paths to matching documents. |
| generate_documentation_navigationC | Generate a navigation structure from the markdown documents in the docs directory. Returns a JSON structure that can be used for navigation menus. |
| check_documentation_healthC | Check the health of the documentation by analyzing frontmatter, links, and navigation. Returns a report with issues and a health score. |
| create_folderC | Create a new folder in the docs directory. Optionally creates a README.md file in the new folder with basic frontmatter. |
| move_documentC | Move a document from one location to another. Optionally updates references to the document in other files. |
| rename_documentA | Rename a document while preserving its location and content. Optionally updates references to the document in other files. |
| update_navigation_orderC | Update the navigation order of a document by modifying its frontmatter. |
| create_documentation_sectionC | Create a new navigation section with an index.md file. |
| validate_documentation_linksC | Check for broken internal links in documentation files. |
| validate_documentation_metadataC | Ensure all documents have required metadata fields. |
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 14 tools
Each tool has a distinct purpose with clear boundaries: health checking, creation, editing, listing, moving, reading, renaming, searching, updating navigation, and validation. No tools appear to overlap in functionality, making it easy for an agent to select the correct one.
All tools follow a consistent verb_noun naming pattern (e.g., check_documentation_health, create_documentation_section, edit_document). This uniformity enhances readability and predictability for agents.
With 14 tools, the server is well-scoped for documentation management, covering a comprehensive range of operations from CRUD to validation and navigation. Each tool serves a specific, necessary function without redundancy.
The tool set provides complete coverage for documentation lifecycle management, including creation, reading, updating, deletion (via move/rename/overwrite), validation, and navigation. There are no obvious gaps that would hinder agent workflows.