# context7 - Doramagic AI Context Pack

> Purpose: pre-work context for the user's host AI. This pack does not prove that the project has been installed, run, or validated.

## Project

- canonical_name: `upstash/context7`
- capability: MCP server for Context7
- expected_user_outcome: MCP server for Context7

## Operating Boundaries

- Do not claim that the project has been installed, run, called through an API, or used on local files unless separate evidence proves it.
- Project facts must come from repo evidence, Claim Graph, or explicit source references.
- When a capability is not verified, mark it as unverified instead of completing it as fact.
- publish_status: `publishable`
- blocking_gaps: none

---

## Doramagic Context Augmentation

The following sections strengthen the repository context for a host AI. Human Manual data is a reading route, and pitfall notes become operating constraints.

## Human Manual Outline

Usage rule: this is only a reading route and salience signal, not factual authority. Concrete claims must still return to repo evidence or Claim Graph.

Host AI hard rules:
- Do not treat page titles, section order, summaries, or importance values as factual project evidence.
- When explaining the Human Manual outline, state that it is only a reading route or salience signal.
- Capability, installation, compatibility, runtime state, and risk claims must cite repo evidence, source paths, or Claim Graph.

- **Context7 Platform Overview and Architecture**: importance `high`
  - source_paths: README.md, package.json, pnpm-workspace.yaml, server.json, .env.example
- **MCP Server and Core Documentation Tools**: importance `high`
  - source_paths: packages/mcp/src/index.ts, packages/mcp/src/lib/api.ts, packages/mcp/src/lib/auth/auth-prompt.ts, packages/mcp/src/lib/encryption.ts, packages/mcp/src/lib/jwt.ts
- **ctx7 CLI, Agent Setup, and Skills System**: importance `high`
  - source_paths: packages/cli/src/index.ts, packages/cli/src/commands/setup.ts, packages/cli/src/commands/remove.ts, packages/cli/src/commands/auth.ts, packages/cli/src/commands/docs.ts
- **SDKs, Extensions, and Plugin Ecosystem**: importance `medium`
  - source_paths: packages/sdk/src/client.ts, packages/sdk/src/commands/get-context/index.ts, packages/sdk/src/commands/get-context/types.ts, packages/sdk/src/commands/search-library/index.ts, packages/sdk/src/commands/search-library/types.ts

## Repo Inspection Evidence

- repo_clone_verified: true
- repo_inspection_verified: true
- repo_commit: `7dde3382b0223ed3022cf89542b23b95b4ea532e`
- inspected_files: `pnpm-lock.yaml`, `README.md`, `package.json`, `docs/contact.mdx`, `docs/overview.mdx`, `docs/docs.json`, `docs/enterprise.mdx`, `docs/library-updates.mdx`, `docs/api-guide.mdx`, `docs/skills.mdx`, `docs/tips.mdx`, `docs/plans-pricing.mdx`, `docs/openapi.json`, `docs/adding-libraries.mdx`, `docs/installation.mdx`, `docs/clients/cli.mdx`, `docs/clients/cursor.mdx`, `docs/clients/claude-code.mdx`, `docs/clients/opencode.mdx`, `docs/agentic-tools/overview.mdx`

Host AI hard rules:
- Without repo_clone_verified=true, do not claim that the source code has been read.
- Without repo_inspection_verified=true, do not write README, docs, or package-file conclusions as facts.
- Without quick_start_verified=true, do not claim that the Quick Start path has run successfully.

## Doramagic Pitfall Constraints

These rules come from Doramagic discovery, validation, or compilation findings. The host AI must treat them as operating constraints, not background notes.

### Constraint 1: Security or permission risk requires verification

- Trigger: Developers should check this security_permissions risk before relying on the project: [Bug]: OAuth metadata issuer mismatch for MCP OAuth endpoint
- Host AI rule: Before packaging this project, run the relevant install/config/quickstart check for: [Bug]: OAuth metadata issuer mismatch for MCP OAuth endpoint. Context: Source discussion did not expose a precise runtime context.
- Why it matters: Developers may expose sensitive permissions or credentials: [Bug]: OAuth metadata issuer mismatch for MCP OAuth endpoint
- Evidence: failure_mode_cluster:github_issue | fmev_95c37b5d4ec8d5ee4507509dad3c2a1f | https://github.com/upstash/context7/issues/2723
- Hard boundary: Do not present this pitfall as solved, verified, or ignorable unless later evidence explicitly closes it.

### Constraint 2: Installation risk requires verification

- Trigger: Developers should check this installation risk before relying on the project: @upstash/context7-pi@0.1.0
- Host AI rule: Before packaging this project, run the relevant install/config/quickstart check for: @upstash/context7-pi@0.1.0. Context: Observed when using node
- Why it matters: Upgrade or migration may change expected behavior: @upstash/context7-pi@0.1.0
- Evidence: failure_mode_cluster:github_release | fmev_46f371ada1fbace84d952510823b7f4b | https://github.com/upstash/context7/releases/tag/%40upstash/context7-pi%400.1.0
- Hard boundary: Do not present this pitfall as solved, verified, or ignorable unless later evidence explicitly closes it.

### Constraint 3: Installation risk requires verification

