MemoryPlugin MCP Server
OfficialClick on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@MemoryPlugin MCP Server Search my memories for anything about the Johnson project"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
MemoryPlugin MCP Server
An MCP (Model Context Protocol) server for MemoryPlugin, enabling AI assistants like Claude to store and retrieve your memories. This server provides a bridge between AI assistants and your MemoryPlugin account, allowing them to:
Store new memories and organize them into buckets
Search your memories with hybrid semantic + keyword search
Browse Smart Memory categories and their summaries
Edit memories or move them between buckets
Recall your imported chat history from ChatGPT, Claude, and other AI tools
Read or summarize a specific past conversation
Fetch the full transcript of a past conversation as structured JSON for deeper analysis
Search documents you uploaded to MemoryPlugin
Setup
Getting Your API Token
Find your API token in the dashboard
Copy the token for use in configuration
Claude Desktop Configuration
Configure the server in your Claude Desktop configuration file:
Option 1: Using npx (recommended, but currently experiencing issues)
{
"mcpServers": {
"memoryplugin": {
"command": "npx",
"args": ["-y", "@memoryplugin/mcp-server"],
"env": {
"MEMORY_PLUGIN_TOKEN": "your-token-here"
}
}
}
}Option 2: Using global installation (current workaround)
First, install the package globally:
npm install -g @memoryplugin/mcp-serverThen find your Node.js installation path:
which node
# Example output: /Users/username/.nvm/versions/node/v21.7.3/bin/nodeAnd find the installed package path:
npm root -g
# Look for something like: /Users/username/.nvm/versions/node/v22.14.0/lib/node_modulesAdd @memoryplugin/mcp-server/dist/index.js to the end of the path you received in the previous step.
So the final path should look like:
/Users/username/.nvm/versions/node/v22.14.0/lib/node_modules/@memoryplugin/mcp-server/dist/index.jsUse these paths in your configuration:
{
"mcpServers": {
"memoryplugin": {
"command": "/Users/username/.nvm/versions/node/v21.7.3/bin/node",
"args": [
"/Users/username/.nvm/versions/node/v21.7.3/lib/node_modules/@memoryplugin/mcp-server/dist/index.js"
],
"env": {
"MEMORY_PLUGIN_TOKEN": "your-token-here"
}
}
}
}If you experience any startup issues with Option 2, please use Option 1 with global installation instead.
Related MCP server: Simple Memory MCP
Available Tools
The MCP server exposes these tools to AI assistants:
Memories
store_memory— save a new memory, optionally into a specific bucketsearch_memories— hybrid semantic + keyword search over your saved memoriesget_memories_and_buckets— fetch recent or all memories (optionally by bucket) along with your bucket listlist_buckets— view all memory buckets with memory countscreate_bucket— create a new bucket to organize memories by topiclist_bucket_categories— list Smart Memory categories inside a bucket, each with a summarylist_category_memories— load the full memories of one Smart Memory categoryupdate_or_move_memories— edit a memory's text, or move one or many memories to another bucket
Chat history
recall_chat_history— search your imported past conversations across AI tools; supports parallel queries, token budgets, date bounds, and a quality modeget_conversation_summary— AI-generated summary of one past conversation (needs 5,000+ tokens; for shorter chats useget_full_conversation)get_full_conversation— the complete transcript of one past conversationexport_conversation— a temporary download URL (expires in 15 minutes, no auth needed) the assistant fetches to get one past conversation as a structured JSON file, for transcripts too long to read inline or destined for file-based processing
Files
search_uploaded_files— search documents you uploaded to your MemoryPlugin file buckets
Example Usage
Here are some example prompts you can use with Claude once the server is configured:
Could you store this as a memory: "Had coffee with Sarah at Blue Bottle, discussed upcoming project deadlines"
Can you show me my latest 5 memories?
Could you create a new bucket called "Work Meetings"?
Search my memories for anything related to "coffee meetings"
Show me the categories in my main bucket
What did we decide about the pricing page? Check my past conversations.
Go through my whole conversation about the pricing redesign and pull out every action itemSupport
For any issues or questions, please contact support@memoryplugin.com
License
MIT. See LICENSE.
Available Tools
13 toolscreate_bucketA
Create a new bucket to organize memories. Buckets are folders like 'Work', 'Personal', 'Health'. Ask the user for a name if not specified.
Inputs: name (required).
export_conversationA
Download the complete transcript of a past conversation as a machine-readable JSON file. Returns a temporary download URL (expires in 15 minutes, no auth needed) that you fetch yourself to get the full conversation as structured messages (role, content, timestamp).
Use when a transcript is too long to read inline, or when you need it as a file for analysis or scripting. To read a short transcript directly, use get_full_conversation instead. Requires the conversationId from recall_chat_history's sources array.
Inputs: conversationId (required).
get_conversation_summaryA
Get details of a specific past conversation. For short conversations (<5K tokens), returns the full transcript. For longer conversations, returns an AI-generated summary. Use when the user wants to dive deeper into a conversation returned by recall_chat_history. Requires the conversationId from that tool's sources array.
Inputs: conversationId (required).
get_full_conversationA
Get the complete transcript of a specific past conversation. Returns all messages in the conversation without summarization. Use when you need the raw conversation content. Requires the conversationId from recall_chat_history's sources array.
Inputs: conversationId (required).
get_memories_and_bucketsA
Retrieve 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.
Inputs: all, count, query, latest, +1 more.
list_bucket_categoriesA
List 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 memories via list_category_memories.
Inputs: bucketId (required).
list_bucketsA
List the user's memory buckets. Buckets are organizational folders for memories (e.g., 'Work', 'Personal', 'Health').
Inputs: no named parameters.
list_category_memoriesA
Get all memories within a specific Smart Memory category. Use when a category's summary (from list_bucket_categories) indicates it's relevant to the current conversation. The categoryId persists across conversations.
Inputs: bucketId (required), categoryId (required), limit.
recall_chat_historyA
Search and synthesize context from the user's past AI conversations. MemoryPlugin's Chat History feature syncs conversations from ChatGPT, Claude, and other platforms, making them searchable.
Also known as the 'MemoryPlugin inject tool' or 'memoryplugin chat history tool'.
WHEN TO USE: When the user asks about their past decisions, patterns, preferences, relationships, projects, or anything where their conversation history provides valuable personal context. Consider proactively suggesting this when the user's question could benefit from their history.
HOW TO USE:
For simple lookups: a single query is fine
For complex/multifaceted topics: use parallel queries (via 'queries' array) approaching from different angles - timeline, emotions, people, decisions, outcomes, etc.
Set maxTokens per query (300-1000) to control how much context is returned. More tokens = richer detail but consumes more conversation window.
If unclear how much context to fetch, ask the user.
Use 'before'/'after' (ISO 8601 dates like "2025-01-15" or "2025-01-15T10:30:00Z") to constrain results to a date range. Bare dates are interpreted in UTC and are inclusive on both ends.
Use 'mode: "quality"' for slower but more thorough recall on hard or ambiguous queries; defaults to 'speed'.
Returns synthesized summaries (not raw conversation logs) with source metadata for citations.
Inputs: mode, after, query, before, +5 more.
search_memoriesA
Search the user's saved memories using hybrid semantic + keyword search. Returns matching memories ranked by relevance.
Results may include image memories with a temporary image_url that can be fetched to view the image. Image URLs expire after a few hours.
MemoryPlugin stores memories the user wants to persist across AI conversations. Use when looking for specific saved information.
Inputs: query (required), limit, bucketId.
search_uploaded_filesA
Search documents the user has uploaded to their MemoryPlugin document library (not files uploaded directly to this conversation). MemoryPlugin file buckets store documents persistently across all AI chats.
Returns relevant text passages with source file and page info.
Use when:
User explicitly mentions their MemoryPlugin documents
User asks about "my files" or "my documents" and there are no files in the current conversation
If unsure whether they mean MemoryPlugin files or conversation files, ask to clarify
Inputs: query (required), topK, bucketId.
store_memoryA
Save 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').
Inputs: text (required), bucketId.
update_or_move_memoriesA
Edit a single memory's text or bucket, or move multiple memories to a different bucket.
WHEN TO USE: When the user wants to correct, update, or reorganize their saved memories.
Single memory: provide memoryId with optional text and/or bucketId/bucketName. Bulk move: provide memoryIds array with bucketId or bucketName.
Bucket can be specified by ID (number) or name (string). If a name is given and no bucket exists with that name, one is created automatically.
Inputs: text, bucketId, memoryId, memoryIds, +1 more.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
TDQS
Scored across 13 tools
Most tools are clearly distinct, but there is some overlap between list_buckets and get_memories_and_buckets (both return buckets), and between get_full_conversation and get_conversation_summary (both retrieve conversation content). Otherwise, search, store, list, and update operations are well separated.
Naming follows a mostly consistent verb_noun pattern (e.g., search_memories, list_buckets, create_bucket). Minor deviations include 'recall_chat_history' instead of 'search_chat_history', 'store_memory' instead of 'save_memory', and the compound 'update_or_move_memories'.
13 tools is well-scoped for a memory plugin covering memories, buckets, categories, chat history, and file search. Each tool has a clear role, and the count feels appropriate without being excessive.
The tool set covers create, read, and update operations for memories and buckets, but lacks delete operations for memories or buckets. It also lacks an explicit upload tool for files, though search functionality exists. These gaps could hamper full lifecycle management.
Maintenance
Related MCP Connectors
Persistent cloud memory for AI agents. Store and search key-value memories across sessions.
Persistent memory for AI assistants: store, search, and connect knowledge across conversations.
Persistent personal memory for AI assistants — save, search, and recall across every MCP client.
Persistent memory for AI agents. Search, store, and recall across sessions.
Related MCP Servers
- AlicenseAqualityNot gradedmaintenanceEnables AI applications to add, search, update, and delete long-term memories using the Mem0 Memory API, allowing agents to persistently remember user preferences, conversation history, and contextual information across sessions.9Apache 2.0
- AlicenseNot gradedqualityDmaintenanceEnables AI assistants to store and retrieve persistent memories with a web management interface. Supports creating, searching, and managing memories through natural language commands or a visual web dashboard.1MIT

JauMemory MCP Serverofficial
AlicenseAqualityDmaintenanceProvides persistent memory capabilities for AI assistants, enabling storage, recall, and analysis of information across conversations with intelligent memory management.2537 npmMIT- AlicenseBqualityDmaintenanceProvides persistent memory for AI assistants, enabling storage, recall, and analysis of information across conversations with intelligent memory management.5037 npmMIT