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_contentsA | Read the contents of a document and return it as a string. |
| edit_documentA | Edit a document by replacing a string in the documents content with a new string |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| list_docs |
TDQS
Scored across 2 tools
The two tools are clearly distinct: one reads document contents, the other edits by string replacement. No ambiguity in purpose.
Both tools follow a consistent verb_noun pattern: read_doc_contents and edit_document. The naming style is uniform.
With only two tools, the server feels extremely thin for any meaningful functionality, especially given the 'Chat' name suggests broader capabilities. The surface is too limited.
The toolset covers only read and edit operations, missing essential CRUD operations like create, delete, or list. This creates significant gaps for document management workflows.