docs: fix Context7 suggestions

[context7]

Looks good. Now let me double-check the "SDK login" — resolved.

Let me reconsider suggestion 4's inclusion and whether I should double-check with the readPromptSignal X-Context7-Auth-Prompt — not needed for the page.

One more: the architecture page references /library-updates — that's docs/library-updates.mdx with title "Keeping Libraries Fresh". The URL path is /library-updates. Good.

Also the architecture page says "health check GET /ping" — correct.

Let me verify the mcp index has /ping returning {"status":"ok","message":"pong"} — yes (lines 483-485). Good.

Now let me reconsider whether the architecture page's claim "rejects session-style GET/DELETE operations with 405" — from changelog 2.1.3: "Reject GET requests on MCP endpoints with 405 to eliminate idle SSE connection timeouts." And index.ts comment: "answers GET/DELETE (session operations) with 405." Good.

Now, is there anything about suggestion 4's "source freshness" — I linked to /library-updates. Good. "known accuracy limitations" — the query-docs "one concept per query" + 3 calls. Good.

Let me also verify I should keep the release-notes accuracy: 3.2.1/3.2.2 (EMA, opencode) omitted — fine, I summarized key ones and linked to full changelog.

Now the final answer HTML comment. Let me compose statuses:

1 fixed
2 fixed
3 fixed
4 fixed
5 fixed
6 dismissed
7 already_documented
8 fixed
9 fixed
10 fixed

Let me write the bullets under 8 words each for the "at most eight words" part. Wait, the bullet format: " — , in path/to/file". The first part is the suggestion summarized in ≤8 words. Then what changed + path.

Let me craft:

• MCP changelog surfaced in the docs — added @upstash/context7-mcp release history, in docs/resources/release-notes.mdx
• MCP breaking changes between major versions — same page covers 3.x→4.x, in docs/resources/release-notes.mdx
• MCP and REST network behavior documented — new architecture and release-notes pages, in docs/resources/architecture.mdx
• Quality filter evaluation mechanics expanded — AND combination, license and per-source filters, wildcard overrides, in docs/howto/policies.mdx
• Context response schemas documented — response schemas and codeList versus codeExamples, in docs/api-guide.mdx
• library page URL and token semantics — skipped: source defines only API-side token fields, not the page
• REST library search response with example JSON — added example response, in docs/api-guide.mdx
• base URL configuration documented — SDK baseUrl and CONTEXT7_API_URL, in docs/sdks/ts/getting-started.mdx and docs/resources/developer.mdx
• CLI setup flags reference — full option table and --stdio/-y example, in docs/clients/cli.mdx
• License (MIT) in the README — already shown via the MIT license badge

The order: the instructions say "changed ones first". So all "fixed" ones first, then already_documented/dismissed. Order within: I'll list by suggestion number for fixed ones? The instruction says changed ones first, then presumably others. Let me order fixed ones first (in suggestion-number order), then already_documented (7), then dismissed (6). Hmm, let me just do: 1,2,3,4,5,8,9,10 (fixed, numeric order), then 7 (already_documented), then 6 (dismissed). Actually simpler: fixed in numeric order (1-5,8,9,10), then 7 already_documented, then 6 dismissed.

Wait, but bullet count must be one per suggestion (10 bullets). Each bullet ≤120 words. Fine.

Let me make sure each bullet's first segment ≤8 words.

1. "Quality filter evaluation mechanics expanded" — 5 words ✓
2. "MCP changelog surfaced in the docs" — 6 ✓
3. "MCP breaking changes between major versions" — 5 ✓
4. "MCP and REST network behavior documented" — 6 ✓
5. "Context response schemas documented" — 4 ✓
6. "library page URL and token semantics" — 6 ✓ (dismissed)
7. "Licen

[mintlify]

Preview deployment for your docs. Learn more about Mintlify Previews.

Project	Status	Preview	Updated
context7	🟢 Ready	View Preview	Sep 9, 2026, 2:07 AM

💡 Tip: Enable Automations to automatically generate PRs for you.

[context7]

Docs7 for context7.com

Result	Status	Action
Deployment	✅ Ready	Open preview

Commit 260e1db · Updated 2026-09-09 02:08 UTC · View build details