Mem0

Mem0 MCP integration

Writes memory records as a conversation happens, recalls them semantically when the person returns, and keeps them scoped to the right project.

47actions available

Three actions you can hand over today

Every action runs live through MCP. Nothing to build, nothing to maintain.

  • Add new memory records

    Lyro stores new memory records from conversations, building a persistent knowledge base about each customer. Over time, Lyro learns customer preferences and history, enabling faster, more personalized support.

  • Search memories with filters

    Lyro finds past customer interactions, preferences, or issues using semantic search. Agents answer questions instantly from context instead of asking customers to repeat themselves.

  • Delete an organization

    Lyro removes an entire organization from Mem0 when it's no longer needed. Your platform stays uncluttered with defunct accounts.

See all 47 actions

How businesses use Mem0 + Lyro

Each card is one request a support team gets, and the Mem0 actions Lyro runs to close it.

  • Store what a conversation just established

    Lyro adds memory records from the messages exchanged, scoped to the user, agent, or app they belong to, so a stated preference or an agreed decision is available the next time that person appears.

    Add New Memory RecordsCreate a New UserGet Entity by ID
  • Recall the right memory, not all of them

    Lyro searches memories semantically with a natural language query and structured filters, and pulls everything tied to one entity, so recall is targeted rather than a dump of the whole history.

    Perform Semantic Search on MemoriesSearch Memories With FiltersGet Memories by Entity
  • Keep memories accurate as the facts change

    Lyro updates the text of a memory when the underlying fact moves, corrects up to a thousand at once in a batch, and reads the version history behind one so a change stays traceable.

    Update Memory Text ContentUpdate Memory Batch With UUIDRetrieve Memory History by ID
  • Scope memories to the right project and people

    Lyro creates the project a workspace's memories live in, adds members to it with a role, and registers the webhook that tells another system when something in that project changes.

    Create ProjectAdd Member to ProjectCreate Webhook

How it works

Get started in 3 steps

Connect once, then just ask. There is no workflow builder to learn and nothing to maintain — Lyro reads the Mem0 actions it has and picks the ones a request needs.

  1. 01

    Connect Mem0

    Authorize the Mem0 account your team already uses — one consent screen, no API keys, no mapping tables. Lyro can only do what you granted that account, and you can disconnect it at any time.

  2. 02

    Tell your agent what you need

    Describe the job the way you would hand it to a teammate. Lyro maps it to the Mem0 actions that close it and chains as many as the request needs.

  3. 03

    Watch it work

    The agent runs the actions inside the conversation the customer is already in, so nobody copies data between tabs and your team can take over at any point.

    Get started free
Mem0 · Lyro

Everything else about Mem0

Setup, permissions, and the limits of what Lyro can do inside Mem0.

  • Yes, at several granularities. Delete Memory by ID removes one, Delete Memory Batch With UUIDs clears up to 1000 in a single call, and Delete Memories removes everything matching a filter, though that action requires at least one filter so it cannot empty the store by accident. Delete Entity by Type and ID hard-deletes the user, agent, app, or run itself.

Every action available in Mem0

All 47 actions your agent can call on Mem0, straight from the live MCP connection.

  • Add member to project

    Adds an existing user to a project (identified by project_id within organization org_id), assigning a valid system role.

  • Add new memory records

    Stores new memory records from a list of messages, optionally inferring structured content; requires association via agent_id, user_id, app_id, or run_id.

  • Add organization member

    Adds a new member, who must be a registered user, to an organization, assigning them a specific role.

  • Create a new agent

    Creates a new agent with a unique agent_id and an optional name; additional metadata may be assigned by the system.

  • Create a new agent run

    Creates a new agent run in the mem0.ai system.

  • Create a new application

    Creates a new application, allowing metadata to be passed in the request body (not an explicit field in this action's request model); ensure app_id is unique to avoid potential errors or unintended updates.

  • Create a new organization entry

    Creates a new organization entry using the provided name and returns its details.

  • Create a new user

    Creates a new user with the specified unique user_id and supports associating metadata (not part of the request schema fields).

  • Create memory entry

    Lists/searches existing memory entries with filtering and pagination; critically, this action retrieves memories and does *not* create new ones, despite its name.

  • Create project

    Creates a new project with a given name within an organization that must already exist.

  • Create webhook

    Creates a new webhook for a specific project to receive real-time notifications.

  • Delete an organization

    Permanently deletes an existing organization identified by its unique ID.

  • Delete memory by ID

    Permanently deletes a specific memory by its unique ID; ensure the memory_id exists as this operation is irreversible.

  • Delete entity by type and ID

    Call to permanently and irreversibly hard-delete an existing entity (user, agent, app, or run) and all its associated data, using its type and ID.

  • Delete memories

    Deletes all memories matching specified filter criteria.

  • Delete memory batch with uuids

    Deletes a batch of up to 1000 existing memories, identified by their UUIDs, in a single API call.

  • Delete project

    Permanently deletes a specific project and all its associated data from an organization; this action cannot be undone and requires the project to exist within the specified organization.

  • Delete project member

    Removes an existing member, specified by email address, from a project, immediately revoking their project-specific access; the user is not removed from the organization.

  • Delete webhook

    Deletes a webhook and stops receiving notifications for the specified webhook ID.

  • Export data based on filters

    Creates a new memory export job with optional entity filters (user_id, agent_id, app_id, run_id).

  • List organizations

    Retrieves a summary list of organizations for administrative oversight; returns summary data (names, IDs), not exhaustive details, despite 'detailed' in the name.

  • Fetch details of a specific organization

    Fetches comprehensive details for an organization using its org_id; the org_id must be valid and for an existing organization.

  • Get list of entity filters

    Retrieves predefined filter definitions for entities (e.g., by type, creation/modification date); returns definitions only, not filtered entity data.

  • Get entity by ID

    Fetches detailed information for an existing entity (user, agent, app, or run) identified by its type and unique ID.

  • Get event status by event ID

    Retrieves a single async event by ID to check its current status and results.

  • Get memories by entity

    Retrieve all memories associated with a specific entity (user, agent, app, or run).

  • Get memory export

    Retrieves the status and results of a memory export job by its ID.

  • Get organization members

    Fetches a list of members for a specified, existing organization.

  • Get project details

    Fetches comprehensive details for a specified project within an organization.

  • Get project members

    Retrieves all members for a specified project within an organization.

Ready to connect Mem0?

Authorize the account and your agent has all 47 actions from the first conversation.

Support agent working at a laptop next to the Lyro mascot