Engram
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
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
| logging | {} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| extensions | {
"io.modelcontextprotocol/ui": {}
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| rememberC | Stage a durable fact about the user into memory (pending review). |
| recallA | Return the user's promoted memories, most relevant first. Pass a query to filter. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| memory_recall | Compact memory context for the current user, for clients to auto-load. |
TDQS
Scored across 2 tools
The two tools have clearly distinct purposes: one retrieves memories, the other stores them. No overlap in functionality.
Both tool names are single verbs in imperative form, consistent and predictable.
With only 2 tools, the server feels minimal but still covers basic operations for a simple memory service. More tools could be expected for a fuller feature set.
Missing essential operations like updating, deleting memories, listing all memories, and reviewing pending items. The surface has significant gaps for a memory management server.