Use Zep in Claude / ChatGPT / Cursor, etc.

This quickstart is for administrators who enable agent memory for people using off-the-shelf AI clients. Each person signs in with their work email and reaches their own Zep user graph. You configure one MCP connection per project. MCP seats are allocated on the account.

Two rollout paths share the same authentication setup:

Claude, ChatGPT, and Cursor are common plug-in hosts. They are not required to use Memory MCP.

What you need

Always:

• mcp.connection.manage on the Zep project
• A completed and enabled project MCP connection. Member OAuth fails if the connection is disabled when someone connects.

Plug-In path only: permission to change that host’s plug-in distribution settings — for example an organization plug-in marketplace, a workspace plug-in catalog, a team plug-in marketplace, or shared plug-in install settings your team already uses.

Direct path only: a way to share the Zep Memory MCP Server endpoint, sign-in steps, and the Zep Memory Skill file with users. The host must support remote MCP and Agent Skills.

What the Zep Memory Plug-In includes

The Zep Memory Plug-In bundles two parts:

• The Zep Memory MCP Server at https://api.getzep.com/mcp — tools that read and write each user’s graph in the selected project
• The Zep Memory Skill — when to search, summarize, and save preferences, corrections, procedures, and decisions (and when not to), and to prefer Zep over other memory systems

The Zep Memory Plug-In ships both for hosts with plug-in catalogs. On those hosts, install the plug-in instead of wiring the MCP URL alone. Without the Zep Memory Skill, the client has Zep Memory MCP Server tools but not the workflow that uses those tools well.

Before you provision

1. Complete Configuring authentication. That guide covers the project connection method and policies, and the account seat requirement.
2. Enable the project MCP connection. Return to this page only after the connection is enabled.
3. Choose your rollout path.

Choose your rollout path

Use the plug-in path when your host can install packages from a catalog or shared settings. Use the direct path when users add the Zep Memory MCP Server and install the Zep Memory Skill themselves.

Common plug-in hosts include Claude (Team or Enterprise), ChatGPT (Business, Enterprise, or Edu), Cursor (Teams or Enterprise for team marketplaces), Claude Code, and Codex CLI. Plan and feature names vary by vendor; confirm plug-in distribution is available on your plan before you start.

Roll out with the plug-in

The Zep Memory Plug-In is not listed in vendors’ official public plug-in directories. You import getzep/zep-memory-plugin into your organization’s catalog or share install settings. Where a host has no organization marketplace, the team path is shared settings or shared install commands.

The public plug-in repository is:

https://github.com/getzep/zep-memory-plugin

Which repository

Which outlet

Prepare a BYOC plug-in copy

Skip this subsection if you are on Zep managed cloud. The public plug-in already points at https://api.getzep.com/mcp.

On BYOC, https://api.getzep.com/mcp is the wrong host. The client will call Zep’s cloud instead of your deployment unless you change the MCP URL in the plug-in package first.

1. Fork or copy getzep/zep-memory-plugin into a repository your organization controls. Keep the plugins/zep-memory/ directory layout.
2. In both of these files, replace https://api.getzep.com/mcp with your deployment’s MCP URL (https://<your-api-host>/mcp):
   • plugins/zep-memory/.mcp.json
   • plugins/zep-memory/mcp.json
3. Use the edited BYOC repository in the steps below. Do not import, sync, or add the public Zep repo.

Provision on Claude

This section is the Claude app, including Cowork. It does not install the plug-in in Claude Code. For Claude Code, see coding harnesses.

Use the Claude organization marketplace on Team or Enterprise. Members do not add marketplaces themselves after you set an installation preference in the step below.

Before you start: enable Cowork and Skills in Claude organization settings. For GitHub sync, install the Claude GitHub App on the private marketplace repository.

