Claude Server MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
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
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| save_project_contextC | Save project-specific context with relationships |
| save_conversation_contextC | Save conversation context with continuation support |
| get_contextC | Retrieve context by ID and optional project ID |
| list_contextsC | List contexts with filtering options |
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 4 tools
Each tool has a clearly distinct purpose with no overlap: get_context retrieves a specific context, list_contexts lists contexts with filters, save_conversation_context saves conversation-specific context, and save_project_context saves project-specific context. The descriptions clearly differentiate between retrieval, listing, and two types of saving operations.
All tools follow a consistent verb_noun pattern (get_context, list_contexts, save_conversation_context, save_project_context) with clear, descriptive names. The naming convention is uniform throughout the set, making it easy to understand each tool's function at a glance.
With 4 tools, the count is reasonable for a context management server, covering key operations like retrieval, listing, and saving. It feels slightly minimal but well-scoped, as each tool serves a distinct and necessary function without redundancy.
The tool set provides good coverage for context management with get, list, and save operations for both conversation and project contexts. A minor gap exists in update or delete functionality for contexts, but agents can likely work around this by re-saving or managing contexts through the provided tools.