Editor and Agent Plugin Assets
Overview
This area packages Context7 for editor and agent plugin ecosystems. The files are distributable assets only: manifests, MCP server declarations, prompt instructions, skills, agents, commands, READMEs, licenses, and logos. They all point users or agents at Context7's hosted documentation service, whose common tools are resolve-library-id and query-docs, but each host has different manifest fields, component discovery paths, and authentication expectations.
Path routing for this doc is by plugin family:
plugins/cursor/context7/**is the Cursor marketplace package. plugins/…/plugin.json declares package metadata, component roots (skills,rules,agents), andmcpServers: ./mcp.json; plugins/…/mcp.json points thecontext7server athttps://mcp.context7.com/mcp/oauth. Cursor-specific behavior lives inplugins/cursor/context7/rules/use-context7.mdc(always-on rule), plugins/…/SKILL.md (library-doc lookup workflow, including optionalquery-codesource lookup), and plugins/…/docs-researcher.md (focused documentation researcher agent). The root marketplace index .cursor-plugin/marketplace.json publishes this package from./plugins/cursor/context7.plugins/claude/context7/**is the Claude Code plugin package. plugins/…/plugin.json contains the package metadata, while plugins/…/.mcp.json configures the hosted HTTP MCP server athttps://mcp.context7.com/mcp?client=claude-code-plugin. Its README documents Claude's browser sign-in via/mcpand explicitly says this plugin does not readCONTEXT7_API_KEY; headless/API-key setup is delegated tonpx ctx7 setup --claudeor manual MCP configuration. The root marketplace index .claude-plugin/marketplace.json publishes this package from./plugins/claude/context7and mirrors version1.0.4.plugins/codex/context7/**is the Codex plugin package. plugins/…/plugin.json declares package metadata plus UI-facinginterfacedetails, points skills to./skills/, and points MCP configuration to ./.mcp.json; plugins/…/.mcp.json uses HTTPhttps://mcp.context7.com/mcp. The bundled plugins/…/SKILL.md is the same detailed Context7 workflow used by several other client-specific packages. Its README documents marketplace installation, OAuth in a browser, and a headless fallback throughnpx ctx7 setup --codex.plugins/copilot/context7/**is the GitHub Copilot CLI package. plugins/…/plugin.json declaresagents/,skills/,commands/, and .mcp.json component paths. plugins/…/.mcp.json points tohttps://mcp.context7.com/mcpand includes aContext7-API-Keyheader populated from${CONTEXT7_API_KEY:-}, so this package supports API-key authentication in addition to OAuth described in the README. Copilot also ships plugins/…/docs.md for/context7:docsmanual lookups and plugins/…/docs-researcher.agent.md for focused docs research.plugins/antigravity/context7/**is the Antigravity package. plugins/…/plugin.json holds marketplace metadata, suggested prompts, assets/logo.svg, and version1.0.1; plugins/…/mcp_config.json uses Antigravity'sserverUrlfield forhttps://mcp.context7.com/mcp. Its skill at plugins/…/SKILL.md follows the common Context7 workflow, and the README documents authentication through Agent Settings → Customizations.plugins/agent-plugins/context7/**is the portable Agent Plugins 1.0 package. plugins/…/plugin.json uses thehttps://agent-plugins.org/schemas/1.0.0/plugin.schema.jsonschema and intentionally keeps only portable top-level metadata. plugins/…/mcp.json uses the Agent Plugins MCP schema and astreamable-httpserver athttps://mcp.context7.com/mcp/oauth. Its README explains that Agent Plugins discovers plugin.json, mcp.json, andskills/from fixed locations and that credentials cannot be embedded or expanded in this portable format.plugins/context7-power/**packages Context7 as a "Power". plugins/…/POWER.md combines frontmatter metadata with instructions for when to use Context7 and how to callresolve-library-idandquery-docs; plugins/…/mcp.json points tohttps://mcp.context7.com/mcp.- gemini-extension.json is a root-level Gemini extension manifest. It declares a user setting named
API Keybacked byCONTEXT7_API_KEYand runs the local npm MCP package throughnpx -y @upstash/context7-mcp --api-key ${CONTEXT7_API_KEY}instead of using a hosted HTTP MCP URL.
The skill and agent instruction files are intentionally content-bearing assets, not generated code. The common context7-mcp skill text in plugins/…/SKILL.md, plugins/…/SKILL.md, plugins/…/SKILL.md, and plugins/…/SKILL.md tells agents to resolve a library, choose the best match by name, score, and version, query docs by single concept, optionally use query-code for exact source facts, and cite versions or source lines where relevant. The portable Agent Plugins copy at plugins/…/SKILL.md has a much longer frontmatter description because some hosts rely heavily on the skill description for activation.
Coupling
- If any plugin package version changes, verify its marketplace index points at the same package and version where one exists: .claude-plugin/marketplace.json mirrors plugins/…/plugin.json, while .cursor-plugin/marketplace.json points at
plugins/cursor/context7but does not carry a version. - If a component directory is renamed inside a package, update the host manifest that declares discovery paths: plugins/…/plugin.json names
./skills/,./rules/,./agents/, and ./mcp.json; plugins/…/plugin.json names./skills/and ./.mcp.json; plugins/…/plugin.json namesagents/,skills/,commands/, and .mcp.json. A path-only move can otherwise leave a marketplace install with missing skills, agents, commands, or MCP servers. - If the Context7 hosted MCP endpoint or auth mode changes, check every MCP declaration rather than assuming one shape applies everywhere: Cursor and portable Agent Plugins use OAuth endpoints under
/mcp/oauth, Claude adds?client=claude-code-plugin, Antigravity usesserverUrl, Copilot injectsContext7-API-KeyfromCONTEXT7_API_KEY, and Gemini shells out to@upstash/context7-mcpwith an API key. - If the lookup workflow changes, keep the repeated instruction assets in sync where the host-specific differences do not require divergence: plugins/…/SKILL.md, plugins/…/docs-researcher.md, plugins/…/docs-researcher.agent.md, plugins/…/docs.md, and plugins/…/POWER.md all describe resolving IDs, querying one concept at a time, and preferring version-specific docs.
- If portable Agent Plugins support new component types or credential fields, re-check plugins/…/README.md against plugins/…/plugin.json and plugins/…/mcp.json; the README currently explains that commands, agents, hooks, rules, and embedded API keys are intentionally absent because they are not portable in spec 1.0.
Risks
- Authentication can silently break if an endpoint is copied between packages without preserving the host-specific shape. For example, plugins/…/.mcp.json relies on a
Context7-API-Keyheader expansion, while plugins/…/mcp.json explicitly uses OAuth at/mcp/oauthbecause the portable spec forbids env expansion in URLs or headers; copying the Copilot pattern into the portable package would ship visible credential configuration that its README says clients must not use. - The common skill text is manually duplicated across plugins/…/SKILL.md, plugins/…/SKILL.md, plugins/…/SKILL.md, and plugins/…/SKILL.md. If only one copy is updated for a new tool parameter or guidance change, agents in the other hosts keep using stale instructions even though the package names and tool names are identical.