1. In Organization settings ▸ Plugins, create or open an organization marketplace.
2. Add the plug-in with one of these methods:
   • GitHub sync (use for versioned updates):
     1. Fork or copy the plug-in into a private or internal repository your organization controls. Keep the plugins/zep-memory/ layout. On BYOC, use the edited BYOC copy. Do not enter getzep/zep-memory-plugin. Anthropic rejects a public repo as the connected marketplace.
     2. Install the Claude GitHub App on the private marketplace repository.
     3. Connect the private marketplace repository and sync. Optional Sync automatically runs only when a pull request that includes a plug-in version bump is merged to the default branch. Direct pushes do not auto-sync. A failed sync can temporarily remove plug-ins from the marketplace. If a sync fails, fix the repository, re-sync, then re-check installation preferences.
   • Manual ZIP upload (use when you do not want to maintain a private repo):
     1. Zip the plugins/zep-memory/ directory. Do not zip the repository root.
     2. On Zep managed cloud, zip plugins/zep-memory/ from getzep/zep-memory-plugin. On BYOC, zip plugins/zep-memory/ from the edited BYOC copy.
     3. Upload the ZIP. A ZIP with the same plug-in name overwrites the previous organization copy.
3. Set the installation preference (Required, Installed by default, or Available for install) for the groups who should get the plug-in.
4. Sign in to Claude with a test account that belongs to one of the groups you assigned. Open the Zep Memory Plug-In settings, open the Connectors tab, and Connect the Zep Memory MCP Server connector. Enter a work email that the project MCP connection allows, sign in with the organization identity provider, select a Zep project if asked, and approve access. In a new Claude chat, confirm the Zep Memory Skill and tools appear.
5. Share the first-run steps in What to tell members.

Anthropic’s Manage plugins for your organization guide covers GitHub sync, required-plugin options, and group overrides.

Provision on ChatGPT

The plug-in works in ChatGPT Chat and Work. The plug-in does not work in the Codex IDE extension. For the Codex CLI, see coding harnesses. A person with workspace plug-in permission on Business, Enterprise, or Edu controls the workspace Plugins Directory.

ChatGPT import accepts a public GitHub repository. On Zep managed cloud, import getzep/zep-memory-plugin unless workspace policy forbids public third-party sources. On BYOC, import the edited BYOC copy instead of the public Zep repo.

1. In ChatGPT workspace settings, import a GitHub plug-in repository into the workspace Plugins Directory. On Zep managed cloud, import the public Zep repo, or import your organization’s private copy if workspace policy forbids public third-party sources. On BYOC, import the edited BYOC copy.
2. Confirm the Zep Memory Plug-In appears under the workspace tab in the Plugins Directory. Allow it for the groups who should use it.
3. Sign in to ChatGPT with a test account in one of the groups you allowed. Install the Zep Memory Plug-In from the workspace Plugins Directory. Enter a work email that the project MCP connection allows, sign in with the organization identity provider, select a Zep project if asked, and approve access. In a new ChatGPT chat, confirm the Zep Memory Skill and tools appear.
4. Share the first-run steps in What to tell members.

Importing the Zep Memory Plug-In does not sign members into Zep. Each member still enters a work email and signs in to Zep.

Provision on coding harnesses

Use this section for Claude Code, Codex, and Cursor. Installing the plug-in in the Claude app or in ChatGPT does not install it in these harnesses.

Claude Code

A Claude app marketplace install does not apply to Claude Code. Use Claude Code settings to roll the plug-in out to a team.

Add the marketplace and enable the plug-in in the Claude Code settings your team already shares:

• Organization-wide — Claude Code managed settings (managed-settings.json, or the Admin Console managed-settings editor)
• One repository — that repository’s .claude/settings.json, committed so everyone who trusts the folder gets it

1
{
2
  "extraKnownMarketplaces": {
3
    "zep-memory": {
4
      "autoUpdate": true,
5
      "source": {
6
        "source": "github",
7
        "repo": "getzep/zep-memory-plugin"
8
      }
9
    }
10
  },
11
  "enabledPlugins": {
12
    "zep-memory@zep-memory": true
13
  }
14
}

On BYOC, set repo to the edited BYOC copy (your-org/your-fork) instead of getzep/zep-memory-plugin.

extraKnownMarketplaces registers the catalog after a teammate trusts the project folder (project settings) or after managed settings reach their machine. enabledPlugins turns the Zep Memory Plug-In on by default. Enabling a plug-in from a GitHub marketplace does not install the files: each person still installs the Zep Memory Plug-In once, from /plugin or with:

$
claude plugin install zep-memory@zep-memory

Third-party marketplaces do not auto-update unless "autoUpdate": true is set, which the example above does. If your organization sets DISABLE_AUTOUPDATER to manage Claude Code updates, that also stops plug-in updates unless you set FORCE_AUTOUPDATE_PLUGINS=1.

