How to integrate Mem0 MCP with Grok Build

Connect Grok Build to Mem0 MCP. Store meeting notes from today's call, export all project memories as csv, and more from your terminal, with authentication handled for you.

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

How to integrate Mem0 MCP with Grok Build

Grok Build is xAI's terminal coding agent. It runs on Grok 4.5, plans its work before it acts, and can run multiple sub-agents in parallel. It also reads Claude Code's MCP configuration, so any server you already have in a .mcp.json is picked up with no changes.

In this guide, I will show you how to connect your Mem0 account to Grok Build through Composio, so it can store meeting notes from today's call, export all project memories as CSV, add new user to our team space, and more without leaving the terminal. Composio holds the OAuth tokens for you, and Grok Build only calls the tools you approve.

For exact tool slugs and parameter tables, see the tool catalog in the Composio docs.

Also integrate Mem0 with

Why use Composio over a standalone MCP server?

  • Read and write access. Composio's Mem0 integration lets Grok Build take real actions like creating drafts, sending updates, and labeling records, not just reading data.
  • 1,700+ SaaS toolkits out of the box. One endpoint gives you a full catalog of pre-built connectors, from Gmail and Slack to Notion, Linear, and Salesforce.
  • One MCP server for every app. Wire up a single Composio server instead of maintaining a separate MCP entry for each app.
  • Smart, context-aware tool loading. Grok Build caps how many tools it holds in a single request. Composio loads only the tools a task needs, so you do not spend that budget on tools you are not using.
  • Cross-app automation. Chain actions across apps in one run. Pull a thread, summarize it in Notion, and post the highlights to Slack from a single prompt.

Prerequisites

  • Grok Build installed and signed in. Install with curl -fsSL https://x.ai/cli/install.sh | bash on macOS or Linux, or irm https://x.ai/cli/install.ps1 | iex on Windows PowerShell. On first launch Grok opens a browser to authenticate; for headless or CI use, set an XAI_API_KEY environment variable instead (create the key at console.x.ai).
  • Access to the Mem0 account you want to connect.
  • The Composio MCP endpoint. Composio's server is remote and hosted, so there is nothing to run locally and no tunnel to set up.

Step-by-step: Connect Mem0 to Grok Build

1. Install and verify Grok Build

Install the CLI, then restart your shell so the grok binary lands on your PATH:

bash
curl -fsSL https://x.ai/cli/install.sh | bash
which grok

On Windows, install with PowerShell instead: irm https://x.ai/cli/install.ps1 | iex. If which grok returns a path, you are set. Grok Build runs on Grok 4.5 by default; you can switch models inside the session with /model <name>.

2. Add the Composio server

Add Composio as a remote HTTP MCP server with the grok mcp add command:

bash
grok mcp add --transport http composio https://connect.composio.dev/mcp

You can also add and manage servers from inside a session. Run /mcps to open the extensions modal on the MCP tab, then add a new server and paste the Composio URL. Added this way, Grok auto-detects the name from the URL and lists the server as connect:

bash
https://connect.composio.dev/mcp
Grok Build /mcps extensions modal listing MCP servers Grok Build adding the Composio MCP server with its URL

Grok also reads Claude Code-style config, so an entry in ~/.grok/config.toml or a project .mcp.json works the same way.

3. Authenticate

Composio uses OAuth. In the /mcps modal, select the Composio server and press i to authenticate (Grok also triggers this browser flow automatically the first time it uses a Composio tool). Click Allow to authorize access. Grok stores the tokens under ~/.grok/mcp_credentials.json, and /mcps shows Composio as connected.

Grok Build prompting to authenticate the Composio MCP server Composio authorization screen with the Allow button for Grok Build

4. Start building

Ask Grok to work with your Mem0 account through Composio. On the first Mem0 action, Composio prompts you to connect the account through OAuth. Approve the scopes once, and Composio handles token refresh from there.

What you can do after connecting Mem0

  • Store meeting notes from today's call
  • Export all project memories as CSV
  • Add new user to our team space
  • Search recent notes mentioning quarterly goals

Security + privacy notes (important)

  • Use least-privilege access. Grant only the Mem0 scopes you actually need.
  • Review OAuth scopes before approving. Check that the requested scopes match what you expect Composio and Grok Build to do.
  • Keep write actions human-reviewed. Grok Build proposes a plan before it acts. Leave that approval step on for actions like sending messages or editing records.
  • Keep secrets out of version control. Your XAI_API_KEY and any tokens should never be committed. Use environment variables or a secrets manager.
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

Adds memory records from messages, optionally inferring structured content.

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 a required name; additional metadata may be assigned by the system.

Create a new agent run

Creates a new agent run in the mem0.ai system.

Create a new application

Creates a new application with an application ID and name; ensure the 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 optional metadata.

Create memory entry

Lists or searches existing memory entries using required nonempty filters and optional pagination.

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 memory export job requiring organization and project IDs and at least one user, agent, app or run filter.

List organizations

Retrieves a list of organizations with their details, including IDs, names, ownership, members and plan information.

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 entity filters from the entity filters endpoint, with a response modeled as a list of entities.

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

Retrieves memories associated with a specified user, agent, app, or run by entity type and ID, with optional pagination.

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 entities with optional organization and project filters; results may be summaries and subject to limits.

Perform semantic search on memories

Searches memories using a natural language query and optional filters, or requests metadata-only search.

Remove a member from the organization

Removes a member from an organization using the organization ID and member's email address.

Retrieve all events for the currently logged in user

Retrieves a paginated list of events for the authenticated user in a read-only operation.

Retrieve list of memory events

Retrieves memory events from the Mem0 platform, providing interaction history and context for AI assistants.

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 version history of a Mem0 memory by its ID, allowing you to inspect its evolution and audit changes.

Retrieve memory list

Retrieves a paginated list of memories filtered by IDs, metadata, keywords, dates, and other criteria.

Search memories with filters

Searches memories using a required nonempty set of structured filters and an optional natural language query, which defaults to '*'.

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 and/or metadata 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 within an organization using the provided name, description, custom instructions, or custom categories.

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

Start with Mem0.It takes 30 seconds.

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

Start building