MCP Chat CLI
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| ANTHROPIC_API_KEY | Yes | Your Anthropic API 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. |
| summarize | Summarizes the contents of a document. |
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 contents, the other edits by replacing text. There is no functional overlap.
Both tool names follow the verb_noun pattern (edit_document, read_doc_contents), with consistent snake_case and clear action-object structure.
With only two tools, the server feels thin for a document utility, though it could be a minimal implementation. It falls into the borderline category (1-2 tools).
The server lacks basic CRUD operations like create and delete documents. While read and edit are provided, agents cannot create new documents or remove them, which are significant gaps.