← All integrations

Mem0 MCP server

16 operations0 webhooks

Long-term memory for AI agents with Mem0 - add, search, list, update and delete memories, read a memory's change history, and poll the events Mem0 queues for asynchronous work.

Use Mem0 in Claude, ChatGPT, Cursor or another MCP client

Connect Mem0 once in Corsair, then add one MCP address to your agent.

Connect Mem0
Setup steps for Claude, ChatGPT, Cursor and Claude Code

Building your own app on the Corsair SDK? Get API keys

Try Mem0 with your agent

Connect Mem0, then paste this into Claude, ChatGPT or Cursor. For ideas from other apps, see the use cases.

Using Corsair, show me what you can do in Mem0 on my account, then run one read-only example and show me the result.

Runs once, when you ask

Mem0 tools and triggers

Tools are what your agent can do in Mem0 through Corsair's MCP server. Triggers are the Mem0 events a routine can start from.

Memories

  • AddWrite

    Extract memories from conversation messages and store them for a user, agent, app or run; processing is queued and returns an event_id to poll

    memories.add

  • Batch DeleteDestructive

    Permanently delete up to 1000 memories in one call

    memories.batchDelete

  • Batch UpdateWrite

    Update up to 1000 memories in one call

    memories.batchUpdate

  • DeleteDestructive

    Permanently delete one memory; delete_linked also removes memories linked to it

    memories.delete

  • Delete AllDestructive

    Delete every memory matching a filter, or every memory for an entity when the filter is "*"; Mem0 queues the deletion and answers immediately

    memories.deleteAll

  • GetRead-only

    Read one memory by its ID

    memories.get

  • HistoryRead-only

    Read the change history of one memory: each ADD, UPDATE and DELETE with its old and new text

    memories.history

  • ListRead-only

    List stored memories page by page, filtered by entity, date range or category; entity IDs go inside `filters`

    memories.list

  • SearchRead-only

    Rank stored memories by relevance to a query with hybrid semantic, keyword and entity matching; entity IDs go inside `filters`

    memories.search

  • UpdateWrite

    Change one memory's text or metadata, or set its expiration date; pass expiration_date as null to clear one

    memories.update

Webhooks

  • CreateWrite

    Register a URL to receive Mem0 events for a project, subscribing it to memory add, update, delete or categorize and the ingest job events

    webhooks.create

  • DeleteDestructive

    Unregister a webhook so Mem0 stops posting events to its URL

    webhooks.delete

Connect Mem0 to Claude, ChatGPT or Cursor

  1. 1

    Connect Mem0 in Corsair

    Add your Mem0 API key once in Corsair. Corsair stores the credential encrypted and makes the Mem0 API calls for your agent, so it never goes into a prompt or a config file. Connect Mem0

    If your link lets the agent add apps, you can skip this: it gives you a sign-in link the first time it needs Mem0. On a ChatGPT personal plan, connect Mem0 here first.

  2. 2

    Add Corsair's MCP server to your agent

    Every client uses the same address:

    https://mcp.corsair.dev/mcp
    Open Customize → Connectors → Add custom connector, paste the address, then select Connect.

    Codex, Gemini CLI, VS Code, Zed and other clients with OAuth sign-in work the same way. Clients without it, such as GitHub Copilot's coding agent, use a link's own address and an API key. Setup for every client

  3. 3

    Sign in and choose what needs your approval

    Your client opens Corsair to sign in. Pick a link: the apps your agent can use and a mode that decides what it may do without asking. In the default Cautious mode, Mem0's read and write operations run right away and its 4 destructive operations wait for your approval. Strict mode asks before every write and refuses destructive operations, and Read mode allows reads only.

FAQ

Install corsair and @corsair-dev/mem0, add the Mem0 plugin, and connect with an API key. Then call methods like corsair.mem0.api.events.get() from your app. Corsair keeps each tenant isolated.

Yes. Mem0 requires an API key from your Mem0 account or developer dashboard. Create credentials with access that matches what you automate, then paste them into Corsair or connect through managed auth in Hub.

Yes. One Corsair client can hit Mem0, GitHub, Notion, Stripe, and the rest. Trigger Mem0 from a webhook, push updates to Slack, or chain actions across plugins. Same tenant context across integrations, plain TypeScript.

Teams use Corsair for long-term memory for ai agents with mem0 - add, search, list, update and delete memories, read a memory's change history, and poll the events mem0 queues for asynchronous work. Common builds include sync jobs, admin tooling, and agents that call Mem0 APIs from your backend.

The SDK is open source. Self-host and you pay Corsair nothing for the integration layer. Hub bills for hosted auth and execution, not per Mem0 API call. Hub has a generous free tier. For hobby projects you can probably run the whole thing on free. Paid plans start to matter with more tenants or heavier traffic.

We maintain @corsair-dev/mem0 in the open repo. When Mem0 ships API changes, upgrade the package. Your call sites stay typed. You should not need to rewrite the integration layer each time.

No. Corsair does not read your Mem0 data or hold individual access credentials. Credentials stay in your database. API calls run on your instance. We do not store Mem0 data on your behalf.

Yes. Add https://mcp.corsair.dev/mcp as a custom connector or MCP server in Claude, ChatGPT, Cursor, VS Code, Claude Code, Codex or any client that supports remote MCP servers with OAuth sign-in, then sign in to Corsair. On ChatGPT personal plans, custom servers currently get read tools only.

Yes. Put Mem0 on a link in Strict mode and every write waits for your approval, while destructive actions are refused. The default Cautious mode asks only before the 4 destructive Mem0 operations. You can change a link's mode at hub.corsair.dev/me.