Memory MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| ANTHROPIC_API_KEY | Yes | Your Anthropic API Key obtained from https://console.anthropic.com/ |
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 |
|---|---|
| recall_memory_toolC | 从项目记忆中回忆相关信息 |
| memorize_memory_toolC | 记住一些内容 |
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 completely distinct purposes: one stores information (memorize) and one retrieves information (recall). There is no overlap in functionality, and an agent would never confuse which tool to use for which operation.
Both tools follow the same verb_noun_tool pattern: memorize_memory_tool and recall_memory_tool. The naming is perfectly consistent with clear action verbs and matching structure throughout.
With only 2 tools, this server feels thin for a memory system. While memorize and recall cover basic operations, there are no tools for managing, organizing, updating, or deleting memories, which would be expected for a complete memory management system.
The tool surface is severely incomplete for a memory system. While it covers basic store and retrieve operations, there are no tools for updating existing memories, deleting memories, listing available memories, searching with filters, or managing memory organization. This creates significant gaps that will limit agent effectiveness.