Zep Context

Knowledge-work plugin for Claude Desktop Chat, Claude Cowork, ChatGPT Work, and Cursor. Not positioned for Claude Code, Codex, or other coding-agent CLIs.

Bundles:

• The zep-context skill — how to use Zep for user context, threads, and standalone graphs via LLM-mediated Context MCP tool calls
• The Zep Context MCP Server at https://api.getzep.com/mcp

Terms and privacy

Read these before installing or using this plugin. They are the terms of service and privacy policy for this plugin.

• Terms of Service
• Privacy Policy

The plugin files (skill, manifests, and MCP config) are also licensed under the Apache License 2.0.

This plugin connects the host to Zep’s Context MCP Server. You sign in with OAuth. After that, the assistant can search and add to your Zep context — your user graph, and standalone graphs when your project enables them. That API and context data is handled under the Privacy Policy above.

Usage

Once installed and signed in, ask the assistant to recall or save durable context. For example:

• What context do you have about me?
• Search my Zep context for this topic.
• Save this context to Zep.

The skill tells the assistant to look up stored context before guessing, and to write standing facts about who the user is, their work environment (people, projects, teams), preferences, corrections, procedures, decisions, and feedback without waiting to be asked. Standalone graphs hold project and company-wide knowledge; search those with list_graphs then search_graph_in when the project enables them.

Install and product docs: Context MCP Server.

Configuration

No API keys, plugin variables, or other secrets belong in this repository. Auth is client-managed OAuth against https://api.getzep.com/mcp.

The first Context MCP call should prompt for Zep sign-in (work email → identity provider → project). You need a Zep account whose project has Context MCP enabled.

Support

• Docs: Context MCP Server
• Issues: getzep/zep-context-plugin

Product intent

• Teach knowledge-work assistants to use Zep to get and save context about the user and the business
• LLM-written context via MCP tools is the v1 write path (hooks / auto-ingest of every message are out of scope)
• Internal rollout via Claude Team / Enterprise, ChatGPT workspace distribution, and Cursor local / team-marketplace install; public Cursor Marketplace listing is a separate Cursor review after submitting this repository
• Docs follow-up: install instructions on the Context MCP Server docs page

Packaging note

plugins/zep-context/ is the one plugin root (ChatGPT cannot install a marketplace source.path of "./"). That directory conforms to Agent Plugins 1.0.0: plugin.json identifies the portable package, skills/ contains the skill, and mcp.json declares the Context MCP Server using the standard streamable-http transport.

Cursor loads that Agent Plugins package as-is. Claude and OpenAI compatibility does not depend on either vendor adopting the standard. The same folder also holds .claude-plugin/, .codex-plugin/, and .mcp.json.

.codex-plugin/ is the ChatGPT Work package format. Keeping that manifest does not mean this plugin targets Codex as a coding product.

Repository and distribution

This repository is the catalog plus that one package. Marketplace entries point at ./plugins/zep-context (Claude and ChatGPT Work) or plugins/zep-context (Cursor, via pluginRoot).

claude plugin marketplace add getzep/zep-context-plugin
claude plugin install zep-context@zep-context

Upgrade from zep-memory

Existing installs do not update in place because the plugin and marketplace names changed. Remove the old plugin and marketplace, then add the new marketplace and install the new plugin:

claude plugin uninstall zep-memory@zep-memory

claude plugin marketplace remove zep-memory

claude plugin marketplace add getzep/zep-context-plugin

claude plugin install zep-context@zep-context

Cursor (local test)

Symlink the plugin root — not this repository root — into Cursor's local plugin directory, then reload:

mkdir -p ~/.cursor/plugins/local
ln -s /absolute/path/to/zep-context-plugin/plugins/zep-context ~/.cursor/plugins/local/zep-context

Then in Cursor: Developer: Reload Window. Open Customize and confirm the zep-context skill and MCP server are present. The first Context MCP call should prompt for Zep OAuth (work email → IdP → project).

You can also import this GitHub repository as a Cursor team marketplace; .cursor-plugin/marketplace.json points at the same plugin root.

To list on the public Cursor Marketplace, submit this repository at cursor.com/marketplace/publish. Cursor reviews the listing and every later update; merging to GitHub does not publish by itself.

Releasing

Keep portable, Claude, and ChatGPT Work manifest versions synchronized with python3 scripts/plugin_manifests.py set <version>, validate, then open a PR. How that reaches users (Claude org marketplace, ChatGPT Work workspace share, Cursor team marketplace, public Cursor Marketplace) is documented under Releasing in AGENTS.md.