server-anthropic
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| ANTHROPIC_API_KEY | Yes | Your Anthropic API key from console.anthropic.com | |
| ANTHROPIC_WORKSPACE_ID | No | Optional workspace ID for usage segmentation |
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 | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_modelsA | List all available Anthropic models and their capabilities. Access requires a valid API key configured through the ANTHROPIC_API_KEY environment variable. |
| send_messageA | Send a message to an Anthropic model using the Messages API. Requires authentication via ANTHROPIC_API_KEY environment variable. Optionally supports workspace segmentation via ANTHROPIC_WORKSPACE_ID. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 2 tools
The two tools have clearly distinct purposes: list_models provides information about available models, while send_message executes a message to a model. There is no overlap or ambiguity.
Both tool names follow a consistent verb_noun pattern with underscores: list_models and send_message. The naming is clear and predictable.
With only 2 tools, the server feels thin for its intended purpose of interacting with the Anthropic API. While the tools are essential, additional tools like streaming or model details would be expected.
The server covers basic operations (list models and send a message) but lacks common features like streaming, message history, or batch operations. Notable gaps exist for a full API surface.