mcp_server_document_manager
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| ANTHROPIC_API_KEY | Yes | Your Anthropic API secret key |
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": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| read_docB | Read the contents of a document by its ID |
| edit_docB | Edit the document by replacing a string in the document content with a new string |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| format | Rewrite the content of the document in Markdown format |
| summarize | Summarize the document content |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| list_docs |
TDQS
Scored across 2 tools
Read and edit are fundamentally distinct operations with no overlap. An agent can easily determine which tool to use based on whether it needs to view or modify a document.
Both tools follow the same verb_noun pattern: read_doc and edit_doc. The naming is perfectly consistent and predictable.
With only 2 tools, the set feels thin for a 'document manager,' but it is not extreme. The count is borderline and could be acceptable only if the server is intentionally scoped to just read and edit operations.
The tool surface lacks obvious document management operations such as create, delete, list, or search. Agents would hit dead ends if they need to add or remove documents, making the server significantly incomplete for its stated domain.