MCP Context7 Docs

mcp-context7-docs

Activation gate (anti-noise)

Activate when at least one is true:

• User asks for current/official docs for a named library or framework (Next.js, FastAPI, Prisma, etc.).
• User includes "use context7" or equivalent.
• You are about to call a third-party API and the exact version or recent API surface matters.

Do not activate for:

• General web search, news, or "what happened lately" → use searxng / duckduckgo (see skills/deep-research/SKILL.md).
• Deep synthesized research with citations in one call → perplexity only when user explicitly requests deep research.
• Repo-local conventions → read the repository first (repo-grounding).

Procedure

1. Identify library name and version if known (from package.json, pyproject.toml, lockfile, or user).
2. Call Context7 MCP tools to resolve and fetch relevant documentation snippets.
3. Prefer official API shapes from Context7 over memory or training cutoff; cite that docs came from Context7 when they drive a design choice.
4. If Context7 is unavailable: mark UNCERTAIN, fall back to searxng for the official docs URL, then read repo lockfiles for version.

Output

• Short: which library/version was targeted + key API constraints + next implementation step.
• Do not dump full doc pages; keep only what the current task needs.

Failure handling

• MCP unreachable: confirm context7 in mcp.json, CONTEXT7_API_KEY in ~/.cursor/.env — runbook doc/mcp-secrets.md; restart Cursor; Node.js 18+ / npx on PATH.