How to integrate Mem0 MCP with Hermes

Hermes is a 24/7 autonomous agent that lives on your computer or server — it remembers what it learns and evolves as your usage grows. This guide explains the easiest and most robust way to connect your Mem0 account to Hermes. You can do this through either Composio Connect CLI or Composio Connect MCP. For personal use we recommend the CLI, but you won't go wrong with MCP either.

Mem0 logoMem0
Api Key

Mem0 is an AI-powered note-taking and knowledge management platform. It helps you organize, search, and generate content from your personal knowledge base.

47 Tools

Introduction

Hermes is a 24/7 autonomous agent that lives on your computer or server — it remembers what it learns and evolves as your usage grows.

This guide explains the easiest and most robust way to connect your Mem0 account to Hermes. You can do this through either Composio Connect CLI or Composio Connect MCP. For personal use we recommend the CLI, but you won't go wrong with MCP either.

Also integrate Mem0 with

What is Composio Connect?

Composio Connect is a consumer offering that lets anyone plug 1,000+ applications directly into their agent harness — including Hermes. It can:

  • Search and load tools from relevant toolkits on-demand, reducing context usage.
  • Chain multiple tools to accomplish complex workflows via a remote workbench, without excessive back-and-forth with the LLM.
  • Manage app authentication end-to-end with zero manual overhead.

Integrating Mem0 with Hermes

Using Composio Connect CLI

1. Install the Composio CLI

Run the install script directly, or paste https://composio.dev/hermes into your Hermes chat box to have it installed for you.

bash
curl -fsSL https://composio.dev/install | bash
Hermes authenticating with Composio

2. Authenticate

Once the CLI is installed, ask Hermes to authenticate with Composio.

3. Connect to Mem0

Ask your agent to connect to Mem0, or simply request any Mem0-related task. Hermes will prompt you to authenticate and authorize access.

4. Done. You're all set with a new Mem0 connection.


Using Composio Connect MCP

1. Get your MCP URL and API Key

Go to dashboard.composio.dev and copy your Connect MCP URL and API key.

Copy MCP URL and API key from Composio dashboard

2. Open the Hermes config file

bash
nano ~/.hermes/config.yaml

3. Add the Composio Connect MCP server

bash
mcp_servers:
  composio:
    url: "https://connect.composio.dev/mcp"
    headers:
      x-consumer-api-key: "YOUR_COMPOSIO_API_KEY"
    connect_timeout: 60
    timeout: 180

Save with Ctrl + O, Enter, then exit with Ctrl + X.

4. Restart your Hermes agent

Once restarted, ask your agent to connect to Mem0 or request any Mem0-related task. It will prompt you to authenticate and authorize access.

5. Done!

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.

Way Forward

With Mem0 connected, Hermes can now act on your behalf whenever it detects a relevant task or you ask it to.

From here, you can extend Hermes further:

  • Connect more apps: Calendar, Slack, Notion, Linear, and hundreds of others are available through the same Composio Connect setup. Each new integration compounds what Hermes can do for you.
  • Build workflows across tools: Once multiple apps are connected, Hermes can chain actions together — turn an email into a calendar invite, a Slack message into a Linear ticket, or a meeting note into a follow-up draft.
  • Let it learn your patterns: The more you use Hermes, the better it gets at anticipating how you'd handle recurring tasks. Give it feedback on drafts and decisions, and it will adapt.

If you run into trouble or want to share what you've built, join the community or check out the Docs for deeper configuration options.

TOOLS

Supported Tools

Every Mem0 action and event your agent gets out of the box.

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.

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.

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

Tool to 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.

Get projects

Retrieves all projects for a given organization `org_id` to which the caller has access.

Get project webhooks

Retrieves all webhooks configured for a specific project.

Get user memory stats

Retrieves a summary of the authenticated user's memory activity, including total memories created, search events, and add events.

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.

Perform semantic search on memories

Searches memories semantically using a natural language query and metadata filters.

Remove a member from the organization

Removes 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 user

Retrieves a paginated list of events for the authenticated user, filterable and paginable via URL query parameters.

Retrieve list of memory events

Retrieves a chronological list of all memory events (e.

Retrieve memory by id

Retrieves a complete memory entry by its unique identifier; `memory_id` must be valid and for an existing memory.

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.

Retrieve memory list

Retrieves a list of memories, supporting pagination and diverse filtering (e.

Search memories with filters

Semantically searches memories using structured filters with an optional natural language query.

Update memory batch with uuid

Updates text for up to 1000 memories in a single batch, using their UUIDs.

Update memory text content

Updates the text content of an existing memory, identified by its `memory_id`.

Update organization member role

Updates the role of an existing member to a new valid role within an existing organization.

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.

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.

FAQ

Frequently asked questions

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.

Yes, you can. Hermes 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.

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.

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.

Start with Mem0.It takes 30 seconds.

Managed auth, hosted MCP servers, and every Mem0 tool your agent needs.Free to start.

Start building