memory
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| MEMORY_SERVICE_URL | No | URL of the cross-agent-memory HTTP service used by the MCP server. | http://127.0.0.1:5370 |
| MEMORY_SERVICE_TOKEN | No | Bearer token for the memory service, required only if the service was started with MEMSVC_TOKEN set. |
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 |
|---|---|
| memory_searchA | Search the shared memory across ALL agent tools (session logs of this and other AI coding tools, project docs, decisions, notes). Use it whenever you need past context: previous decisions, how a problem was solved before, architecture rationale, user preferences. Returns the most relevant text snippets with their source and relevance score. |
| memory_writeA | Store an item into shared memory so future sessions (in this tool or any other connected AI tool) can find it. Use it for durable facts: decisions made, discoveries, important insights, user preferences. |
| memory_statsA | Get memory-service statistics: which collections exist and how many chunks each holds. Useful to see what has been indexed. |
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 3 tools
Each tool maps to a distinct memory operation: inspection (stats), retrieval (search), and storage (write). There is no plausible way to confuse them, and the descriptions reinforce the boundary between reading and writing.
All three names follow the identical memory_<verb> pattern (memory_stats, memory_search, memory_write), with short, predictable verbs. Naming is fully consistent and self-documenting.
Three tools is a tight, well-scoped surface for a memory service where each tool clearly earns its place. It sits at the thin edge of the ideal range, though the narrow scope justifies it.
Read (search), write, and introspection (stats) are covered, but there is no way to delete, correct, or update a stored memory, and stats gives only counts rather than per-collection detail. Agents that wrote a wrong or stale fact have no lifecycle operation to fix it, which is a notable gap for a shared memory store.