mcp-doc-chat
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_doc_contentA | Reads the content of a document and returns it as a string. |
| edit_doc_contentC | Edits the content of a document based on the provided new content. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| format | Rewrites a contents of the document in markdown format. |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| list_docs |
TDQS
Scored across 2 tools
The two tools have clearly distinct purposes: one reads document content, the other edits it. There is no overlap or ambiguity.
Both tool names follow a consistent verb_noun pattern (read_doc_content, edit_doc_content), making them predictable and easy to understand.
With only two tools, the server is minimal but reasonably scoped for a chat-based document interaction context. It's slightly thin but not inappropriate.
The tools cover reading and editing existing documents, but lack essential operations like creating, deleting, or listing documents. This is a significant gap for a document-focused server.