MCP Chat
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| USE_UV | No | 1 to launch the MCP server via uv, 0 for plain python | 1 |
| CLAUDE_MODEL | Yes | Model id to chat with | claude-sonnet-4-5 |
| 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 |
|---|---|
| format | Rewrites the 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 completely distinct purposes: one reads document content, the other edits by replacing text. There is zero overlap or ambiguity between them.
Both tools follow a verb_noun pattern (read_doc_contents, edit_document), but the noun forms differ slightly ('doc_contents' vs 'document'). This minor inconsistency doesn't hinder readability.
With only two tools, the server feels thin for a document manipulation domain. While the narrow focus is defensible, the count is below the typical 3-15 range and borders on insufficient.
The server provides read and edit (replace) operations, but lacks create, delete, list, or other common document lifecycle operations. These gaps could be worked around but represent notable missing functionality.