How to connect Mem0 MCP with VS Code

Trusted by teams at
AWS
Glean
Zoom
Airtable

30 min · no commitment · see it on your stack

Mem0 logo
VS Code logo
divider

How to connect Mem0 MCP with VS Code

VS Code is the most popular code editor out there. With its recent AI makeover, it can do more than just help you write code. You can connect your applications to it and let LLMs automate many of the mundane tasks in your workflow.

In this guide, I will explain how to connect Mem0 with VS Code in the most secure and robust way possible via Composio.

Also integrate Mem0 with

Why use Composio?

Composio provides:

  • Access to 1,000+ managed apps from a single MCP endpoint. This makes it convenient for agents to run cross-app workflows.
  • Programmatic tool calling. Allows LLMs to write its code in a remote workbench to handle complex tool chaining. Reduces to-and-fro with LLMs for frequent tool calling.
  • Large tool response handling outside the LLM context. This minimizes context bloat from large tool responses.
  • Dynamic just-in-time access to thousands of tools across hundreds of apps. Composio loads the tools your agent needs, so LLMs are not overwhelmed by tools they do not need.

Integrate Mem0 MCP with VS Code

1. Install with one click

Click the button below to add Composio to VS Code. You will be prompted to authorize. This requires VS Code 1.99+ with GitHub Copilot.

+Install in VS Code

2. Or add manually

Open or create .vscode/mcp.json in your project root and add the following configuration:

bash
{
  "servers": {
    "composio": {
      "type": "http",
      "url": "https://connect.composio.dev/mcp"
    }
  }
}

3. Authorize

Click the install button to authorize VS Code to connect to Composio. VS Code will detect OAuth and prompt you to sign in.

VS Code MCP server install screen for Composio

A browser window will open to authorize.

Composio authorization browser window

4. Authenticate Mem0 and start working

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

For example, ask it 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 to Mem0.

That is it. Composio tools are now available in VS Code, and your Mem0 account is ready to use.

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 an export job with schemaInitiates an asynchronous job to export memories, structured by a schema provided in the request body and allowing optional filters.
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.
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 memories matching specified filter criteria; omitting all filters may result in deleting all memories.
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 username, from a project, immediately revoking their project-specific access; the user is not removed from the organization.
Export data based on filtersRetrieves memory export data, optionally filtered by various identifiers (e.
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 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 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 (required if `only metadata based search` is false) and/or 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 entity-specific memoriesRetrieves all memories (e.
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 a natural language query and mandatory structured filters, offering options to rerank results and select specific fields; any provided `org id` or `project id` must reference a valid existing entity.
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.

Way Forward

Now that Mem0 is connected, extend your setup by connecting the other apps you already use every day, so your agent 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.
  • Connect HubSpot or Salesforce to log customer context, update records, and draft follow-ups.

Start with one workflow you do repeatedly, then keep adding apps as you find new handoffs. With everything behind a single MCP endpoint, your agent can coordinate multiple tools safely and reliably in one conversation.

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 VS Code?

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