How to integrate Zep MCP with Grok Build

Connect Grok Build to Zep MCP. Store a memory about today's meeting, retrieve all memories tagged urgent, and more from your terminal, with authentication handled for you.

Zep logoZep
Api Key

Zep is a foundational memory layer for AI agents and apps. It lets your AI remember, recall, and organize key information over time.

43 Tools

How to integrate Zep 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 Zep account to Grok Build through Composio, so it can store a memory about today's meeting, retrieve all memories tagged urgent, summarize knowledge about client preferences, and more without leaving the terminal. Composio holds the OAuth tokens for you, and Grok Build only calls the tools you approve.

Also integrate Zep with

Why use Composio over a standalone MCP server?

  • Read and write access. Composio's Zep integration lets Grok Build take real actions like creating drafts, sending updates, and labeling records, not just reading data.
  • 1,000+ 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 Zep 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 Zep 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 Zep account through Composio. On the first Zep 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 Zep

  • Store a memory about today's meeting
  • Retrieve all memories tagged urgent
  • Summarize knowledge about client preferences

Security + privacy notes (important)

  • Use least-privilege access. Grant only the Zep 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 Zep action and event your agent gets out of the box.

Add Fact Triple

Tool to add a manually specified fact triple (subject-predicate-object) to the Zep knowledge graph.

Add Session Memory

Tool to add memory messages to a specified Zep session.

Add Thread Messages

Tool to add chat messages to a thread in Zep and ingest them into the user knowledge graph.

Clone Graph

Tool to clone a user or group graph with new identifiers in Zep.

Create Graph

Tool to create a new graph by adding data to Zep.

Create Group

Tool to create a new group in Zep for multi-user graph management.

Create Session

Tool to create a new session in Zep for storing conversation memory.

Create Thread

Tool to create a new thread in Zep for a specific user.

Create User

Tool to create a new user in Zep with properties like user_id, email, and metadata.

Delete Graph

Tool to delete a graph from Zep.

Delete Group

Tool to delete a group from Zep.

Delete Session Memory

Tool to delete a session and its memory from Zep.

Delete Thread

Tool to delete a thread and its messages from Zep.

Delete User

Tool to delete a user and all associated threads and artifacts from Zep.

Get Edge by UUID

Tool to retrieve a specific edge by its UUID from the Zep knowledge graph.

Get Graph by ID

Tool to retrieve a graph by its unique identifier from Zep.

Get Group by ID

Tool to retrieve a group by ID from Zep.

Get Node Entity Edges

Tool to retrieve all entity edges for a specific node in the Zep knowledge graph.

Get Project Info

Tool to retrieve project information based on the provided API key.

Get Session by ID

Tool to retrieve a session by its unique identifier from Zep.

Get Session Memory

Tool to retrieve memory for a given session including relevant facts and entities.

Get Session Message by UUID

Tool to retrieve a specific message by UUID from a Zep session.

Get Session Messages

Tool to retrieve messages for a given session from Zep.

Get Task Status

Tool to check the status of asynchronous operations in Zep.

Get Thread Messages

Tool to retrieve conversation history for a specific thread from Zep.

Get Thread User Context

Tool to retrieve the most relevant user context from the user graph based on thread messages.

Get User by ID

Tool to retrieve a user by their user ID from Zep.

Get User Node

Tool to retrieve a user's graph node and summary from Zep.

Get User Nodes

Tool to retrieve all nodes for a specific user from their graph in Zep.

Get User Sessions

Tool to retrieve all sessions for a user from Zep.

Get User Threads

Tool to retrieve all threads for a specific user from Zep.

Graph Search

Tool to perform hybrid graph search combining semantic similarity and BM25 full-text search across the Zep knowledge graph.

List Graphs

Tool to retrieve all graphs from Zep with pagination support.

List Groups Ordered

Tool to retrieve all groups from Zep with pagination support.

List Sessions Ordered

Tool to retrieve all sessions from Zep with pagination and ordering support.

List Threads

Tool to retrieve all threads from Zep with pagination support.

List Users Ordered

Tool to retrieve all users from Zep with pagination support.

List All Threads

Tool to list all threads with pagination and ordering support.

Update Graph

Tool to update graph information in Zep including name and description.

Update Group

Tool to update group information in Zep including name, description, and fact rating instructions.

Update Message

Tool to update a message in a Zep thread.

Update Session Metadata

Tool to update session metadata in Zep.

Update User

Tool to update an existing user's information in Zep including email, metadata, and ontology settings.

FAQ

Frequently asked questions

A standalone Zep MCP server gives Grok Build a fixed set of Zep tools tied to that one server. The Composio Tool Router lets Grok Build load tools from Zep and many other apps on demand, based on the task, all through a single endpoint.

Yes. Grok Build ships with native MCP support. Add a server with the grok mcp add command, from the in-session /mcps modal, or by editing ~/.grok/config.toml. It also reads Claude Code-style .mcp.json files, so Grok Build discovers the tools automatically.

Yes. Grok Build has zero-migration compatibility with Claude Code's configuration, so the same Composio server entry works in both without edits.

Tokens, keys, and configuration are encrypted at rest and in transit. Composio is SOC 2 Type 2 compliant, so your Zep data and credentials are handled to that standard.

Start with Zep.It takes 30 seconds.

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

Start building