IntegrationsMemory MCP Server

Use Zep in Claude, ChatGPT, Cursor, and other clients

Connect supported MCP clients to the Zep Memory MCP Server

The Zep Memory MCP Server lets people use their Zep agent memory from an MCP client. Each person signs in with a work email and reaches their own user graph in the selected Zep project.

Use the same endpoint for supported clients on Zep managed cloud:

https://api.getzep.com/mcp

BYOC deployments use the /mcp path on their own API host.

Configure the project

An administrator must configure and enable one Memory MCP connection for the Zep project.

1

Configure authentication

Follow Configuring authentication to connect Google Workspace or a custom OIDC provider, configure admission, select the authorization mode, and control write access.

2

Enable the connection

Enable the project connection after you have tested its identity-provider and policy settings. Member OAuth will fail while the connection is disabled.

3

Share the endpoint

Give members the Zep Memory MCP Server endpoint and the client connection steps. Each member must connect with their own work identity.

Client requirements

The client must support a remote MCP server over Streamable HTTP and OAuth 2.1 with PKCE. The client authenticates against Zep. Zep sends the user to the organization’s identity provider, so the MCP client is not registered as an OAuth application on that identity provider.

Claude, ChatGPT, Claude Code, Codex, Cursor, and other clients can work with this flow when they support these protocol requirements. Product plans and configuration surfaces are controlled by each client vendor.

Connection flow

  1. The member adds the remote Memory MCP Server endpoint.
  2. The client opens the Zep sign-in flow.
  3. The member enters a work email and signs in with the organization’s identity provider.
  4. The member selects a Zep project when more than one eligible project exists.
  5. The member approves the requested read and write access.

The selected project is fixed in the signed token. The member must reconnect to select a different project.

Access and governance

The user-graph tools operate on the signed-in member’s user graph. When the project enables shared graph access, the configured authorization mode determines which shared Context Graphs the member can retrieve or update.

See: