MCP / AI and media
Mem0 MCP: AI workflows
Mem0 is an universal, self-improving memory layer for LLM applications. Connect it to Claude, Codex, Cursor or any MCP client through one FlyMy.AI MCP.
$ YOUR NEXT RUN
Use Mem0 MCP in your assistant
Paste this prompt into Claude Code, Codex, Cursor or any agent. It reads the guide and helps you connect.
Read https://flymy.ai/skill.md and https://flymy.ai/mcp/mem0.md. Help me connect Mem0 MCP to this assistant. Then help me run this task: Use Mem0 to add member to project. Ask me for the required inputs first and show the result.
What Mem0 MCP can do
43 actions in the FlyMy.AI catalog, the most used first. Your agent finds them through search_tools and calls the one the task needs.
| Action | What it does |
|---|---|
# MEM0_ADD_MEMBER_TO_PROJECT | Adds an existing user to a project (identified by `project id` within organization `org id`), assigning a valid system role. |
# MEM0_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`. |
# MEM0_ADD_ORGANIZATION_MEMBER | Adds a new member, who must be a registered user, to an organization, assigning them a specific role. |
# MEM0_CREATE_AN_EXPORT_JOB_WITH_SCHEMA | Initiates an asynchronous job to export memories, structured by a schema provided in the request body and allowing optional filters. |
# MEM0_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. |
# MEM0_CREATE_A_NEW_AGENT_RUN | Creates a new agent run in the mem0.ai system. |
# MEM0_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... |
# MEM0_CREATE_A_NEW_ORGANIZATION_ENTRY | Creates a new organization entry using the provided name and returns its details. |
# MEM0_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). |
# MEM0_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. |
# MEM0_CREATE_PROJECT | Creates a new project with a given name within an organization that must already exist. |
# MEM0_DELETE_AN_ORGANIZATION | Permanently deletes an existing organization identified by its unique id. |
Show all 43 actions
| Action | What it does |
|---|---|
# MEM0_DELETE_A_SPECIFIC_MEMORY_BY_ID | Permanently deletes a specific memory by its unique id; ensure the `memory id` exists as this operation is irreversible. |
# MEM0_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. |
# MEM0_DELETE_MEMORIES_ENDPOINT | Deletes memories matching specified filter criteria; omitting all filters may result in deleting all memories. |
# MEM0_DELETE_MEMORY_BATCH_WITH_UUIDS | Deletes a batch of up to 1000 existing memories, identified by their uuids, in a single api call. |
# MEM0_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. |
# MEM0_DELETE_PROJECT_MEMBER | Removes an existing member, specified by username, from a project, immediately revoking their project-specific access; the user is not removed from the organization. |
# MEM0_EXPORT_DATA_BASED_ON_FILTERS | Retrieves memory export data, optionally filtered by various identifiers (e.g., user id); without filters, it may return all accessible or recent exports based on default behavior. |
# MEM0_FETCH_DETAILED_LIST_OF_ORGANIZATIONS | Retrieves a summary list of organizations for administrative oversight; returns summary data (names, ids), not exhaustive details, despite 'detailed' in the name. |
# MEM0_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. |
# MEM0_FETCH_LIST_OF_ENTITY_FILTERS | Retrieves predefined filter definitions for entities (e.g., by type, creation/modification date); returns definitions only, not filtered entity data. |
# MEM0_FETCH_SPECIFIC_ENTITY_DETAILS_WITH_OPTIONAL_FILTERS | Fetches detailed information for an existing entity (user, agent, app, or run) identified by its type and unique id. |
# MEM0_GET_ORGANIZATION_MEMBERS | Fetches a list of members for a specified, existing organization. |
# MEM0_GET_PROJECTS | Retrieves all projects for a given organization `org id` to which the caller has access. |
# MEM0_GET_PROJECT_DETAILS | Fetches comprehensive details for a specified project within an organization. |
# MEM0_GET_PROJECT_MEMBERS | Retrieves all members for a specified project within an organization. |
# MEM0_GET_USER_MEMORY_STATS | Retrieves a summary of the authenticated user's memory activity, including total memories created, search events, and add events. |
# MEM0_LIST_ENTITIES_WITH_OPTIONAL_ORG_AND_PROJECT_FILTERS | Retrieves a list of entities, optionally filtered by organization or project (prefer `org id`/`project id` over deprecated `org name`/`project name`), noting results may be summaries and subject... |
# MEM0_PERFORM_SEMANTIC_SEARCH_ON_MEMORIES | Searches memories semantically using a natural language query (required if `only metadata based search` is false) and/or metadata filters. |
# MEM0_REMOVE_A_MEMBER_FROM_THE_ORGANIZATION | Removes a member, specified by their username, from an existing organization of which they are currently a member. |
# MEM0_RETRIEVE_ALL_EVENTS_FOR_THE_CURRENTLY_LOGGED_IN_USER | Retrieves a paginated list of events for the authenticated user, filterable and paginable via url query parameters. |
# MEM0_RETRIEVE_ENTITY_SPECIFIC_MEMORIES | Retrieves all memories (e.g., user preferences, chat history) for a specific entity from the mem0 platform, using its `entity type` and `entity id`; ensure the entity exists. |
# MEM0_RETRIEVE_LIST_OF_MEMORY_EVENTS | Retrieves a chronological list of all memory events (e.g., user inputs, ai responses) from the mem0 platform, providing interaction history and context for ai assistants. |
# MEM0_RETRIEVE_MEMORY_BY_UNIQUE_IDENTIFIER | Retrieves a complete memory entry by its unique identifier; `memory id` must be valid and for an existing memory. |
# MEM0_RETRIEVE_MEMORY_HISTORY_BY_ID | Retrieves the complete version history for an existing memory, using its unique `memory id`, to inspect its evolution or audit changes. |
# MEM0_RETRIEVE_MEMORY_LIST | Retrieves a list of memories, supporting pagination and diverse filtering (e.g., by ids, metadata, keywords, date ranges); ensure dates are iso 8601 and `page`/`page size` (if used) are positive... |
# MEM0_SEARCH_MEMORIES_WITH_QUERY_FILTERS | Semantically searches memories using a natural language query and mandatory structured filters, offering options to rerank results and select specific fields; any provided `org id` or `project id`... |
# MEM0_UPDATE_MEMORY_BATCH_WITH_UUID | Updates text for up to 1000 memories in a single batch, using their uuids. |
# MEM0_UPDATE_MEMORY_DETAILS_BY_ID | Updates the text content of an existing memory, identified by its `memory id`. |
# MEM0_UPDATE_ORGANIZATION_MEMBER_ROLE | Updates the role of an existing member to a new valid role within an existing organization. |
# MEM0_UPDATE_PROJECT | Updates a project by `project id` within an `org id`, modifying only provided fields (name, description, custom instructions, custom categories); list fields are fully replaced (cleared by `[]`)... |
# MEM0_UPDATE_PROJECT_MEMBER_ROLE | Updates the role of a specific member within a designated project, ensuring the new role is valid and recognized by the system. |
Ask your agent
Requests to paste as they are. Each one runs on the actions named under it.
MEM0_ADD_MEMBER_TO_PROJECTMEM0_ADD_NEW_MEMORY_RECORDSMEM0_ADD_ORGANIZATION_MEMBERConnect Mem0 in a minute
One MCP for every integration. Add it once, then every MCP in the catalog is a request away.
- 01
Add FlyMy.AI
Add the FlyMy.AI MCP to your assistant with one of the commands below and sign in. No key to copy.
- 02
Add your API Key
Paste it into the Mem0 connection settings once; it stays with FlyMy.AI, never in a prompt or a chat.
- API Key - Your Mem0 API key for authentication. Obtain it from your Mem0 settings. Get API key →
- 03
Ask
Paste a request from this page. Every run shows what it cost.
claude mcp add --transport http flymyai https://mcp-agents.flymy.ai/mcp
Then run /mcp in Claude Code and sign in.
codex mcp add flymy --url https://mcp-agents.flymy.ai/mcp
Then run codex mcp login flymy to sign in.
https://mcp-agents.flymy.ai/mcp
Settings, Connectors, Add custom connector: paste this URL.
Pay per run
FlyMy.AI bills the run: the model and the tool's seconds. Calls go to your own Mem0 account, under its plan and limits. No seats and no minimum.
Go to the source
From the FlyMy.AI platform catalog of 2026-11-03: name, description, actions and setup as the platform lists them. Examples are requests to paste, not recorded runs.