# How to connect Mem0 to Muse

```json
{
  "title": "How to connect Mem0 to Muse",
  "toolkit": "Mem0",
  "toolkit_slug": "mem0",
  "framework": "Muse",
  "framework_slug": "muse",
  "url": "https://composio.dev/toolkits/mem0/framework/muse",
  "markdown_url": "https://composio.dev/toolkits/mem0/framework/muse.md",
  "updated_at": "2026-10-01T09:23:01.707Z"
}
```

## Introduction

Muse is Meta's AI assistant. It can connect to outside tools through custom connectors, which use the Model Context Protocol (MCP).
This guide explains how to connect Mem0 to Muse using Composio Connect, which handles OAuth, token refresh, and reliability so you do not have to. You add Composio as a custom connector once, then ask Muse to work with Mem0 in plain language.

## Also integrate Mem0 with

- [Claude Code](https://composio.dev/toolkits/mem0/framework/claude-code)
- [Cursor](https://composio.dev/toolkits/mem0/framework/cursor)
- [ChatGPT](https://composio.dev/toolkits/mem0/framework/chatgpt)
- [Claude Cowork](https://composio.dev/toolkits/mem0/framework/claude-cowork)
- [Antigravity](https://composio.dev/toolkits/mem0/framework/antigravity)
- [OpenAI Agents SDK](https://composio.dev/toolkits/mem0/framework/open-ai-agents-sdk)
- [Claude Agent SDK](https://composio.dev/toolkits/mem0/framework/claude-agents-sdk)
- [Codex](https://composio.dev/toolkits/mem0/framework/codex)
- [Kimi Code](https://composio.dev/toolkits/mem0/framework/kimi)
- [Grok Build](https://composio.dev/toolkits/mem0/framework/grok-build)
- [VS Code](https://composio.dev/toolkits/mem0/framework/vscode)
- [OpenCode](https://composio.dev/toolkits/mem0/framework/opencode)
- [OpenClaw](https://composio.dev/toolkits/mem0/framework/openclaw)
- [Hermes](https://composio.dev/toolkits/mem0/framework/hermes-agent)
- [Atomic Agent](https://composio.dev/toolkits/mem0/framework/atomic-agent)
- [CLI](https://composio.dev/toolkits/mem0/framework/cli)
- [Google ADK](https://composio.dev/toolkits/mem0/framework/google-adk)
- [LangChain](https://composio.dev/toolkits/mem0/framework/langchain)
- [Vercel AI SDK](https://composio.dev/toolkits/mem0/framework/ai-sdk)
- [Mastra AI](https://composio.dev/toolkits/mem0/framework/mastra-ai)
- [LlamaIndex](https://composio.dev/toolkits/mem0/framework/llama-index)
- [CrewAI](https://composio.dev/toolkits/mem0/framework/crew-ai)
- [Pydantic AI](https://composio.dev/toolkits/mem0/framework/pydantic-ai)
- [AutoGen](https://composio.dev/toolkits/mem0/framework/autogen)

## TL;DR

- Cross-app workflows across 1,500+ apps from a single plugin layer.
- On-demand tool loading so Muse only loads the tools needed for the current task.
- Programmatic tool calling through a remote workbench for complex, multi-step workflows.
- Multi-account support so users can connect and switch between multiple accounts for the same app.
- Shared account access so teams or agents can work through common business accounts and service connections.
- Managed authentication with OAuth handling, credential storage, and token refresh managed by Composio.
- Safer credential handling so app credentials stay outside the model context and tool responses.
- User-level account isolation so actions run against the correct connected account instead of mixing user access.

## Connect Mem0 to Muse

### Connecting Mem0 to Muse
You add Composio to Muse once as a custom connector, then connect Mem0 from the chat.

## 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

| Tool slug | Name | Description |
|---|---|---|
| `MEM0_ADD_MEMBER_TO_PROJECT` | 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` | 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` | Add organization member | Adds a new member, who must be a registered user, to an organization, assigning them a specific role. |
| `MEM0_CREATE_A_NEW_AGENT` | 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` | Create a new agent run | Creates a new agent run in the mem0.ai system. |
| `MEM0_CREATE_A_NEW_APPLICATION` | 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. |
| `MEM0_CREATE_A_NEW_ORGANIZATION_ENTRY` | Create a new organization entry | Creates a new organization entry using the provided name and returns its details. |
| `MEM0_CREATE_A_NEW_USER` | 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` | 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` | Create project | Creates a new project with a given name within an organization that must already exist. |
| `MEM0_CREATE_WEBHOOK` | 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. |
| `MEM0_DELETE_AN_ORGANIZATION` | Delete an organization | Permanently deletes an existing organization identified by its unique ID. |
| `MEM0_DELETE_A_SPECIFIC_MEMORY_BY_ID` | Delete 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` | 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` | Delete memories | Deletes all memories matching specified filter criteria. IMPORTANT: At least one filter (agent_id, user_id, app_id, or run_id) must be provided to prevent accidental deletion of all memories. Requires delete permissions on the organization/project. |
| `MEM0_DELETE_MEMORY_BATCH_WITH_UUIDS` | 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` | 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` | 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. |
| `MEM0_DELETE_WEBHOOK` | Delete webhook | Deletes a webhook and stops receiving notifications for the specified webhook ID. Use this when you no longer need webhook notifications or want to remove a specific webhook configuration. |
| `MEM0_EXPORT_DATA_BASED_ON_FILTERS` | Export data based on filters | Creates a new memory export job with optional entity filters (user_id, agent_id, app_id, run_id). Returns export job ID and confirmation message. Requires org_id and project_id. Uses default schema for memory structure if not specified. |
| `MEM0_FETCH_DETAILED_LIST_OF_ORGANIZATIONS` | List 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` | 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` | 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. |
| `MEM0_FETCH_SPECIFIC_ENTITY_DETAILS_WITH_OPTIONAL_FILTERS` | Get entity by id | Fetches detailed information for an existing entity (user, agent, app, or run) identified by its type and unique ID. |
| `MEM0_GET_EVENT_STATUS_BY_EVENT_ID` | Get event status by event ID | Retrieves a single async event by ID to check its current status and results. Use this after operations that return event IDs (e.g., add_new_memory_records) to poll for completion before proceeding with dependent operations. |
| `MEM0_GET_MEMORIES_BY_ENTITY` | Get memories by entity | Tool to retrieve all memories associated with a specific entity (user, agent, app, or run). Use when you need to fetch memories for a known entity type and ID combination. |
| `MEM0_GET_MEMORY_EXPORT` | Get memory export | Retrieves the status and results of a memory export job by its ID. Use this after creating an export job to fetch the processed memory data. The response structure matches the schema defined during export creation. |
| `MEM0_GET_ORGANIZATION_MEMBERS` | Get organization members | Fetches a list of members for a specified, existing organization. |
| `MEM0_GET_PROJECT_DETAILS` | Get project details | Fetches comprehensive details for a specified project within an organization. |
| `MEM0_GET_PROJECT_MEMBERS` | Get project members | Retrieves all members for a specified project within an organization. |
| `MEM0_GET_PROJECTS` | Get projects | Retrieves all projects for a given organization `org_id` to which the caller has access. |
| `MEM0_GET_PROJECT_WEBHOOKS` | Get project webhooks | Retrieves all webhooks configured for a specific project. Use this to list webhook configurations including their event types, URLs, and active status. |
| `MEM0_GET_USER_MEMORY_STATS` | Get user memory stats | Retrieves a summary of the authenticated user's memory activity, including total memories created, search events, and add events. Note: This endpoint is undocumented in the official mem0 API specification but is functional. |
| `MEM0_LIST_ENTITIES_WITH_OPTIONAL_ORG_AND_PROJECT_FILTERS` | List entities | 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 to limits. |
| `MEM0_PERFORM_SEMANTIC_SEARCH_ON_MEMORIES` | Perform semantic search on memories | Searches memories semantically using a natural language query and metadata filters. IMPORTANT: - At least one of 'user_id', 'agent_id', or 'run_id' MUST be provided - A non-empty 'query' string is REQUIRED for semantic search - To retrieve memories without a search query, use 'retrieve_memory_list' action instead |
| `MEM0_REMOVE_A_MEMBER_FROM_THE_ORGANIZATION` | 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` | 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. This is a read-only operation that does not modify data. Supported Query Parameters (applied directly to the request URL): - `event_type` (str, optional): Filters events by their type (e.g., 'ADD', 'SEARCH'). - `start_date` (str, optional): Filters events on or after this date (format: YYYY-MM-DD). - `end_date` (str, optional): Filters events on or before this date (format: YYYY-MM-DD). - `page` (int, optional): Specifies the page number for paginated results. - `page_size` (int, optional): Number of events per page (default: 50, max: 100). |
| `MEM0_RETRIEVE_LIST_OF_MEMORY_EVENTS` | 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` | Retrieve memory by id | 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` | 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` | 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 integers. REQUIRED: At least one of agent_id, user_id, app_id, or run_id must be provided. |
| `MEM0_SEARCH_MEMORIES_WITH_QUERY_FILTERS` | Search memories with filters | Semantically searches memories using structured filters with an optional natural language query. If query is omitted, defaults to '*' (wildcard) for filter-only searches. Offers options to rerank results, select specific fields, and adjust similarity threshold; any provided `org_id` or `project_id` must reference a valid existing entity. |
| `MEM0_UPDATE_MEMORY_BATCH_WITH_UUID` | 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` | Update memory text content | Updates the text content of an existing memory, identified by its `memory_id`. |
| `MEM0_UPDATE_ORGANIZATION_MEMBER_ROLE` | Update organization member role | Updates the role of an existing member to a new valid role within an existing organization. |
| `MEM0_UPDATE_PROJECT` | 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 `[]`), other omitted/null fields remain unchanged. |
| `MEM0_UPDATE_PROJECT_MEMBER_ROLE` | 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. |

## Supported Triggers

None listed.

## Troubleshooting

### 1. Why doesn't Muse show a button to add my API key?

Muse shows the button only when you ask it to open the secure credentials store.
- Start a new chat.
- Send the message from step 1 exactly as written.
- If Muse asks for the key in the chat, do not paste it. Ask Muse to open the secure credentials store.

### 2. Why does the Composio connection fail after I add my API key?

The key or the connector settings are not correct.
- Copy the full key from the Composio dashboard. It starts with ck_.
- Make sure the URL is https://connect.composio.dev/mcp and the header is x-consumer-api-key.
- Remove the Composio connector in Muse settings, then do steps 1 to 3 again.

### 3. Why doesn't Muse use the Composio tools for Mem0?

Muse may not pick the Composio connector for the request.
- Ask Muse to list its Composio tools.
- Name Composio and Mem0 in your request, for example: Use Composio to connect to Mem0.
- If it still does not work, start a new chat and try again.

### 4. Why does Muse ask me to connect Mem0 again?

Your Mem0 connection expired or was removed.
- Open the link Muse gives you and sign in to Mem0 again.
- Check that the Mem0 connection shows as ACTIVE in the Composio dashboard.

### 5. What do I do if I pasted my API key into the chat?

Treat the key as exposed.
- Create a new API key in the Composio dashboard and delete the old one.
- Add the new key in Muse's secure credentials store, not in the chat.

## Creating MCP Server - Stand-alone vs Composio SDK

Once connected, Muse can access the Mem0 MCP server through Composio to run the actions you authorize, using plain language in the chat.

## Complete Code

None listed.

## Conclusion

### Way Forward
Now that Mem0 is connected, extend your setup by connecting the other apps you already use every day, so Muse can run true cross-app workflows end to end.
- Connect Calendar to turn threads into scheduled meetings automatically.
- Connect Slack or Teams to post summaries, approvals, and alerts where your team works.
- Connect Notion, Linear, Jira, or Asana to convert requests into tickets, tasks, and docs.
- Connect Drive, Dropbox, or OneDrive to fetch, file, and share attachments without manual steps.
Start with one workflow you do repeatedly, then keep adding apps as you find new handoffs. With everything behind a single connection, Muse can coordinate multiple tools safely and reliably in one conversation.

## How to build Mem0 MCP Agent with another framework

- [Claude Code](https://composio.dev/toolkits/mem0/framework/claude-code)
- [Cursor](https://composio.dev/toolkits/mem0/framework/cursor)
- [ChatGPT](https://composio.dev/toolkits/mem0/framework/chatgpt)
- [Claude Cowork](https://composio.dev/toolkits/mem0/framework/claude-cowork)
- [Antigravity](https://composio.dev/toolkits/mem0/framework/antigravity)
- [OpenAI Agents SDK](https://composio.dev/toolkits/mem0/framework/open-ai-agents-sdk)
- [Claude Agent SDK](https://composio.dev/toolkits/mem0/framework/claude-agents-sdk)
- [Codex](https://composio.dev/toolkits/mem0/framework/codex)
- [Kimi Code](https://composio.dev/toolkits/mem0/framework/kimi)
- [Grok Build](https://composio.dev/toolkits/mem0/framework/grok-build)
- [VS Code](https://composio.dev/toolkits/mem0/framework/vscode)
- [OpenCode](https://composio.dev/toolkits/mem0/framework/opencode)
- [OpenClaw](https://composio.dev/toolkits/mem0/framework/openclaw)
- [Hermes](https://composio.dev/toolkits/mem0/framework/hermes-agent)
- [Atomic Agent](https://composio.dev/toolkits/mem0/framework/atomic-agent)
- [CLI](https://composio.dev/toolkits/mem0/framework/cli)
- [Google ADK](https://composio.dev/toolkits/mem0/framework/google-adk)
- [LangChain](https://composio.dev/toolkits/mem0/framework/langchain)
- [Vercel AI SDK](https://composio.dev/toolkits/mem0/framework/ai-sdk)
- [Mastra AI](https://composio.dev/toolkits/mem0/framework/mastra-ai)
- [LlamaIndex](https://composio.dev/toolkits/mem0/framework/llama-index)
- [CrewAI](https://composio.dev/toolkits/mem0/framework/crew-ai)
- [Pydantic AI](https://composio.dev/toolkits/mem0/framework/pydantic-ai)
- [AutoGen](https://composio.dev/toolkits/mem0/framework/autogen)

## Related Toolkits

- [Google Sheets](https://composio.dev/toolkits/googlesheets) - Google Sheets is a cloud-based spreadsheet tool for real-time collaboration and data analysis. It lets teams work together from anywhere, updating information instantly.
- [Notion](https://composio.dev/toolkits/notion) - Notion is a collaborative workspace for notes, docs, wikis, and tasks. It streamlines team knowledge, project tracking, and workflow customization in one place.
- [Airtable](https://composio.dev/toolkits/airtable) - Airtable combines the flexibility of spreadsheets with the power of a database for easy project and data management. Teams use Airtable to organize, track, and collaborate with custom views and automations.
- [Asana](https://composio.dev/toolkits/asana) - Asana is a collaborative work management platform for teams to organize and track projects. It streamlines teamwork, boosts productivity, and keeps everyone aligned on goals.
- [Google Tasks](https://composio.dev/toolkits/googletasks) - Google Tasks is a to-do list and task management tool integrated into Gmail and Google Calendar. It helps you organize, track, and complete tasks across your Google ecosystem.
- [Linear](https://composio.dev/toolkits/linear) - Linear is a modern issue tracking and project planning tool for fast-moving teams. It helps streamline workflows, organize projects, and boost productivity.
- [Jira](https://composio.dev/toolkits/jira) - Jira is Atlassian’s platform for bug tracking, issue tracking, and agile project management. It helps teams organize work, prioritize tasks, and deliver projects efficiently.
- [Clickup](https://composio.dev/toolkits/clickup) - ClickUp is an all-in-one productivity platform for managing tasks, docs, goals, and team collaboration. It streamlines project workflows so teams can work smarter and stay organized in one place.
- [Monday](https://composio.dev/toolkits/monday) - Monday.com is a customizable work management platform for project planning and collaboration. It helps teams organize tasks, automate workflows, and track progress in real time.
- [Addressfinder](https://composio.dev/toolkits/addressfinder) - Addressfinder is a data quality platform for verifying addresses, emails, and phone numbers. It helps you ensure accurate customer and contact data every time.
- [Agiled](https://composio.dev/toolkits/agiled) - Agiled is an all-in-one business management platform for CRM, projects, and finance. It helps you streamline workflows, consolidate client data, and manage business processes in one place.
- [AirOps MCP](https://composio.dev/toolkits/airops_mcp) - AirOps MCP is AirOps' managed content platform exposing brand context, knowledge bases, and workflows. Use it to give agents brand-aware content, automate content workflows, and track Brand Kit edits.
- [Amazing Marvin](https://composio.dev/toolkits/amazing_marvin) - Amazing Marvin is a personal productivity app for tasks, projects, habits, planning, time tracking, and rewards. It helps you build a flexible workflow that matches how you actually work.
- [ApptiveGrid](https://composio.dev/toolkits/apptivegrid) - ApptiveGrid is a collaborative no-code database and app platform for spaces, grids, forms, and structured records. It helps teams organize operational data, collect inputs, and build lightweight business apps without custom backend work.
- [Ascora](https://composio.dev/toolkits/ascora) - Ascora is a cloud-based field service management platform for service businesses. It streamlines scheduling, invoicing, and customer operations in one place.
- [Basecamp](https://composio.dev/toolkits/basecamp) - Basecamp is a project management and team collaboration tool by 37signals. It helps teams organize tasks, share files, and communicate efficiently in one place.
- [Boxhero](https://composio.dev/toolkits/boxhero) - Boxhero is a cloud-based inventory management platform for SMBs, offering real-time updates, barcode scanning, and team collaboration. It helps businesses streamline stock tracking and analytics for smarter inventory decisions.
- [Breathe HR](https://composio.dev/toolkits/breathehr) - Breathe HR is cloud-based HR software for SMEs to manage employee data, absences, and performance. It simplifies HR admin, making it easy to keep employee records accurate and up to date.
- [Breeze](https://composio.dev/toolkits/breeze) - Breeze is a project management platform designed to help teams plan, track, and collaborate on projects. It streamlines workflows and keeps everyone on the same page.
- [Bugherd](https://composio.dev/toolkits/bugherd) - Bugherd is a visual feedback and bug tracking tool for websites. It helps teams and clients report website issues directly on live sites for faster fixes.

## Frequently Asked Questions

### Does Muse support MCP?

Yes. Muse supports custom connectors that use the Model Context Protocol (MCP). Composio connects as one custom connector over remote streamable HTTP at https://connect.composio.dev/mcp, and gives Muse access to Mem0 and 1,500+ other apps.

### Where do I get the API key for the Composio connector?

Copy it from the Composio dashboard. It starts with ck_. Enter it only in Muse's secure credentials store, never in the chat.

### Can I connect more than one Mem0 account to Muse?

Yes. Composio supports multiple connected accounts for the same app. Give each Mem0 connection a name, such as work or personal, and tell Muse which one to use.

### How safe is my Mem0 data with Composio?

Tokens, keys, and configuration are encrypted at rest and in transit. Your Composio API key stays in Muse's secure credentials store, not in the chat or the model context. Composio is SOC 2 Type 2 compliant.

---
[See all toolkits](https://composio.dev/toolkits) · [Composio docs](https://docs.composio.dev/llms.txt)