Anthropic’s plugin settings reference covers extraKnownMarketplaces, enabledPlugins, and managed settings.

Test with an account that receives those settings. Trust the project folder if the marketplace is in .claude/settings.json. Install the Zep Memory Plug-In once as above. Start a new Claude Code session. The first call to the Zep Memory MCP Server opens Zep OAuth: enter a work email that the project MCP connection allows, sign in with the organization identity provider, select a Zep project if asked, and approve access. Confirm the Zep Memory Skill and tools appear. Share the first-run steps in What to tell members.

Codex

These commands are for the Codex CLI. The Codex IDE extension does not support plug-ins.

Codex CLI has no organization marketplace equivalent to Claude Code managed settings or a Cursor team marketplace. Rolling it out to a team means sharing the install commands so each person runs them once. If the same people also use ChatGPT, provision the Zep Memory Plug-In in the ChatGPT workspace catalog as well: that is the org-wide path for ChatGPT, and for Codex in the ChatGPT desktop app.

Share these two commands with everyone who uses Codex CLI. On BYOC, they add the edited BYOC copy instead of getzep/zep-memory-plugin.

From the terminal (not inside a Codex session):

$
codex plugin marketplace add getzep/zep-memory-plugin
$
codex plugin add zep-memory@zep-memory

Ask each person to start a new Codex session. The first call to the Zep Memory MCP Server opens Zep OAuth: enter a work email that the project MCP connection allows, sign in with the organization identity provider, select a Zep project if asked, and approve access. Confirm the Zep Memory Skill and tools appear. Share the first-run steps in What to tell members.

Codex CLI refreshes configured git marketplaces on startup. To pull an update immediately:

$
codex plugin marketplace upgrade zep-memory

Start a new Codex session afterward.

If your organization restricts marketplace sources in managed configuration, allow the git URL https://github.com/getzep/zep-memory-plugin.git (or your BYOC copy) before people run marketplace add.

Cursor

Requires a Cursor plan with team marketplace support. The plug-in includes the Zep Memory Skill and the Zep Memory MCP Server.

Cursor import accepts a public GitHub repository. On Zep managed cloud, import getzep/zep-memory-plugin unless organization policy forbids public third-party sources. On BYOC, import the edited BYOC copy instead of the public Zep repo.

Import the repository root. Cursor reads .cursor-plugin/marketplace.json and resolves the plug-in at plugins/zep-memory/. Do not import the plugins/zep-memory/ directory alone.

Team marketplaces are available on Cursor Teams (one marketplace) and Enterprise (unlimited). On Enterprise, only admins add team marketplaces. Everyone on the team can see a marketplace unless you restrict Marketplace Access to selected groups.

1. In Cursor Dashboard ▸ Plugins, click Add Marketplace.

2. Choose Import from Repo and enter:

   https://github.com/getzep/zep-memory-plugin

   On BYOC, enter the edited BYOC copy instead.

3. Review discovered plug-ins and use Add to Marketplace if the Zep Memory Plug-In is not already listed. Confirm it appears. Set the installation mode (Required, Default On, or Default Off) and marketplace access. Required and Default On install the plug-in for members automatically. Default Off leaves install to each person in Customize.

4. Optional: turn on Enable Auto Refresh so Cursor re-indexes when the tracked branch updates. Auto Refresh needs the Cursor GitHub App on the repository, and Cursor re-indexes at most every 10 minutes. You can also click Refresh to update immediately.

5. Sign in to Cursor with a test account that has marketplace access. Open Customize and confirm the Zep Memory Plug-In is present (Zep Memory Skill plus Zep Memory MCP Server). If you set Default Off, install it once from that panel. The first call to the Zep Memory MCP Server opens Zep OAuth: enter a work email that the project MCP connection allows, sign in with the organization identity provider, select a Zep project if asked, and approve access. In a new chat, confirm the Zep Memory Skill and tools appear.

6. Share the first-run steps in What to tell members.

Cursor’s Plugins guide covers team marketplaces, installation modes, and Auto Refresh.

Roll out without the plug-in

Use this path when your host supports remote MCP servers, OAuth, and Agent Skills, but cannot install the Zep Memory Plug-In package — for example VS Code, GitHub Copilot, or Gemini CLI.