- Trigger: Developers should check this installation risk before relying on the project: Add tool to search by npm package name to skip the initial docs index search, makes MCP server faster
- Host AI rule: Before packaging this project, run the relevant install/config/quickstart check for: Add tool to search by npm package name to skip the initial docs index search, makes MCP server faster. Context: Observed when using node
- Why it matters: Developers may fail before the first successful local run: Add tool to search by npm package name to skip the initial docs index search, makes MCP server faster
- Evidence: failure_mode_cluster:github_issue | fmev_97f541b9c1bdf6a270413d479cb65002 | https://github.com/upstash/context7/issues/230
- Hard boundary: Do not present this pitfall as solved, verified, or ignorable unless later evidence explicitly closes it.

### Constraint 4: Installation risk requires verification

- Trigger: Developers should check this installation risk before relying on the project: [Feature Request] Local docs sync and numerous dx improvements
- Host AI rule: Before packaging this project, run the relevant install/config/quickstart check for: [Feature Request] Local docs sync and numerous dx improvements. Context: Observed during installation or first-run setup.
- Why it matters: Developers may fail before the first successful local run: [Feature Request] Local docs sync and numerous dx improvements
- Evidence: failure_mode_cluster:github_issue | fmev_33ab52cf164db9dced1235e8c17026f6 | https://github.com/upstash/context7/issues/103
- Hard boundary: Do not present this pitfall as solved, verified, or ignorable unless later evidence explicitly closes it.

### Constraint 5: Installation risk requires verification

- Trigger: Developers should check this installation risk before relying on the project: ctx7 setup --cli: downloadSkillFromGitHub missing Authorization header causes 403
- Host AI rule: Before packaging this project, run the relevant install/config/quickstart check for: ctx7 setup --cli: downloadSkillFromGitHub missing Authorization header causes 403. Context: Observed when using macos
- Why it matters: Developers may fail before the first successful local run: ctx7 setup --cli: downloadSkillFromGitHub missing Authorization header causes 403
- Evidence: failure_mode_cluster:github_issue | fmev_f983d67f6d5644dbb372458c86f98034 | https://github.com/upstash/context7/issues/2363
- Hard boundary: Do not present this pitfall as solved, verified, or ignorable unless later evidence explicitly closes it.

### Constraint 6: Installation risk requires verification

- Trigger: Developers should check this installation risk before relying on the project: ctx7@0.4.5
- Host AI rule: Before packaging this project, run the relevant install/config/quickstart check for: ctx7@0.4.5. Context: Observed during installation or first-run setup.
- Why it matters: Upgrade or migration may change expected behavior: ctx7@0.4.5
- Evidence: failure_mode_cluster:github_release | fmev_9786b7981f1e51c97bd00ed6170af655 | https://github.com/upstash/context7/releases/tag/ctx7%400.4.5
- Hard boundary: Do not present this pitfall as solved, verified, or ignorable unless later evidence explicitly closes it.

### Constraint 7: Installation risk requires verification

- Trigger: Developers should check this installation risk before relying on the project: ctx7@0.5.1
- Host AI rule: Before packaging this project, run the relevant install/config/quickstart check for: ctx7@0.5.1. Context: Observed when using docker
- Why it matters: Upgrade or migration may change expected behavior: ctx7@0.5.1
- Evidence: failure_mode_cluster:github_release | fmev_5ee21e73150b416333eaa911b8e0c948 | https://github.com/upstash/context7/releases/tag/ctx7%400.5.1
- Hard boundary: Do not present this pitfall as solved, verified, or ignorable unless later evidence explicitly closes it.

### Constraint 8: Installation risk requires verification

- Trigger: Project evidence flags a installation risk. Review the linked source before relying on this workflow.
- Host AI rule: Reproduce the official install and quickstart path in an isolated environment.
- Why it matters: May increase setup, validation, or first-run risk for the user.
- Evidence: community_evidence:github | cevd_37c5d19255fa423199c3f5f0b317c9b1 | https://github.com/upstash/context7/issues/230
- Hard boundary: Do not present this pitfall as solved, verified, or ignorable unless later evidence explicitly closes it.

### Constraint 9: Configuration risk requires verification

- Trigger: Developers should check this configuration risk before relying on the project: @upstash/context7-mcp@3.1.0
- Host AI rule: Before packaging this project, run the relevant install/config/quickstart check for: @upstash/context7-mcp@3.1.0. Context: Source discussion did not expose a precise runtime context.
- Why it matters: Upgrade or migration may change expected behavior: @upstash/context7-mcp@3.1.0
- Evidence: failure_mode_cluster:github_release | fmev_554228c877dad4ddb42a45c3dcf8b001 | https://github.com/upstash/context7/releases/tag/%40upstash/context7-mcp%403.1.0
- Hard boundary: Do not present this pitfall as solved, verified, or ignorable unless later evidence explicitly closes it.

### Constraint 10: Configuration risk requires verification

- Trigger: Developers should check this configuration risk before relying on the project: Feature Request: Support multiple product docs in one repo
- Host AI rule: Before packaging this project, run the relevant install/config/quickstart check for: Feature Request: Support multiple product docs in one repo. Context: Source discussion did not expose a precise runtime context.
- Why it matters: Developers may misconfigure credentials, environment, or host setup: Feature Request: Support multiple product docs in one repo
- Evidence: failure_mode_cluster:github_issue | fmev_752d9c6ad1111e7576eb2b756e09be9a | https://github.com/upstash/context7/issues/328
- Hard boundary: Do not present this pitfall as solved, verified, or ignorable unless later evidence explicitly closes it.