MemoryPlugin
com.memoryplugin/memory · 1.0.0
Give every AI you use one shared, permanent memory. Store once, recall in whichever AI you open.
Nobody here has read this server's code, because it publishes none. The description above is the maker's own, from the registry. A connection test shows whether it answers and what tools it says it has; it never calls a tool, so it cannot show what one does with your data.
Where it sits in the directory's order
What can be seen from outside, weighed as the directory publishes.
Observable signals: 45 of 100 points (at most 60 here)
| Input | Points | What was seen |
|---|---|---|
| Source published | held at 0 | No entry here publishes source: that is what puts it in this directory. |
| Licence stated | held at 0 | With no files, there is nothing for a licence to be stated in or held against. |
| Advisory state | held at 0 | Advisory databases index packages, and these entries publish none, so there is nothing to look up. |
| Auth declared | 0 of 15 | The registry entry declares no key. That is what it declares, not a finding that it has no protection. |
| Latest connection test reached it | 20 of 20 |
Where it answers
https://www.memoryplugin.com/api/mcp/mcpstreamable-httphttps://www.memoryplugin.com/api/mcp/ssesse
Connection test
The MCP handshake, then a request for the tool list, with no key and no data of yours. Run nightly, and by anyone, at most once every ten minutes per server.
It completed the handshake and listed 14 tools.
- Protocol
- 2025-06-18
- Calls itself
- MemoryPlugin MCP (Authenticated) 0.0.0
- Handshake time
- 101 ms
- HTTP status
- 200
The tools it lists (14, as of 4 days ago)
The tool-description rules found nothing in these descriptions. They look for instructions aimed at a model and for hidden characters; they cannot see what a tool does when it runs.
store_memorySave information to the user's MemoryPlugin account. MemoryPlugin lets users build persistent memory across AI conversations. WHEN TO USE: Proactively save anything that might be useful for future context - preferences, decisions, project details, personal info, insights, or anything the user might want recalled later. Err on the side of saving. Ask the user which bucket to save to if unclear. Buckets are organizational folders (e.g., 'Work', 'Personal', 'Health').
list_bucketsList the user's memory buckets. Buckets are organizational folders for memories (e.g., 'Work', 'Personal', 'Health').
create_bucketCreate a new bucket to organize memories. Buckets are folders like 'Work', 'Personal', 'Health'. Ask the user for a name if not specified.
get_memories_and_bucketsRetrieve the user's saved memories from MemoryPlugin, optionally filtered by bucket. Also returns the list of available buckets. Use to see what the user has previously saved. Consider using at conversation start if the user's query might benefit from their stored context.
list_bucket_categoriesList AI-generated categories within a bucket. When users activate Smart Memory, their memories are automatically organized into topic-based categories. Returns for each category: - name: Category title - summary: Dense overview of core facts, preferences, current projects, key context (~200 words) - additionalInfo: Lists specific topics available in this category and suggests when to load the full memories - memoryCount: Number of memories in category Also returns recentMemories: the 30 most recent memories in the bucket. Use the summary and additionalInfo to decide if/when to load full mem
list_category_memories
How this entry becomes a listing
For the maker. The catalogue lists what it can read, and this server publishes nothing to read yet. There are two routes, and only the first is open today.
Publish the source Open today
- Put the server's source in a public repository on github.com, with a licence.
- Keep a server.json in that repository naming this server,
com.memoryplugin/memory, and declare the repository in it:"repository": { "url": "https://github.com/owner/repo", "source": "github" }, adding"subfolder"when the server lives in a folder. - Publish that version to the official MCP registry.
- The nightly registry sweep records the declaration. This page stays, dated, and says the source is declared but not yet read.
- The catalogue reads declared repositories at a pinned commit, in batches run by hand, and lists the servers that meet the batch's rules (among them a server.json at that commit naming the server, an https endpoint and a licence). When it lists this server, this page links to the listing. There is no schedule, so no date can be promised.
List it through the maker studio Not open yet
From the official MCP registry, last updated there 71 days ago. The registry entry · www.memoryplugin.com