MCP 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_contentsB | Read the contents of a document and return it as a string. |
| edit_documentC | Edit a document by replacing a string in document's content with new string. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| format_document | Rewrites the content of the document in markdown format. |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| list_docs |
TDQS
Scored across 2 tools
read_doc_contents and edit_document target clearly different operations: reading content versus replacing content. There is no practical overlap or ambiguity between them.
Both names use snake_case with a verb_noun structure, which is mostly predictable. However, 'read_doc_contents' uses abbreviated 'doc' while 'edit_document' uses the full word 'document', a minor inconsistency.
Two tools is thin for document manipulation, especially under a server named MCP Chat. The set is minimal but not obviously excessive or mismatched. It feels borderline under-scoped rather than clearly appropriate.
The surface covers reading and string-replacement editing, but lacks create, delete, append, list, or metadata operations. These are notable gaps for a document lifecycle, though basic read/edit workflows are possible.