mcpbeat Sign in

MemoryPlugin MCP Server

by memoryplugin Your server? Claim it
answering

MemoryPlugin is answering right now. Last checked 6 min ago. It exposes 14 tools.

Give every AI you use one shared, permanent memory. Store once, recall in whichever AI you open.

Uptime history 48 days of history · worst day 41%
48 days agonow
48.4%
Uptime 24h
89 of 184 checks
14
Tools
read from the server
306 ms
Response time
average over 24h
open, no key
Access
streamable-http

MemoryPlugin does not always answer

Over the last week it answered 46.2% of our checks. We check every 15 minutes, so you hear about the next outage within the hour — not from your users.

Three servers free · no card

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 6 min ago.

run in your terminal
claude mcp add memory --transport http https://www.memoryplugin.com/api/mcp/mcp
~/Library/Application Support/Claude/claude_desktop_config.json
{
  "mcpServers": {
    "memory": {
      "url": "https://www.memoryplugin.com/api/mcp/mcp"
    }
  }
}
~/.codex/config.toml
[mcp_servers.memory]
url = "https://www.memoryplugin.com/api/mcp/mcp"
.cursor/mcp.json
{
  "mcpServers": {
    "memory": {
      "url": "https://www.memoryplugin.com/api/mcp/mcp"
    }
  }
}
.vscode/mcp.json
{
  "mcpServers": {
    "memory": {
      "url": "https://www.memoryplugin.com/api/mcp/mcp"
    }
  }
}

This server publishes 1 more address. The block above uses the one we reach during checks; the full list is under Endpoints below, and the author may intend a particular one for your client.

Available tools 14

Read directly from the server with tools/list, grouped by what they act on. If a tool disappears, we record the date.

bucket
create_bucket
Create a new bucket to organize memories. Buckets are folders like 'Work', 'Personal', 'Health'. Ask the user for a name if not specified.
list_bucket_categories
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.
memories
get_memories_and_buckets
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.
search_memories
Search the user's saved memories using hybrid semantic + keyword search. Returns matching memories ranked by relevance. MemoryPlugin stores memories the user wants to persist across AI conversations. Use when looking for specific saved information.
buckets
list_buckets
List the user's memory buckets. Buckets are organizational folders for memories (e.g., 'Work', 'Personal', 'Health').
category
list_category_memories
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.
chat
chat_history_overview
Returns an AI-generated overview of the user, built from the chat history they have synced into their MemoryPlugin account. Call it at the start of a conversation to load the user's context. If no overview exists yet, the user can generate one from their MemoryPlugin dashboard.
conversation
get_conversation_summary
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.
export
export_conversation
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.
full
get_full_conversation
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.
move
update_or_move_memories
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.
recall
recall_chat_history
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. - 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'. - If unclear how much context to fetch, ask the user. Returns synthesized summaries (not raw conversation logs) with source metadata for citations.
store
store_memory
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').
uploaded
search_uploaded_files
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

Endpoints

URLTransportStateLatencyChecked
https://www.memoryplugin.com/api/mcp/mcp streamable-http answering 251 ms 6 min ago
https://www.memoryplugin.com/api/mcp/sse sse answering 286 ms 7 min ago

Alternatives to MemoryPlugin

same job, measured the same way
Callosium
by callosium

One shared memory for every AI you use, in plain Markdown files you own.

109 installs/wk local only
Atlaso
by atlaso

AI memory layer — one shared, persistent memory across every AI tool you connect.

answering
Memocore
by memocore

Shared memory for all your AI agents, your whole team and every MCP client — save, search, recall.

answering
Agentage Memory
by agentage

One memory, every AI. A shared, user-owned markdown memory your AI clients read and write over MCP.

answering
One Brain
by prophet-git

Shared memory for a team in Claude Code: what one person records, everyone has.

answering
MemoCat — Shared AI Memory
by montygovernance

One shared, persistent memory across AI agents and systems, with semantic recall and live updates.

1 945 installs/wk local only
CLS++ Memory
by rajamohan1950

Cross-LLM persistent memory: store context once, recall it from any AI model.

122 installs/wk answering
Recall — persistent memory for agents
by workers-notdown-app-recall

Persistent memory for AI agents. Free, no LLM, no SDK. Open Worker you can self-host in 2 commands.

5 tools answering

MemoryPlugin — questions

Answers built from our own checks of this server.

What can MemoryPlugin do?
It exposes 14 tools, read directly from the server on our last check. Among them: chat_history_overview, create_bucket, export_conversation, get_conversation_summary, get_full_conversation, get_memories_and_buckets and 8 more. The full list with descriptions is on this page — we take it from the server itself via tools/list, not from a README. How MCP servers expose tools in the first place →
What is MemoryPlugin mostly used for?
Its tools cluster around memories and bucket. That is what this server is built to work with — the grouping comes from the actual tool names, not from a category we assigned.
Is MemoryPlugin working right now?
We send a real MCP handshake every 15 minutes. Over the last 24 hours 89 of 184 checks got a reply (48.4%), average response time 306 ms. The bar chart above shows every period we have measured.
How do I connect MemoryPlugin?
Copy the ready config from this page — we generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each with the file path that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address.
Does MemoryPlugin need an API key?
No. MemoryPlugin completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 14 of them are readable on this page. This is what we observed, not what the docs claim.
How fast is MemoryPlugin?
It answers our handshake in 306 ms on average, which is faster than 50% of all working MCP servers we measure. The comparison comes from our own checks across the whole registry, every 15 minutes.