How to connect Mem0 to Claude Cowork

Trusted by
AWS
Glean
Zoom
Airtable

30 min · no commitment · see it on your stack

Mem0 logo
Claude Cowork logo
divider

Introduction

Cowork is Anthropic's AI agent for knowledge work. Think of it as Claude Code for everything else. It works autonomously with your computer, local files, and applications to accomplish complex tasks.

This guide walks you through the easiest and most secure way to connect your Mem0 account to Cowork via Composio Connect, enabling it to store meeting notes from today's call, export all project memories as CSV, add new user to our team space, and more such actions on your behalf without compromising your account security.

Also integrate Mem0 with

Connecting Mem0 to Claude Cowork

1. Open Customize

In Claude Desktop, click Customize in the left sidebar, then select Connectors and click the + icon at the top.

Claude Desktop connectors screen with Add custom connector selected

2. Add the Composio MCP server

Click Add custom connector and paste in the Composio MCP server URL:

bash
https://connect.composio.dev/mcp
Add custom connector dialog with Composio MCP server URL

3. Authorize in your browser

Click Connect. You'll be redirected to a browser window where you can authorize Composio to continue.

Composio authorization screen for Claude Cowork

4. Connect your Mem0 account

Back in Cowork, ask the agent to connect to Mem0 or give it any Mem0-related task.

For example, ask Cowork to:

  • "Store meeting notes from today's call"
  • "Export all project memories as CSV"
  • "Add new user to our team space"

It will prompt you to authenticate and authorize access.

That's it. Composio's tools are now available in Cowork, and your Mem0 account is ready to use.

What is Claude Cowork?

Claude Cowork is Anthropic's agent for general knowledge work. It can use your computer, files, and connected applications to complete longer-running tasks across your work tools.

With Composio Connect, Cowork can securely access apps like Mem0 through MCP without you sharing account credentials directly with the agent.

What is the Mem0 MCP server, and what's possible with it?

The Mem0 MCP server is an implementation of the Model Context Protocol that connects your AI agent and assistants like Claude, Cursor, etc directly to your Mem0 account. It provides structured and secure access to your notes, projects, and organizational knowledge, so your agent can perform actions like searching memories, managing users, adding content, and orchestrating agent runs on your behalf.

  • AI-powered memory search and recall: Let your agent search and retrieve existing memory entries using advanced filters and pagination to surface just the right note or piece of information.
  • Automated content and note creation: Have your agent store new memory records from conversations, meetings, or tasks—ensuring nothing slips through the cracks.
  • Collaboration and organization management: Direct your agent to add members to projects or organizations, assign roles, and keep team structures up to date.
  • Agent and application orchestration: Enable your agent to create new AI agents, initiate agent runs, and manage applications for custom workflows and automation.
  • Structured knowledge export and reporting: Ask your agent to initiate export jobs with specific schemas and filters, so you can back up or analyze your stored knowledge on demand.

Supported Tools & Triggers

