Skip to content

chore: drop bundled context7 MCP server - #260

Open
ryzizub wants to merge 1 commit into
mainfrom
chore/drop-context7-mcp
Open

ryzizub wants to merge 1 commit into
mainfrom
chore/drop-context7-mcp

Conversation

@ryzizub

@ryzizub ryzizub commented Oct 26, 2026

Copy link
Copy Markdown
Contributor

Description

Wingspan shipped a .mcp.json that started @upstash/context7-mcp@latest for everyone who installed the plugin, even though only the two research agents used it and both already fell back to other sources. It also ran a second copy for users who already have Context7 configured globally.

The research agents now reference documentation sources generically — the installed packages themselves, a documentation MCP server if one is exposed in the tool list, or the official docs online — and fall back to the next source instead of blocking when one is unavailable. Context7 still works for anyone who configures it; it is simply no longer a dependency of the plugin.

  • Remove .mcp.json
  • Rewrite the Context7-specific steps in official-docs-research-agent and best-practices-research-agent
  • Drop .mcp.json from the repository structure in AGENTS.md and from the reporting scope in SECURITY.md

Type of Change

  • New feature (feat)
  • Bug fix (fix)
  • Code refactor (refactor)
  • Documentation (docs)
  • CI change (ci)
  • Chore (chore)

🤖 Generated with Claude Code

The plugin shipped a .mcp.json that started @upstash/context7-mcp@latest for
every user, while only the two research agents used it and both already had
fallbacks. Replace the Context7-specific instructions with source-agnostic
guidance: use whatever documentation sources the environment offers — the
installed packages themselves, a documentation MCP server if one is exposed,
or the official docs online — and fall back instead of blocking when a source
is unavailable.
@ryzizub
ryzizub marked this pull request as ready for review October 26, 2026 17:57
@ryzizub
ryzizub requested a review from a team as a code owner October 26, 2026 17:57
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants