# How to connect Mem0 to OpenClaw (paste one key, 47 tools) > Connect Mem0 to OpenClaw with ClawLink: paste your Mem0 key once and 47 tools work from chat. No MCP server to run, nothing stored on your machine. Web version: https://claw-link.dev/openclaw/mem0 The usual route to Mem0 access for OpenClaw is an MCP server you configure and keep running, plus your own OAuth app or API keys. ClawLink gives OpenClaw a more practical Mem0 setup: install one ClawHub skill, connect Mem0 in the browser, and OpenClaw can call real Mem0 actions from any chat surface with no auth, token refresh, or tool wiring to build yourself. **Start here:** install the ClawLink plugin (`openclaw plugins install clawhub:clawlink-plugin`), pair it in the browser, then connect the app in the ClawLink dashboard. The interactive install prompt is on the web version of this page: https://claw-link.dev/openclaw/mem0 ## Setup It takes three steps to connect OpenClaw to Mem0. 1. **Install ClawLink** — add the plugin to OpenClaw once. 2. **Connect Mem0** — one-click OAuth in the ClawLink dashboard. 3. **Use it from chat** — ask OpenClaw in plain English. **Alternative for any agent (no plugin needed):** if the OpenClaw plugin route isn't available or doesn't work, any AI agent with shell access can use the ClawLink CLI instead: ```bash npx -y @useclawlink/cli login # sign in via browser — no API key to paste npx -y @useclawlink/cli connect mem0 # connect Mem0 (browser OAuth) npx -y @useclawlink/cli actions mem0 # list available actions npx -y @useclawlink/cli run mem0 --input '' # execute (add --confirm for writes) ``` ### Install by command The setup prompt above does all of this in one paste. By hand, it is one install command plus a browser approval: ```bash openclaw plugins install clawhub:clawlink-plugin ``` Then ask OpenClaw to set up ClawLink. It starts browser pairing and prints an approval link — open it, approve the device, return to the chat, and say `done`. Finally, connect Mem0 in the [ClawLink dashboard](https://claw-link.dev/dashboard) — paste your Mem0 API key once. Verify the connection by asking OpenClaw: > Use Mem0 to add member to project and walk me through the result in plain English. ### Using a different agent? The OpenClaw plugin is one client of ClawLink's MCP server. Claude Code, Cursor, Codex, or any agent that can run a shell command pairs with the same ClawLink account through the CLI: ```bash npx -y @useclawlink/cli login ``` `login` opens the same browser approval and stores a credential locally. Once Mem0 is connected in the dashboard, that agent calls the same 47 Mem0 tools over MCP. Full setup for MCP clients and shell agents: [connect apps to any AI agent](https://claw-link.dev/learn/connect-apps-to-any-ai-agent). ## Mem0 MCP for OpenClaw Looking for a Mem0 MCP server for OpenClaw? ClawLink connects Mem0 to OpenClaw and exposes 47 Mem0 tools your agent can call over [MCP](https://claw-link.dev/learn/what-is-an-mcp-server), with [hosted auth](https://claw-link.dev/learn/oauth-for-ai-agents) and nothing to run or maintain yourself. Using Hermes instead? The [Hermes Mem0 integration](https://claw-link.dev/hermes/mem0) works the same way. ## What the OpenClaw Mem0 integration can do 47 Mem0 tools are ready for OpenClaw once the account is connected. The 30 below are the ones people reach for most; your agent can call all 47. ### 30 of 47 Mem0 tools for OpenClaw | Tool | What it does | |---|---| | **Add member to project** `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. | | **Add new memory records** `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`. | | **Add organization member** `mem0_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** `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. | | **Create a new agent run** `mem0_create_a_new_agent_run` | Creates a new agent run in the mem0.ai system. | | **Create a new application** `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 unintended updates. | | **Create a new organization entry** `mem0_create_a_new_organization_entry` | Creates a new organization entry using the provided name and returns its details. | | **Create a new user** `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). | | **Create memory entry** `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. | | **Create project** `mem0_create_project` | Creates a new project with a given name within an organization that must already exist. | | **Create webhook** `mem0_create_webhook` | Creates a new webhook for a specific project to receive real-time notifications. Use when you need to set up event-driven integrations that trigger on memory operations. | | **Fetch detailed list of organizations** `mem0_fetch_detailed_list_of_organizations` | Retrieves a summary list of organizations for administrative oversight; returns summary data | | **Fetch details of a specific organization** `mem0_fetch_details_of_a_specific_organization` | Fetches comprehensive details for an organization using its `org_id`; the `org_id` must be | | **Fetch list of entity filters** `mem0_fetch_list_of_entity_filters` | Retrieves predefined filter definitions for entities (e.g., by type, creation/modification | | **Fetch specific entity details with optional filters** `mem0_fetch_specific_entity_details_with_optional_filters` | Fetches detailed information for an existing entity (user, agent, app, or run) identified by | | **Get event status by event ID** `mem0_get_event_status_by_event_id` | Retrieves a single async event by ID to check its current status and results | | **Get memories by entity** `mem0_get_memories_by_entity` | Retrieve all memories associated with a specific entity (user, agent, app, or run) | | **Get memory export** `mem0_get_memory_export` | Retrieves the status and results of a memory export job by its ID | | **Get organization members** `mem0_get_organization_members` | Fetches a list of members for a specified, existing organization | | **Get project details** `mem0_get_project_details` | Fetches comprehensive details for a specified project within an organization | | **Get project members** `mem0_get_project_members` | Retrieves all members for a specified project within an organization | | **Get project webhooks** `mem0_get_project_webhooks` | Retrieves all webhooks configured for a specific project | | **Get projects** `mem0_get_projects` | Retrieves all projects for a given organization `org_id` to which the caller has access | | **Get user memory stats** `mem0_get_user_memory_stats` | Retrieves a summary of the authenticated user's memory activity, including total memories | | **List entities with optional org and project filters** `mem0_list_entities_with_optional_org_and_project_filters` | Retrieves a list of entities, optionally filtered by organization or project (prefer | | **Perform semantic search on memories** `mem0_perform_semantic_search_on_memories` | Searches memories semantically using a natural language query and metadata filters | | **Retrieve all events for the currently logged in user** `mem0_retrieve_all_events_for_the_currently_logged_in_user` | Retrieves a paginated list of events for the authenticated user, filterable and paginable via | | **Retrieve list of memory events** `mem0_retrieve_list_of_memory_events` | Retrieves a chronological list of all memory events (e.g., user inputs, AI responses) from the | | **Retrieve memory by unique identifier** `mem0_retrieve_memory_by_unique_identifier` | Retrieves a complete memory entry by its unique identifier; `memory_id` must be valid and for | | **Retrieve memory history by ID** `mem0_retrieve_memory_history_by_id` | Retrieves the complete version history for an existing memory, using its unique `memory_id`, to | ## Example prompts **Add Member To Project** > Use Mem0 to add member to project and walk me through the result in plain English. **Add New Memory Records** > Use Mem0 to add new memory records and walk me through the result in plain English. **Add Organization Member** > Use Mem0 to add organization member and walk me through the result in plain English. **Create A New Agent** > Create it in Mem0 for me, then confirm the important fields before you finish. ## ClawLink vs. building it yourself The alternative to ClawLink is usually manual API key setup plus your own token handling, permission troubleshooting, and tool plumbing for OpenClaw. That is fine if you want to build and maintain the integration yourself. Most teams just want Mem0 working from chat. | | Manual | ClawLink | |---|---|---| | **Credential handling** | Collect, validate, store, and rotate the Mem0 API key yourself, then make sure every tool call uses the right account. | Users complete the hosted ClawLink setup once and the connected Mem0 account becomes available to the agent without you building credential management. | | **Ongoing maintenance** | You own refresh logic, permission debugging, environment config, and every provider-specific edge case for Mem0. | ClawLink handles the repetitive integration plumbing so your team can focus on the workflow instead of the infrastructure. | | **Agent usability** | You still need to expose the right Mem0 actions to the runtime in a format your agent can reliably use. | 47 tools for Mem0 are already exposed through ClawLink, so the agent can read and act from chat immediately. | ## ClawLink vs. Composio Composio also exposes Mem0 to AI agents. It is developer infrastructure: Python and TypeScript SDKs, an MCP server, and a catalog past 1,000 apps, aimed at teams shipping agent products. ClawLink is built for OpenClaw users instead. You install the plugin once, connect Mem0 in the browser, and the 47 tools above work from chat. There is no SDK and no config file, and the Mem0 key you paste at setup is stored server-side rather than kept in your environment. Choosing between them? Read the full [Composio alternatives](https://claw-link.dev/hub/composio-alternatives) comparison. ### OpenClaw installed the Mem0 skill but can't call the tools The ClawHub skill teaches OpenClaw about Mem0, but the calls run through the ClawLink plugin and your connected account. Make sure Mem0 is connected in the dashboard, then start a fresh chat so OpenClaw reloads the tool catalog. If OpenClaw runs as a persistent gateway, restart it so the new tools register. ### Connection succeeds but no tools appear Reconnect Mem0 from the dashboard, then start a fresh chat if the runtime still has the old tool catalog loaded. ### "Tool schema not loaded yet" error when calling Mem0 tools Mem0 tool schemas load on demand the first time a tool runs and are cached after that, so this error usually clears on its own: wait a few seconds and retry the same request. If every Mem0 call keeps failing with it in a fresh chat, reconnect from the dashboard, and contact support if it still persists — that pattern points to a configuration problem on our side, not something you can fix by reconnecting again. ### Mem0 returns 403 or "permission denied" on one action while others work Two usual causes. The connected account may not have access to the specific workspace, inbox, store, or project in the request — check that first. If access looks right, the agent may have sent a placeholder value (like "YOUR_ID" or an example id from documentation) instead of a real one: ask it to run a list or search tool first, then retry the action with a real id from those results. Most failures at this stage are one of these two, not ClawLink bugs. ### API key setup works but results look incomplete Double-check that the API key for Mem0 has the right scopes or account access. A valid key can still be too limited for some reads or writes. ### Is there a OpenClaw Mem0 integration? Yes. ClawLink is the fastest way to connect OpenClaw to Mem0: link your Mem0 account once in the browser and OpenClaw can call the Mem0 API through 47 ready-made tools — no custom code or token handling. ### How do I add Mem0 to OpenClaw with ClawLink? Paste the setup prompt from this page into OpenClaw. It installs the ClawLink Mem0 skill from ClawHub, then you click Connect in the dashboard to authorize Mem0. OpenClaw calls the tools from the next message — no config files, and the Mem0 key you paste is stored server-side instead of in your environment. ### How long does it take to connect Mem0 to OpenClaw? About two minutes. Sign in, click Connect next to Mem0 in the dashboard, authenticate, and OpenClaw can use it from the next chat message. ### Why use ClawLink instead of wiring Mem0 up myself? The alternative to ClawLink is usually manual API key setup plus your own token handling, permission troubleshooting, and tool plumbing for OpenClaw. That is fine if you want to build and maintain the integration yourself. Most teams just want Mem0 working from chat. ### OpenClaw installed the Mem0 skill but can't call the tools The ClawHub skill teaches OpenClaw about Mem0, but the calls run through the ClawLink plugin and your connected account. Make sure Mem0 is connected in the dashboard, then start a fresh chat so OpenClaw reloads the tool catalog. If OpenClaw runs as a persistent gateway, restart it so the new tools register. ## Related - [DataRobot](https://claw-link.dev/openclaw/datarobot) — DataRobot is a machine learning platform that automates model building, deployment, and monitoring, enabling organizations to derive predictive insights from large datasets. - [Chatbotkit](https://claw-link.dev/openclaw/chatbotkit) — ChatBotKit is a platform that enables developers to build and manage AI-powered chatbots, offering comprehensive APIs and SDKs for seamless integration into applications. - [Connect ElevenLabs](https://claw-link.dev/openclaw/elevenlabs) — Generate speech and voice cloning