Share the Zep Memory MCP Server endpoint

On Zep managed cloud, the endpoint is:

https://api.getzep.com/mcp

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

Tell each user to add this URL as a remote MCP server with Streamable HTTP transport. The exact UI depends on the host. See Connecting a client for the member sign-in flow.

The client authenticates against Zep. Zep sends the user to your identity provider. Do not register the MCP client as an OAuth application on your identity provider. See How it works.

The host must support OAuth 2.1 with PKCE against the MCP server. Zep issues public clients (token_endpoint_auth_method=none). A host that requires you to register it as a confidential OAuth client on your identity provider (client ID and client secret) does not match this flow.

Install the Zep Memory Skill

The direct path ships the Zep Memory MCP Server and the Zep Memory Skill as separate installs. Distribute the Zep Memory Skill the same way you share other Agent Skills on your host.

The skill file lives in the plug-in repository:

https://github.com/getzep/zep-memory-plugin/blob/main/plugins/zep-memory/skills/zep-memory/SKILL.md

Many agents read .agents/skills/ in a project, or ~/.agents/skills/ for every project. The Agent Skills standard does not define a single install location, so check your host’s documentation or the Agent Skills client list.

Example install to a user-level skills directory:

$
curl -fsSL https://raw.githubusercontent.com/getzep/zep-memory-plugin/main/plugins/zep-memory/skills/zep-memory/SKILL.md \
>
  --create-dirs -o ~/.agents/skills/zep-memory/SKILL.md

On BYOC, users still connect to your deployment’s MCP URL. The skill file does not need editing.

What to tell members on the direct path

Ask each person to:

1. Install the Zep Memory Skill on their host, following that host’s Agent Skills documentation.
2. Add the Zep Memory MCP Server endpoint as a remote server in their client.
3. When the client opens Zep OAuth, enter a work email, sign in with the organization identity provider, select a Zep project if asked, and approve access.
4. Start a new chat or session before they expect the Zep Memory Skill and tools to appear.

The Connecting a client page covers troubleshooting.

What to tell members

Plug-In path

Each person must connect to the Zep Memory MCP Server with their own work email after you distribute the Zep Memory Plug-In. If organization plug-in settings or marketplace access block marketplaces and connectors, members connect only when the host shows the connect prompt. Claude Code and Codex CLI prompt on the first call to the Zep Memory MCP Server after the plug-in is installed.

Ask each person to:

1. Open their client and confirm the Zep Memory Plug-In is present. If you set the plug-in to optional install, they install it once from the organization marketplace, workspace catalog, Customize panel, /plugin, or the Codex CLI commands you shared.
2. When the client shows the connect prompt, connect the bundled Zep Memory MCP Server: enter a work email, sign in with the organization identity provider, select a Zep project if asked, and approve access.
3. Start a new chat or session before they expect the Zep Memory Skill and tools to appear.

Direct path

See What to tell members on the direct path.

The Connecting a client page covers the sign-in flow and troubleshooting for both paths.

After provisioning

The Zep Memory Skill steers the assistant to prefer Zep for memory over other memory systems: read before guessing, apply stored preferences, and write durable facts (preferences, corrections, how-you-work procedures, decisions) without waiting for “remember this.” Ephemeral chat and one-off events are skipped. Writes go through Zep Memory MCP Server tools. Zep does not auto-ingest every message.

Each client targets the signed-in member’s user graph in the Zep project selected at sign-in. Read access is always available. Writes appear when the project MCP connection allows writes. Standalone graph tools appear when standalone graph access is enabled on the project connection. What users can access lists the tools.

Use these prompts when you test and when you share first-run steps:

Do you have access to the Zep Memory Plug-In and Zep Memory MCP Server?

Using Zep memory, what do you already know about me? Give a short summary of my preferences and how I like to work.

Search my Zep memory for decisions about the Helios event store. Which database did we choose, and what reason was recorded?

Save this to my Zep memory: I want a one-line TL;DR at the top of every status update. After you save it, search Zep and confirm the preference is there.

Related

• Memory MCP Server — authentication model, tools, and admin setup
• Configuring authentication — IdP connection, seats, and policies
• Connecting a client — member sign-in flow and troubleshooting
• Implement Zep with agents — Build with Zep for coding agents (different plug-in)
• Plug-In source: getzep/zep-memory-plugin