Tools
Add member to projectAdds an existing user to a project (identified by `project_id` within organization `org_id`), assigning a valid system role.
Add new memory recordsStores 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 memberAdds a new member, who must be a registered user, to an organization, assigning them a specific role.
Create a new agentCreates a new agent with a unique `agent_id` and an optional `name`; additional metadata may be assigned by the system.
Create a new agent runCreates a new agent run in the mem0.
Create a new applicationCreates 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 entryCreates a new organization entry using the provided name and returns its details.
Create a new userCreates a new user with the specified unique `user_id` and supports associating `metadata` (not part of the request schema fields).
Create memory entryLists/searches existing memory entries with filtering and pagination; critically, this action retrieves memories and does *not* create new ones, despite its name.
Create projectCreates a new project with a given name within an organization that must already exist.
Create webhookCreates a new webhook for a specific project to receive real-time notifications.
Delete an organizationPermanently deletes an existing organization identified by its unique ID.
Delete memory by idPermanently deletes a specific memory by its unique ID; ensure the `memory_id` exists as this operation is irreversible.
Delete entity by type and idCall 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 memoriesDeletes all memories matching specified filter criteria.
Delete memory batch with uuidsDeletes a batch of up to 1000 existing memories, identified by their UUIDs, in a single API call.
Delete projectPermanently 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 memberRemoves 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 webhookDeletes a webhook and stops receiving notifications for the specified webhook ID.
Export data based on filtersCreates a new memory export job with optional entity filters (user_id, agent_id, app_id, run_id).
List organizationsRetrieves 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 organizationFetches comprehensive details for an organization using its `org_id`; the `org_id` must be valid and for an existing organization.
Get list of entity filtersRetrieves predefined filter definitions for entities (e.
Get entity by idFetches detailed information for an existing entity (user, agent, app, or run) identified by its type and unique ID.
Get event status by event IDRetrieves a single async event by ID to check its current status and results.
Get memories by entityTool to retrieve all memories associated with a specific entity (user, agent, app, or run).
Get memory exportRetrieves the status and results of a memory export job by its ID.
Get organization membersFetches a list of members for a specified, existing organization.
Get project detailsFetches comprehensive details for a specified project within an organization.
Get project membersRetrieves all members for a specified project within an organization.
Get projectsRetrieves all projects for a given organization `org_id` to which the caller has access.
Get project webhooksRetrieves all webhooks configured for a specific project.
Get user memory statsRetrieves a summary of the authenticated user's memory activity, including total memories created, search events, and add events.
List entitiesRetrieves 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 to limits.
Perform semantic search on memoriesSearches memories semantically using a natural language query and metadata filters.
Remove a member from the organizationRemoves a member, specified by their username, from an existing organization of which they are currently a member.
Retrieve all events for the currently logged in userRetrieves a paginated list of events for the authenticated user, filterable and paginable via URL query parameters.
Retrieve list of memory eventsRetrieves a chronological list of all memory events (e.
Retrieve memory by idRetrieves a complete memory entry by its unique identifier; `memory_id` must be valid and for an existing memory.
Retrieve memory history by idRetrieves the complete version history for an existing memory, using its unique `memory_id`, to inspect its evolution or audit changes.
Retrieve memory listRetrieves a list of memories, supporting pagination and diverse filtering (e.
Search memories with filtersSemantically searches memories using structured filters with an optional natural language query.
Update memory batch with uuidUpdates text for up to 1000 memories in a single batch, using their UUIDs.
Update memory text contentUpdates the text content of an existing memory, identified by its `memory_id`.
Update organization member roleUpdates the role of an existing member to a new valid role within an existing organization.
Update projectUpdates 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 `[]`), other omitted/null fields remain unchanged.
Update project member roleUpdates the role of a specific member within a designated project, ensuring the new role is valid and recognized by the system.

How to build Mem0 MCP Agent with another framework

FAQ

What are the differences in Tool Router MCP and Mem0 MCP?

With a standalone Mem0 MCP server, the agents and LLMs can only access a fixed set of Mem0 tools tied to that server. However, with the Composio Tool Router, agents can dynamically load tools from Mem0 and many other apps based on the task at hand, all through a single MCP endpoint.

Can I use Tool Router MCP with Claude Cowork?

Yes, you can. Claude Cowork fully supports MCP integration. You get structured tool calling, message history handling, and model orchestration while Tool Router takes care of discovering and serving the right Mem0 tools.

Can I manage the permissions and scopes for Mem0 while using Tool Router?

Yes, absolutely. You can configure which Mem0 scopes and actions are allowed when connecting your account to Composio. You can also bring your own OAuth credentials or API configuration so you keep full control over what the agent can do.

How safe is my data with Composio Tool Router?

All sensitive data such as tokens, keys, and configuration is fully encrypted at rest and in transit. Composio is SOC 2 Type 2 compliant and follows strict security practices so your Mem0 data and credentials are handled as safely as possible.

Used by agents from

Context
Letta
glean
HubSpot
Agent.ai
Altera
DataStax
Entelligence
Rolai
Context
Letta
glean
HubSpot
Agent.ai
Altera
DataStax
Entelligence
Rolai
Context
Letta
glean
HubSpot
Agent.ai
Altera
DataStax
Entelligence
Rolai

Never worry about agent reliability

We handle tool reliability, observability, and security so you never have to second-guess an agent action.