Introducing a new way to review your PRs.

Read the announcement

upstash / context7

Context7 Platform -- Up-to-date docs for AI agents

View on GitHub

13 documents · Updated Nov 16, 2026

docs / editor-agent-plugins

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), and mcpServers: ./mcp.json; plugins/…/mcp.json points the context7 server at https://mcp.context7.com/mcp/oauth. Cursor-specific behavior lives in plugins/cursor/context7/rules/use-context7.mdc (always-on rule), plugins/…/SKILL.md (library-doc lookup workflow, including optional query-code source 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 at https://mcp.context7.com/mcp?client=claude-code-plugin. Its README documents Claude's browser sign-in via /mcp and explicitly says this plugin does not read CONTEXT7_API_KEY; headless/API-key setup is delegated to npx ctx7 setup --claude or manual MCP configuration. The root marketplace index .claude-plugin/marketplace.json publishes this package from ./plugins/claude/context7 and mirrors version 1.0.4.
  • plugins/codex/context7/** is the Codex plugin package. plugins/…/plugin.json declares package metadata plus UI-facing interface details, points skills to ./skills/, and points MCP configuration to ./.mcp.json; plugins/…/.mcp.json uses HTTP https://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 through npx ctx7 setup --codex.
  • plugins/copilot/context7/** is the GitHub Copilot CLI package. plugins/…/plugin.json declares agents/, skills/, commands/, and .mcp.json component paths. plugins/…/.mcp.json points to https://mcp.context7.com/mcp and includes a Context7-API-Key header 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:docs manual 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 version 1.0.1; plugins/…/mcp_config.json uses Antigravity's serverUrl field for https://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 the https://agent-plugins.org/schemas/1.0.0/plugin.schema.json schema and intentionally keeps only portable top-level metadata. plugins/…/mcp.json uses the Agent Plugins MCP schema and a streamable-http server at https://mcp.context7.com/mcp/oauth. Its README explains that Agent Plugins discovers plugin.json, mcp.json, and skills/ 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 call resolve-library-id and query-docs; plugins/…/mcp.json points to https://mcp.context7.com/mcp.
  • gemini-extension.json is a root-level Gemini extension manifest. It declares a user setting named API Key backed by CONTEXT7_API_KEY and runs the local npm MCP package through npx -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

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-Key header expansion, while plugins/…/mcp.json explicitly uses OAuth at /mcp/oauth because 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.