Knowledge Management
Mem0 MCP connector
Connecting Mem0 to Claude, ChatGPT, Cursor, or any MCP client through Elaichi lets each person search, add, correct, and export the memories, users, and projects in Mem0 inside their own access, with every call logged.
-
How it connects. Connects with an API key. The credential goes into a vault nobody reads back.
-
One address. https://api.elaichi.ai/mcp, the same for every user.
-
Their own access. An agent never gets more than the person it acts for.
How to connect
How to connect Mem0 to Claude, ChatGPT or Cursor
Two steps, about a minute.
In Elaichi
Connect Mem0 once
-
Open Connections, choose Add connection, and pick Mem0.
-
Optionally set Share with to give a team access, then press Connect.
-
Paste a Mem0 API key. One person generates a token in Mem0 and pastes it once. Everyone else works through Share with, and never sees it.
The credential is vaulted. Nobody reads it back, not even the AI.
Add connection
Choose a connector.
In your AI client
Point it at one endpoint
Everyone in the organization uses the same address, and each person only ever reaches what their own account allows.
Connect Mem0 to Claude
-
1
Open Customize, then Connectors.
-
2
Press Add.
-
3
Name it, paste the MCP server URL, then Continue.
https://api.elaichi.ai/mcp -
4
Sign in and approve.
On Team and Enterprise, an Owner adds it once. Everyone else turns it on for themselves.
Connect Mem0 to ChatGPT
-
1
Open Plugins, then press the + button.
-
2
Name it and paste the endpoint into Server URL.
https://api.elaichi.ai/mcp -
3
Leave Authentication on OAuth, then tick the risk acknowledgement.
-
4
Press Create, then sign in and approve.
Works on the web today. The plugin directory lives at chatgpt.com/plugins.
Connect Mem0 to Cursor
-
1
Open
~/.cursor/mcp.json. -
2
Add the endpoint under
mcpServers.https://api.elaichi.ai/mcp -
3
Reload Cursor, then sign in and approve.
~/.cursor/mcp.json
{
"mcpServers": {
"elaichi": {
"url": "https://api.elaichi.ai/mcp"
}
}
}
Set up per machine, so repeat it on each computer you work from.
Connect Mem0 to any MCP client
-
1
Add the endpoint as a remote MCP server.
https://api.elaichi.ai/mcp -
2
Sign in and approve.
{
"mcpServers": {
"elaichi": {
"url": "https://api.elaichi.ai/mcp"
}
}
}
The Elaichi Agent already has these tools, with nothing to set up.
Use cases
What teams do with Mem0 through Elaichi
Every one of these runs inside the access the person already has, and lands in the same audit log.
-
Product
Check what the assistant remembers about a user
After a customer says the assistant got them wrong, search that user's memories in Mem0 to see exactly what has been retained and where it drifted.
-
Support
Correct a bad memory after a ticket
Find the memory in Mem0 that caused a customer to get a wrong answer, fix the wording or remove it, and confirm the change landed before closing the ticket.
-
Engineering
Set up a project for a new pilot
Create a Mem0 project for the pilot and add the teammates who need to be organization members, without leaving the chat.
-
Compliance
Clear a departed customer's memories
When a deletion request arrives, remove every memory in Mem0 tied to that user with a single filter, and keep the event record for the audit file.
-
Operations
Pull an export for the quarterly review
Start an export of memories in Mem0 and fetch it once it is ready, so the review pack is built from what the assistant actually stored.
-
Analytics
Review this week's memory activity
List recent events in Mem0 to see how many memories were created, updated, or deleted, and log feedback on the recalls that missed.
Try asking
- “Search Mem0 memories mentioning the pricing migration”
- “List Mem0 users with memories created this week”
- “Summarize Mem0 events logged for the onboarding entity”
AI tools
Mem0 tools for your AI agents
37 tools are ready to call through Elaichi's MCP endpoint the moment you connect Mem0, governed by the same roles, restrictions, and audit log as everything else in Elaichi.
No tools match your search.
See it in Elaichi
What connecting Mem0 gets you
6 screens from the product, each doing one job for your Mem0 account.
The agent
Ask in plain language, read live memories.
Type a question and get answers drawn from Mem0 memories, users and events.
- memories
- users
- events
- entities
Ask Elaichi to work across your apps.
Search Mem0 memories mentioning the pricing migration
List Mem0 users with memories created this week
Summarize Mem0 events logged for the onboarding entity
Also runs in Claude, ChatGPT or Cursor
MCP clients
One Mem0 endpoint for every MCP client.
Claude, ChatGPT and Cursor connect over OAuth, no SDK and no shared key.
Copy the endpoint
Tool catalog
37 Mem0 tools ready without custom code.
Memories, users, events, entities and exports, each with its own methods.
- Delete a Mem0 entity by ID
- List all Mem0 users
- Get single Mem0 event by ID
- List all Mem0 events
Toolboxes
Every team gets its own Mem0 toolbox.
Curate one toolbox per team so each sees only the Mem0 tools it needs.
- Support
- Sales
- Product
- Research
Shared connections
Teammates use Mem0 without seeing a credential.
Each connection shows who connected it and which teams and members share it.
- Support EMEA
- Sales
- Product
- Research
Audit log
Answer who touched which memory, and when.
Every Mem0 call lands in an append-only log with actor, action and resource.
- When
- Who
- What happened
- Type
Launching soon
From answering questions to doing the work
A person no longer has to ask. A trigger starts the work, inside the same permissions and the same audit log as everything else. Automations and live dashboards are launching soon, on the Black plan.
Automations
A schedule fires, a digest posts to Mem0.
Six steps fetch memories, group them, draft a digest, wait for approval, post back.
Mem0 digest
Run 418 · started 2 minutes ago · on behalf of Emma Laurent
-
✓
Schedule
Every weekday at 08:00
0.2s -
✓
Fetch memories
Mem0
1.4s -
✓
Group by owner
Transform
0.1s -
✓
Draft the digest
Agent step
Ran with 4 tools, returned a structured summary
6.2s -
Approve the digest
Needs approval
Assigned to Michael Brennan
Approve Deny -
Post the digest
Mem0
Queued
Collections and dashboards
Mem0 memory health, counted on a schedule.
Four metrics, 14 days of memories created and a per team breakdown, no model involved.
Mem0 health
Refreshed 4 minutes ago · every 15 minutes · from the memories collection
Memories
1,284 ↓ 12%
Users
96 ↓ 8%
Needs attention
3 ↑ 2
Updated this week
412 ↑ 9%
Memories created
Last 14 days
By team
Share of activity
Support EMEA 34%
Sales 27%
Product 21%
Research 18%
FAQ
Frequently asked questions
How do I connect Mem0 to Claude?
Two steps. In Elaichi, choose Mem0 and paste the API key from your Mem0 dashboard, which is the whole sign-in for this connector, since there is no OAuth application to register and no client ID or secret to generate. Then in Claude open Customize, then Connectors, then Add, and paste https://api.elaichi.ai/mcp. Claude asks you to sign in to Elaichi, and Mem0 is available in your next conversation.
Does Mem0 work with ChatGPT and Cursor as well as Claude?
Yes. Connect Mem0 once in Elaichi and the same endpoint, https://api.elaichi.ai/mcp, works in Claude, ChatGPT, Cursor, any other MCP client, and the Elaichi Agent. Nothing has to be set up again per client, and every one of them runs through the same access rules and the same audit log.
What can an AI agent actually do with my Mem0 data?
With Mem0 connected, an agent can search the memories stored for a user, add a new memory, correct or remove one that is wrong, and clear a whole set of memories with a filter. It can also list users and recent events, start and fetch an export, record feedback on a recall, and create projects and organization members. Because Mem0 has many actions, short concrete asks such as "show the memories for user 4821" work better than long paragraphs.
Does connecting Mem0 give the AI access to every organization and project?
No. Everything an agent does in Mem0 runs under the API key of the person who connected, so it can only reach the organizations, projects, and memories that key already reaches. Elaichi can narrow that further, for example to search and read only, but it can never grant the agent anything the key itself does not have.
Can I stop an agent from deleting or changing memories in Mem0?
Yes. In Elaichi, restrictions on the Mem0 connector work per action, so you can allow searching and reading memories while blocking updates, single deletions, and bulk deletions by filter. A blocked action is never shown to Claude, ChatGPT, Cursor, or any other client, so no prompt, however worded, can reach it.
What happens to a Mem0 connection when someone leaves?
Offboarding that person in Elaichi ends their access to Mem0 at once, across every client they used. If they had shared a Mem0 connection with a team, it keeps working for everyone else and you can hand ownership to someone still in the company. Disconnecting Mem0 once in Elaichi removes it from Claude, ChatGPT, Cursor, and every other client at the same time.
Put Mem0 in front of your team
Fourteen days on Gold, no credit card. Connect it once and pick what each team can call.