> For clean Markdown of any page, append .md to the page URL.
> For a complete documentation index, see https://docs-beta.getzep.com/llms.txt.
> For AI client integration (Claude Code, Cursor, etc.), connect to the MCP server at https://docs-beta.getzep.com/_mcp/server.

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

> Configure the Context MCP Server and connect remote MCP clients through Zep OAuth.

The Zep Context 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:

```text
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 Context MCP connection for the
Zep project.

#### Configure authentication

Follow [Configuring authentication](/context-mcp-server/authentication) to
connect Google Workspace or a custom OIDC provider, configure admission,
select the authorization mode, and control write access.

#### 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.

#### Share the endpoint

Give members the Zep Context MCP Server endpoint and the
[client connection steps](/context-mcp-server/connect). 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 Context 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:

* [Context MCP Server overview](/context-mcp-server)
* [Configuring authentication](/context-mcp-server/authentication)
* [Connecting a client](/context-mcp-server/connect)
* [Shared Context Graph authorization](/context-mcp-server/standalone-graph-authorization)