* docs: backup and restore guide for on-premise
* docs: add dashboard restore flow and Keep all retention
* docs: use ctx7:restore in the local restore command
* docs: use consistent library/index vocabulary in backup-restore
Add the page files for the Policies and Rules dashboard tabs, which the
nav (docs.json) already references. Policies covers source-type access
and library filters; Rules covers global and library-specific teamspace
rules.
Co-authored-by: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
* docs(azure-apim): reflect Settings tab + cascade-delete + audience-uniqueness
Three updates after merging the per-user identity feature to production:
1. Dashboard navigation: Entra cards moved from the Overview tab to a
conditional Settings tab (only visible for enterprise teamspaces or
active trials). Update Part 4 and the troubleshooting section.
2. Cascade-delete: clicking Remove on the Microsoft Entra ID card now
removes both the tenant configuration AND all provisioned users in a
single step. Add a note so admins know not to use Remove for
single-user revocation.
3. Audience uniqueness: each MCP API app (audience GUID) can be claimed
by one teamspace at a time. Document the failure mode and how to
resolve it, since hitting it from a fresh setup is easy.
* docs(azure-apim): add Part 6 — smoke test the gateway from CLI
Walks through pre-authorizing Azure CLI on the Gateway app's scope and
running an `az account get-access-token` + curl against APIM end-to-end.
Lets admins validate the full OBO flow before pointing real MCP clients
at the gateway.
Renumber the original "Connect an MCP client" to Part 7.
* docs(enterprise): add Azure APIM deployment guide
Step-by-step guide for deploying Context7 behind Azure API Management
with Microsoft Entra ID per-user authentication via On-Behalf-Of (OBO)
token exchange. Covers APIM provisioning, Entra app registrations,
policy wiring, OAuth discovery surfaces, and connecting MCP clients
(VS Code Copilot, Cursor) through the gateway.
* docs(azure-apim): cover user pre-provisioning + fix variable typo
- Restructure Part 4 into two steps: tenant config + pre-provisioning
users via the new dashboard card. Calls out that Context7 rejects
unmapped oids — there is no auto-provisioning.
- Add troubleshooting entry for the unmapped-user 401 (most common
failure once tenant config is correct).
- Fix \$APIM_NAME → \$APIM typo in the OAuth proxy provisioning
commands; the rest of the doc uses \$APIM so the OAuth proxy
commands would have failed as written.
* docs: add server URL reference to README and all-clients page
The remote server URL was not easily discoverable in the docs.
This surfaces it in the README installation section and in the
all-clients page intro so users can find it without digging
through individual client configurations.
* docs: align all-clients intro with README wording
* docs: restore unlisted client fallback sentence
* fix(cli): use ~/.agents/skills for global universal skill installs
The universal global path was ~/.config/agents/skills, but the
canonical standard (used by Vercel's skills CLI and OpenAI Codex)
is ~/.agents/skills. This aligns context7 with the broader ecosystem.
Fixes#2276
* chore: add changeset for global skills path fix
The single deployment.mdx page implied Kubernetes-only deployment. Split it into
a deployment/ folder with separate Docker and Kubernetes guides, and simplify the
on-premise getting started page to link to them via Mintlify cards.
New deployment.mdx page under the On-Premise section covering
StatefulSet, Service, Ingress manifests, registry auth, networking
requirements, operations, and troubleshooting for K8s deployments.
Fahreddin Özcan