shared-memory
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| MEMORY_FILE | No | Legacy configuration option specifying the path to memories.jsonl, e.g. <dir>/memories.jsonl. Old configs using this keep working. | |
| SHARED_MEMORY_DIR | No | Directory where shared memory and mailbox JSONL files are stored. Multiple windows share memory by pointing this at the same folder. | ~/.shared-memory-mcp |
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_saveA | Save one important fact about the user (preferences, projects, decisions) to the shared memory that all connected Claude windows can read. Use when the user says "remember this" or states something worth keeping. Write it clearly and specifically. |
| memory_searchA | Search the shared memory. Space-separated keywords; matches any by default (match="all" requires every keyword). Empty query returns the most recent entries. Call once at the start of a new conversation. |
| memory_deleteA | Delete one memory by id. Only when the user asks to forget something. |
| msg_sendA | Leave a message for another Claude window (shared mailbox). The recipient sees it only when it calls msg_read; nothing is pushed. "to" is the recipient's name, or "all" for everyone. |
| msg_readA | Read messages addressed to you (and broadcasts). By default only unread ones, which are then marked read; all_history=true lists the whole exchange. Call before starting work and after finishing a chunk. |
| msg_boardA | Browse every message of a category regardless of recipient or read state (does not mark anything read). Use topic "list" to see categories and counts. |
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 6 tools
The three memory_* tools are clearly distinct (save/search/delete on different operations). msg_read and msg_board both read messages and could be confused, but the descriptions draw a clear line: msg_read is personal unread inbox that marks read, msg_board is a category browser that doesn't mark read.
Clean verb_noun snake_case throughout, organized into two predictable prefixes (memory_* and msg_*). No stylistic deviations.
Six tools cleanly cover two small domains (persistent memory and inter-window messaging) with no filler. Well-scoped for the stated purpose.
Core lifecycle is covered: save/search/delete for memory and send/read/browse for messages. Minor gaps exist—no memory update/edit and no way to delete or reply to messages—but agents can work around these.