Base44
Build and edit Base44 apps from an AI assistant, and query data your app's users submit.
Give your AI agent persistent memory across sessions.
Opens Agent Studio, where connecting is one click. The connector URL below works in any MCP client.
Paste it into any MCP client. Setup docs
The Mem0 MCP server gives Claude, ChatGPT and any MCP-compatible agent a memory that survives the end of a conversation. Its 11 tools save facts about a user, search them semantically, update them and delete them. Sign-in is OAuth or a Mem0 Platform API key. Seven of the 11 tools write, and three of those delete.
Verified connector
Listed by Anthropic as a partner connector in its Connectors Directory.
Connection checked by Agentman on .
Anthropic states this reflects the level of review a connector received, not a security audit.
Tool names from Anthropic's directory listing. This server requires sign-in, so we could not read tool descriptions or parameter schemas.
user_id=* is documented. Each delete filter accepts a wildcard meaning all users, agents or apps in scope.tools/list, so no readOnlyHint or destructiveHint could be checked.permissions label in Anthropic's directory. The read-or-write posture is simply not asserted.https://mcp.mem0.ai/mcp answered our probe with a 307 redirect to /mcp/ before returning the 401; a client that does not follow redirects on POST may report a confusing failure.Everything inside one scope, and the scope is an argument rather than a default. Mem0's docs describe the tool as a bulk delete of all memories in scope, where scope means a `user_id`, `agent_id`, `app_id` or `run_id` filter. The underlying API rejects a call with no filter at all, but each filter separately accepts `*` as a documented wildcard meaning every user, agent or app.
No. Mem0 publishes no soft delete, no trash and no restore path for memories removed through the API, and its delete guide's own verification step is to search again and confirm the memory is gone. If you need a memory to stop surfacing without being destroyed, Mem0 documents `expiration_date` instead, which hides a record from list-shaped reads while leaving it in storage.
Not at the server. The confirmation Mem0 documents lives in the tool descriptions, which tell the model to act on a confirmed scope, so the enforcement is whatever your MCP client does with a write tool. Claude and most clients prompt before a tool call by default, but that is a client behaviour and not a Mem0 platform block. Nothing on the server side refuses an unconfirmed delete.
An entity is one of four scoping identifiers: a user, an agent, an app or a run. Mem0's API reference describes deleting an entity as removing that entity and all its memories, so it is broader than deleting memories alone. These are the partitioning identifiers, not the people and places that Graph Memory extracts, which Mem0's docs call out as a separate concept.
It depends on your plan, and Mem0 states the split plainly. Its privacy policy says inputs, prompts and user-generated content from Free Plan users are used to train its AI models, and that it does not train on the same data from Paid Plan users. Since a memory store holds whatever an assistant chose to remember about someone, that distinction is worth checking before connecting on the free tier.
Yes. Mem0 documents two ways in: the browser OAuth flow most clients trigger on first tool use, and sending a Platform API key as a bearer token for clients without browser sign-in or for headless environments like CI. Both reach the same hosted server. Our own probe saw only the OAuth challenge, since we never authenticated.
Mem0's pricing page publishes a monthly allowance per plan, split between writes and reads. The free Hobby tier lists 10,000 add requests and 1,000 retrieval requests a month, Starter lists 50,000 and 5,000, and Pro lists 500,000 and 50,000. An agent that saves memories automatically consumes the add allowance without anyone deciding to spend it.
mem0ai/mem0-mcp README — https://raw.githubusercontent.com/mem0ai/mem0-mcp/main/README.md (fetched 2026-08-19) · retrieved 2026-08-19www-authenticate Bearer challenge and resource_metadata pointer, 2026-08-19 · retrieved 2026-08-19/mcp path-insert and path-append forms both 404) · retrieved 2026-08-19docs.mem0.ai/robots.txt carries Content-Signal: ai-train=yes, search=yes, ai-input=yes (fetched 2026-08-19) — Mem0 expressly permits AI synthesis of these pages. · retrieved 2026-08-19Connect Mem0 once and your agents call these tools on their own: on a schedule, in a workflow, with nobody at the keyboard.