feat(building-with-zep): add Cursor as a third plugin ecosystem - #581
Merged
Conversation
There was a problem hiding this comment.
Findings
- Critical —
plugins/building-with-zep/.cursor-plugin/plugin.json:11: Cursor does not load MCP configuration inline fromplugin.json; it discovers it from a plugin-rootmcp.json. Consequently, installing this plugin will not installzep-docs, despite the README’s claim. Addplugins/building-with-zep/mcp.jsoncontaining themcpServersconfiguration and remove the unsupported inline field. The existing.mcp.jsoncan remain for Claude/Codex.
Adds a Cursor manifest (.cursor-plugin/plugin.json) and a repo-root Cursor marketplace (.cursor-plugin/marketplace.json) alongside the existing Claude and Codex manifests, so all three runtimes load the same single copy of the skills/building-with-zep tree with no per-ecosystem duplication. Cursor is the one exception to sharing .mcp.json: Cursor auto-discovers mcp.json without the leading dot, and its remote-server schema has no `type` key. Rather than rely on Cursor tolerating "type": "http", the Cursor manifest declares the zep-docs server inline with a bare url. Co-Authored-By: Claude <noreply@anthropic.com>
jackaldenryan
force-pushed
the
jack/create-pr-v1
branch
from
July 28, 2026 03:55
1f6354c to
ee0a31a
Compare
There was a problem hiding this comment.
Suggestion
plugins/building-with-zep/README.md, opening “It bundles two things” section: The README still sayszep-docsis “declared once in.mcp.json,” but this PR also declares it inline in the Cursor manifest. This contradicts the new explanation below and could cause maintainers to update only one endpoint. Revise it to state that Claude/Codex use.mcp.json, while Cursor declares the server inline.
No correctness, security, or packaging blockers found.
There was a problem hiding this comment.
Cursor Bugbot has reviewed your changes using high effort and found 1 potential issue.
❌ Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, enable autofix in the Cursor dashboard.
Reviewed by Cursor Bugbot for commit ee0a31a. Configure here.
Cursor's schema permits declaring mcpServers inline in plugin.json, but no official Cursor plugin does it -- every plugin that ships an MCP server uses a plugin-root mcp.json, and cursor/plugins@a65002e moved the Figma plugin onto that convention. Follow the pattern with a working precedent rather than the one that is merely permitted. Adds plugins/building-with-zep/mcp.json with a bare url (no `type` key, which Cursor documents for stdio servers only) and drops the inline mcpServers field from .cursor-plugin/plugin.json, letting Cursor auto-discover the file. .mcp.json is unchanged and still serves Claude Code and Codex with its `type: "http"` entry. The README now documents both files, why the duplication is deliberate, and that the two endpoints must be kept in sync -- resolving the earlier claim that zep-docs was "declared once in .mcp.json". Co-Authored-By: Claude <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Adds a Cursor manifest (
plugins/building-with-zep/.cursor-plugin/plugin.json) and a repo-root Cursor marketplace (.cursor-plugin/marketplace.json) alongside the existing Claude and Codex manifests, so all three runtimes load the same single copy of theskills/building-with-zep/tree with no duplication or sync step. Cursor is the one exception to sharing.mcp.json— it auto-discoversmcp.jsonwithout the leading dot and its remote-server schema has notypekey, so rather than rely on Cursor tolerating"type": "http", the Cursor manifest declares thezep-docsserver inline with a bareurl. The plugin README is updated to document the three-ecosystem layout, the Cursor install command (/add-plugin building-with-zep@https://github.com/getzep/zep, Cursor 2.5+), and local-dev symlinking.🤖 Generated with Claude Code
Note
Low Risk
Packaging and documentation only—no application runtime, auth, or data-path changes; main maintenance risk is keeping
.mcp.jsonandmcp.jsonURLs in sync.Overview
Extends
building-with-zepto Cursor while keeping one sharedskills/building-with-zep/tree. New repo-root.cursor-plugin/marketplace.jsonandplugins/building-with-zep/.cursor-plugin/plugin.jsonwire the plugin into Cursor’s marketplace/install flow.Adds plugin-root
mcp.json(bareurl, notype) for Cursor auto-discovery, alongside existing.mcp.jsonfor Claude/Codex. README now documents the three-ecosystem layout, why MCP is duplicated, Cursor 2.5+/add-plugin building-with-zep@https://github.com/getzep/zep, and local symlink dev.Reviewed by Cursor Bugbot for commit 50b0c9c. Bugbot is set up for automated code reviews on this repo. Configure here.