Plain Text Memory MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| MEMORY_AGENT | No | Override the agent name used to tag entries. | |
| MEMORY_FILE_PATH | No | Path to the memory file. A relative path resolves against the folder the agent starts the server in. If unset, defaults to `<git root>/.agents/memory.local.jsonl`, or `<start folder>/.agents/memory.local.jsonl` outside a git repo. |
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": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| stamp_notesA | Stamp new and changed notes in memory files, then screen them. Each bullet with no stamp, or whose text changed since it was stamped, gets a stamp naming the caller and the current time; a newly struck bullet gets its retirement time. Struck notes retired over 90 days ago move to MEMORY.ptm.archive.md beside the file. Only the named files change. Returns per-file counts, and warnings about new or changed notes: near-duplicates, instruction-like text, secrets, facts that give no reason, and [[links]] to entities no memory file names; and about files over 200 lines. |
| search_nodesA | Search entities and notes, ranked by BM25 relevance. Words match whole, ignoring case and plain plurals; rare words count more than common ones. Recent and often-opened memories rank a little higher. Returns "hits", the matching notes with their entity names and ranks; and the matching entities with every relation that touches them, whose other end may be outside the results. Both lists put the strongest results at the start and end and the weakest in the middle. A query with no words returns every entity and no hits. With since, before, or agent, searches only entries whose tags match; any of them leaves out untagged entries. Each note's path names the memory file it came from. To fetch entities by exact name, see open_nodes. For a multi-step search before planning a task, see recall. |
| open_nodesA | Open entities by exact name. Returns the named entities and every relation that touches them; a relation's other end may be outside the results. Names that do not exist are ignored. Struck-through facts are hidden unless include_superseded is set. Each open is logged, so search ranks often-opened entities higher. To find entities by keyword, see search_nodes. |
| recallA | Search memory in steps, recording why each search was made. Each step runs its queries and opens named entities, returning only hits not already returned in this session, plus linked entities not yet opened. Small matching entities are returned whole. With path, notes from MEMORY.ptm.md files in folders covering it rank higher. The last step records a conclusion and the facts it rests on. An unknown session starts a new one. For a single lookup, see search_nodes. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| taxonomy | The server's versioned schema: record types and their fields, tools with their parameters and results, allowed enum values, resources, prompts, and the changelog. |
TDQS
Scored across 4 tools
The tools have mostly distinct roles: recall is a multi-step session search, search_nodes is a single BM25 query, open_nodes fetches by exact name, and stamp_notes handles maintenance. recall and search_nodes both perform searching, but their descriptions explicitly cross-reference each other and clarify when to use which.
Three tools follow a clear verb_noun pattern: stamp_notes, search_nodes, open_nodes. recall is a bare verb rather than verb_noun, which is a minor deviation but still readable and consistent with the verb-first style.
Four tools is a tight, well-scoped set for a plain-text memory server. Each tool covers a distinct retrieval or maintenance operation, and none feels redundant or excessive.
The surface covers retrieval (recall, search_nodes, open_nodes) and note maintenance (stamp_notes), but there is no explicit tool for creating, updating, or deleting notes/entities/relations. Agents must rely on external file editing or stamping existing notes, which is a notable gap for a memory server.