Skip to content

Context7 Platform -- Up-to-date docs for AI agents

feat(docs): enhance documentation with improved titles, descriptions, and structured steps for clarity (#2778)

Enes Gules195357db7061
diff --git a/docs/adding-libraries.mdx b/docs/adding-libraries.mdx
index 681b627c..3ee7c6a9 100644
--- a/docs/adding-libraries.mdx
+++ b/docs/adding-libraries.mdx
@@ -1,138 +1,54 @@
---
-title: Library Owners
+title: Adding Libraries
+description: Add a public library to Context7 so AI coding assistants get up-to-date docs for it
---
-Context7 allows you to add your favorite libraries and frameworks so developers always receive current, trustworthy documentation inside their coding environment.
+Context7 indexes public libraries from their source repositories so developers get current, version-specific documentation inside their coding tools. Anyone can add a public library — you don't need to own it.
-## Claiming Your Library
+## Add a Library
-If you're the library owner, you can claim your library on Context7 to unlock a web-based admin panel for managing configuration. This allows you to:
+The fastest way to add a library is through the web interface:
-- Edit settings through a user interface instead of committing file changes
-- Invite team members to collaborate on configuration
-- Add and manage multiple versions of your library documentation
-- Get higher rate limits for refresh operations
+**[Add a Library →](https://context7.com/add-library)**
-**[Learn more about claiming libraries →](/howto/claiming-libraries)**
-
-## Who Can Manage Configuration?
-
-- **Library authors**: Claim ownership via `context7.json` and manage settings through the admin panel, or add configuration directly to your repository
-- **Contributors**: Submit pull requests to add or update the configuration
-
-## Quick Submission
-
-The fastest way to add a library is through our web interface:
-
-**[Submit a Library ->](https://context7.com/add-library?tab=github)**
-
-1. Paste the GitHub repository URL.
-2. (Optional) Adjust folders and exclusions.
-3. Submit and let Context7 parse and index the documentation.
+<Steps>
+ <Step title="Open the Add Library page">
+ Go to [context7.com/add-library](https://context7.com/add-library) and select the **GitHub** tab.
+ </Step>
+ <Step title="Paste the repository URL">
+ Paste the public GitHub repository URL for the library you want to add.
+ </Step>
+ <Step title="Adjust parsing (optional)">
+ Optionally narrow what gets indexed by setting included folders and exclusions. For finer control — committed to the repository itself — add a `context7.json` file (see [Library Owners](/library-owners)).
+ </Step>
+ <Step title="Submit">
+ Submit the repository. Context7 parses and indexes the documentation, then makes it available by its [library ID](/api-guide) (format: `/org/project`).
+ </Step>
+</Steps>
<Note>
- For private sources, see the [Private Sources](/howto/private-sources) guide. Requires a Pro or
- Enterprise plan.
+ This page is for **public** libraries. To add internal or private documentation, see the [Private Sources](/howto/private-sources) guide (requires a Pro or Enterprise plan).
</Note>
-## Advanced Configuration with `context7.json`
-
-For more control over how Context7 parses and presents your library, you can add a `context7.json` file to the root of your repository. This file works similarly to `robots.txt` and tells Context7 how to handle your project.
-
-### Configuration Fields
-
-Here's an example `context7.json` file with all available options:
-
-```json
-{
- "$schema": "https://context7.com/schema/context7.json",
- "projectTitle": "Upstash Ratelimit",
- "description": "Ratelimiting library based on Upstash Redis",
- "folders": [],
- "excludeFolders": ["src"],
- "excludeFiles": [],
- "rules": ["Use Upstash Redis as a database", "Use single region set up"],
- "previousVersions": [
- {
- "tag": "v1.2.1"
- }
- ]
-}
-```
-
-<Note>
- **Pro Tip**: Including the `$schema` field enables autocomplete, validation, and helpful tooltips
- in modern code editors like VS Code, making it easier to create and maintain your configuration.
-</Note>
-
-## Field Descriptions
-
-- **`projectTitle`** (string): Suggested display name for your project in Context7. Only used when the LLM cannot generate a name with high confidence.
-
-- **`description`** (string): Suggested description for your project in Context7. Only used when the LLM cannot generate a description with high confidence.
-
-- **`branch`** (string): The name of the git branch to parse. If not provided, the default branch will be used.
-
-- **`folders`** (array): Specific folder paths to include when parsing. If empty, Context7 scans the entire repository. Root-level markdown files are always included.
-
-- **`excludeFolders`** (array): Patterns to exclude from documentation parsing. Supports simple names, paths, and glob patterns (see Exclusion Patterns below).
-
-- **`excludeFiles`** (array): Specific file names to exclude. Use only the filename, not the full path. Examples: `CHANGELOG.md`, license files, or non-documentation content.
-
-- **`rules`** (array): Best practices or important guidelines that coding agents should follow when using your library. These appear as recommendations in the documentation context provided to coding agents.
-
-- **`previousVersions`** (array): Information about previous versions of your library that should also be available in Context7.
- - **`tag`**: The Git tag or version identifier
-
-- **`branchVersions`** (array): Information about previous versions (branch-based) of your library that should also
- be available in Context7.
- - **`branch`**: The Git branch
-
-### Exclusion Patterns
-
-The `excludeFolders` parameter supports various pattern types for flexible exclusion:
-
-- **Simple folder names**: `"node_modules"` - Excludes any folder named "node_modules" anywhere in the tree
-- **Root-specific patterns**: `"./xyz"` - Excludes the folder only at repository root (e.g., excludes `/xyz` but not `/dist/xyz`)
-- **Path patterns**: `"app-sdk/v2.3"` - Excludes specific paths and everything under them
-- **Glob patterns**: `"*.test"`, `"temp*"` - Excludes folders matching the pattern
-- **Globstar patterns**: `"**/dist"`, `"docs/**/internal"` - Advanced path matching
-- **Complex patterns**: `"src/**/*.test.js"` - Exclude test files in the src directory
-
-Examples:
-
-- `"node_modules"` - Excludes all node_modules folders anywhere
-- `"./build"` - Excludes the build folder only at root (not `src/build`)
-- `"app-sdk/v2.3"` - Excludes the app-sdk/v2.3 path and all its contents
-- `"*.test"` - Excludes folders ending with .test
-- `"docs/**/internal"` - Excludes any "internal" folder under docs
-- `"**/temp"` - Excludes any folder named "temp" anywhere
-
-### Default Exclusions
-
-If you don't specify `excludeFiles` or `excludeFolders` in your `context7.json` file, Context7 uses these default patterns:
+## Maintain the Library?
-#### Default Excluded Files
+If you own or maintain the library, you can take control of how it appears in Context7 — configure parsing with `context7.json`, manage versions through a web admin panel, and get higher refresh limits.
-```
-CHANGELOG.md, changelog.md, CHANGELOG.mdx, changelog.mdx
-LICENSE.md, license.md
-CODE_OF_CONDUCT.md, code_of_conduct.md
-```
+<CardGroup cols={2}>
+ <Card title="Library Owners" icon="gear" href="/library-owners">
+ Control parsing and presentation with `context7.json`
+ </Card>
+ <Card title="Claim Your Library" icon="circle-check" href="/howto/claiming-libraries">
+ Verify ownership and unlock the admin panel
+ </Card>
+</CardGroup>
-#### Default Excluded Folders
+## Keeping Docs Fresh
-```
-*archive*, *archived*, old, docs/old, *deprecated*, *legacy*
-*previous*, *outdated*, *superseded*
-i18n/zh*, i18n/es*, i18n/fr*, i18n/de*, i18n/ja*, i18n/ko*
-i18n/ru*, i18n/pt*, i18n/it*, i18n/ar*, i18n/hi*, i18n/tr*
-i18n/nl*, i18n/pl*, i18n/sv*, i18n/vi*, i18n/th*
-zh-cn, zh-tw, zh-hk, zh-mo, zh-sg
-```
+Once a library is added, Context7 [refreshes its documentation automatically](/library-updates) based on popularity, so developers keep receiving up-to-date docs without any manual work.
-These defaults help coding agents avoid irrelevant, outdated, and non-technical content.
+For tighter control, add the [Context7 GitHub Action](/integrations/github-actions) to trigger a refresh on every push to your default branch — so a new release's docs are indexed as soon as you ship it.
## Need Help?
-If you encounter issues or need assistance adding your project, please [open an issue](https://github.com/upstash/context7/issues/new/choose) or reach out to our community.
+If you encounter issues or need assistance adding a library, please [open an issue](https://github.com/upstash/context7/issues/new/choose) or reach out to our community.
diff --git a/docs/agentic-tools/overview.mdx b/docs/agentic-tools/overview.mdx
index 9f525edd..3c8c6625 100644
--- a/docs/agentic-tools/overview.mdx
+++ b/docs/agentic-tools/overview.mdx
@@ -29,6 +29,12 @@ Context7's agentic tools solve these problems by giving your agents direct acces
Add Context7 tools to your AI SDK workflows with `generateText`, `streamText`, or use the
pre-built `Context7Agent` for automatic documentation lookup.
</Card>
+ <Card title="TypeScript SDK" icon="js" href="/sdks/ts/getting-started">
+ Call Context7 directly from any TypeScript or Node.js app.
+ </Card>
+ <Card title="MCP Server" icon="plug" href="/resources/all-clients">
+ Connect Context7's MCP server to any agent or editor.
+ </Card>
</CardGroup>
## How It Works
diff --git a/docs/docs.json b/docs/docs.json
index 57cc3f4c..a9bd0f5e 100644
--- a/docs/docs.json
+++ b/docs/docs.json
@@ -26,6 +26,7 @@
"plans-pricing",
"clients/cli",
"adding-libraries",
+ "library-owners",
"library-updates",
"api-guide",
"tips"
diff --git a/docs/enterprise.mdx b/docs/enterprise.mdx
index 528d9b87..5ebde6f3 100644
--- a/docs/enterprise.mdx
+++ b/docs/enterprise.mdx
@@ -1,6 +1,7 @@
---
title: Enterprise
sidebarTitle: Overview
+description: Turn your internal documentation into LLM-ready context for developers, coding agents, and engineering leaders
---
Context7 Enterprise converts your internal documentation into structured, high-quality context optimized for LLMs — enabling human developers, coding agents, and engineering leaders to build faster and operate with clarity.
diff --git a/docs/enterprise/deployment/docker.mdx b/docs/enterprise/deployment/docker.mdx
index 511eedb6..376dcc57 100644
--- a/docs/enterprise/deployment/docker.mdx
+++ b/docs/enterprise/deployment/docker.mdx
@@ -1,6 +1,7 @@
---
title: "Docker Deployment"
sidebarTitle: "Docker"
+description: "Deploy Context7 On-Premise with Docker Compose"
---
Deploy Context7 On-Premise with Docker Compose. This guide assumes you have completed the [On-Premise setup](/enterprise/on-premise) and have a valid license key.
diff --git a/docs/enterprise/deployment/kubernetes.mdx b/docs/enterprise/deployment/kubernetes.mdx
index 17050ebd..4643dc75 100644
--- a/docs/enterprise/deployment/kubernetes.mdx
+++ b/docs/enterprise/deployment/kubernetes.mdx
@@ -1,6 +1,7 @@
---
title: "Kubernetes Deployment"
sidebarTitle: "Kubernetes"
+description: "Deploy Context7 On-Premise on Kubernetes using raw manifests"
---
Deploy Context7 On-Premise on Kubernetes using raw manifests. This guide assumes you have completed the [On-Premise setup](/enterprise/on-premise) and have a valid license key.
diff --git a/docs/enterprise/on-premise.mdx b/docs/enterprise/on-premise.mdx
index bdd63e46..6ce04cd5 100644
--- a/docs/enterprise/on-premise.mdx
+++ b/docs/enterprise/on-premise.mdx
@@ -1,6 +1,7 @@
---
title: "On-Premise Deployment"
sidebarTitle: "Getting Started"
+description: "Run the full Context7 stack inside your own infrastructure, so code and documentation never leave your environment"
---
Context7 On-Premise lets you run the full Context7 stack inside your own infrastructure. Your code, documentation, and embeddings never leave your environment.
diff --git a/docs/howto/api-keys.mdx b/docs/howto/api-keys.mdx
index de27f0fc..450a0754 100644
--- a/docs/howto/api-keys.mdx
+++ b/docs/howto/api-keys.mdx
@@ -1,5 +1,5 @@
---
-title: API Keys
+title: Manage API Keys
description: Create and manage API keys for Context7 authentication
---
@@ -11,31 +11,38 @@ API keys authenticate your requests to Context7's documentation services.
### Creating API Keys
-Generate a new API key in four simple steps:
-
-1. **Click "Create API Key"** in the API Keys card
-2. **Enter a name** (optional but recommended)
- - Use descriptive names like "Cursor", "Claude", "VS Code", or "Devin Desktop"
- - This helps you identify keys later
-3. **Copy the key immediately**
- - Keys are shown only once for security
- - Format: `ctx7sk-**********************`
-4. **Use in your requests or add to your MCP configuration**:
-
-```bash
-curl "https://context7.com/api/v2/context?libraryId=/vercel/next.js&query=routing" \
- -H "Authorization: Bearer YOUR_API_KEY"
-```
+<Steps>
+ <Step title="Open the create dialog">
+ Click **Create API Key** in the API Keys card.
+ </Step>
+ <Step title="Name the key">
+ Enter a name (optional but recommended). Descriptive names like "Cursor", "Claude", "VS Code", or "Devin Desktop" help you identify the key later.
+ </Step>
+ <Step title="Copy the key immediately">
+ Keys are shown only once for security. The format is `ctx7sk-**********************`.
+ </Step>
+ <Step title="Use the key">
+ Use it in your requests or MCP configuration:
+
+ ```bash
+ curl "https://context7.com/api/v2/context?libraryId=/vercel/next.js&query=routing" \
+ -H "Authorization: Bearer YOUR_API_KEY"
+ ```
+ </Step>
+</Steps>
<Warning>Store your API key securely. You won't be able to see it again after creation.</Warning>
### Revoking Keys
-Remove API keys you no longer need:
-
-1. **Click the delete button** next to the key
-2. **Confirm deletion** in the modal
-3. **Key deactivates immediately** - all requests using it will fail
+<Steps>
+ <Step title="Delete the key">
+ Click the delete button next to the key you no longer need.
+ </Step>
+ <Step title="Confirm deletion">
+ Confirm in the modal. The key deactivates immediately — all requests using it will fail.
+ </Step>
+</Steps>
<Note>
Revoking a key is permanent and cannot be undone. Update any applications using the key before
diff --git a/docs/howto/chat-widget.mdx b/docs/howto/chat-widget.mdx
index 24ed556f..dfa83f31 100644
--- a/docs/howto/chat-widget.mdx
+++ b/docs/howto/chat-widget.mdx
@@ -1,5 +1,5 @@
---
-title: Chat Widget
+title: Add the Chat Widget
description: Embed an AI-powered chat assistant on your documentation site
---
diff --git a/docs/howto/oauth.mdx b/docs/howto/oauth.mdx
index 18fa17fb..1fa6ce55 100644
--- a/docs/howto/oauth.mdx
+++ b/docs/howto/oauth.mdx
@@ -1,5 +1,5 @@
---
-title: OAuth
+title: Set Up OAuth
description: Authenticate with Context7 MCP server using OAuth 2.0
---
diff --git a/docs/howto/policies.mdx b/docs/howto/policies.mdx
index 95b63da7..6daf4ecf 100644
--- a/docs/howto/policies.mdx
+++ b/docs/howto/policies.mdx
@@ -1,5 +1,5 @@
---
-title: Policies
+title: Manage Policies
description: Control which sources and libraries your teamspace can access
---
diff --git a/docs/howto/private-sources.mdx b/docs/howto/private-sources.mdx
index 6a89469f..4cf6bc78 100644
--- a/docs/howto/private-sources.mdx
+++ b/docs/howto/private-sources.mdx
@@ -9,19 +9,28 @@ Add private sources to Context7 to make your internal documentation available to
## Adding Private Sources
-Follow these steps to add a private source:
-
-1. Go to your teamspace's **Sources** tab
-2. **Click "Add another"** to open the source type selector
-3. **Select a source type**:
- - **GitHub** — connect your GitHub account and select a repository
- - **GitLab** — connect your GitLab account and select a project
- - **Bitbucket** — connect your Bitbucket account and select a repository
- - **Other Git** — add any Git repository by URL
- - **Confluence** — connect your Confluence workspace
- - **OpenAPI** — add an OpenAPI specification
-4. **Authorize** Context7 to access your source (if required)
-5. **Submit** for parsing
+<Steps>
+ <Step title="Open the Sources tab">
+ Go to your teamspace's **Sources** tab.
+ </Step>
+ <Step title="Add a source">
+ Click **Add another** to open the source type selector.
+ </Step>
+ <Step title="Select a source type">
+ - **GitHub** — connect your GitHub account and select a repository
+ - **GitLab** — connect your GitLab account and select a project
+ - **Bitbucket** — connect your Bitbucket account and select a repository
+ - **Other Git** — add any Git repository by URL
+ - **Confluence** — connect your Confluence workspace
+ - **OpenAPI** — add an OpenAPI specification
+ </Step>
+ <Step title="Authorize access">
+ Authorize Context7 to access your source (if required).
+ </Step>
+ <Step title="Submit for parsing">
+ Submit the source for parsing.
+ </Step>
+</Steps>
<Note>You must have a Pro or Enterprise plan to add private sources. Public sources can be added from the [Add Library](https://context7.com/add-library) page.</Note>
@@ -45,11 +54,14 @@ Keep your private documentation up to date:
### Removing Sources
-To remove a private source:
-
-1. **Click the trash icon** next to the source
-2. **Confirm deletion** in the modal
-3. Source documentation becomes unavailable immediately
+<Steps>
+ <Step title="Delete the source">
+ Click the trash icon next to the source.
+ </Step>
+ <Step title="Confirm deletion">
+ Confirm in the modal. The source documentation becomes unavailable immediately.
+ </Step>
+</Steps>
<Warning>
This action is permanent. The source will no longer be accessible via the API.
@@ -79,4 +91,4 @@ Add a `context7.json` file to your repository root for better control over parsi
}
```
-See the [Adding Libraries](/adding-libraries) page for complete configuration options.
+See the [Library Owners](/library-owners) page for complete configuration options.
diff --git a/docs/howto/rules.mdx b/docs/howto/rules.mdx
index 8af738d5..e8d360d8 100644
--- a/docs/howto/rules.mdx
+++ b/docs/howto/rules.mdx
@@ -1,5 +1,5 @@
---
-title: Rules
+title: Manage Rules
description: Prepend custom guidelines to the documentation your teamspace retrieves
---
@@ -24,9 +24,19 @@ Each rule applies at one of two scopes:
## Adding a Rule
-1. Open the [rules tab](https://context7.com/dashboard?tab=rules) and click **Add Rule...**
-2. Choose the scope — **Global** or a specific **Library**.
-3. Enter the rule text.
-4. Save. The rule takes effect on the next documentation request made with the teamspace's API keys.
+<Steps>
+ <Step title="Open the rules tab">
+ Open the [rules tab](https://context7.com/dashboard?tab=rules) and click **Add Rule...**.
+ </Step>
+ <Step title="Choose the scope">
+ Pick **Global** or a specific **Library**.
+ </Step>
+ <Step title="Enter the rule text">
+ Write the instruction you want prepended to retrieved documentation.
+ </Step>
+ <Step title="Save">
+ Save the rule. It takes effect on the next documentation request made with the teamspace's API keys.
+ </Step>
+</Steps>
Existing rules are grouped by scope in the list. Select **Global Rules** or any library entry to edit or remove its rules.
diff --git a/docs/howto/teamspace.mdx b/docs/howto/teamspace.mdx
index f07b1daa..a88abee7 100644
--- a/docs/howto/teamspace.mdx
+++ b/docs/howto/teamspace.mdx
@@ -11,8 +11,14 @@ Add team members, assign roles, and manage access to your Context7 dashboard fro
![Create teamspace dropdown](/images/dashboard/user-dropdown.png)
-1. Click "Create a teamspace" from the top left dropdown
-2. Enter teamspace name
+<Steps>
+ <Step title="Open the teamspace menu">
+ Click **Create a teamspace** from the top-left dropdown.
+ </Step>
+ <Step title="Name the teamspace">
+ Enter a teamspace name.
+ </Step>
+</Steps>
<Note>You must have a Pro or Enterprise plan to create a teamspace. Only the teamspace owner needs a paid plan — invited members don't need their own subscription. Once added, all members automatically benefit from the team's Pro or Enterprise limits.</Note>
@@ -30,11 +36,17 @@ Add team members, assign roles, and manage access to your Context7 dashboard fro
## Inviting Members
-1. Enter member email
-2. Select role (Developer or Admin)
-3. Click "Add"
-4. Member receives an invitation email
-5. Once they sign in, they are automatically added to the teamspace
+<Steps>
+ <Step title="Enter the member's email">
+ Enter the email address of the person you want to invite.
+ </Step>
+ <Step title="Select a role">
+ Choose **Developer** or **Admin**.
+ </Step>
+ <Step title="Send the invite">
+ Click **Add**. The member receives an invitation email and is automatically added to the teamspace once they sign in.
+ </Step>
+</Steps>
<Note>The invitation will remain pending until they sign in.</Note>
diff --git a/docs/howto/verification.mdx b/docs/howto/verification.mdx
index 466e9e56..339c6577 100644
--- a/docs/howto/verification.mdx
+++ b/docs/howto/verification.mdx
@@ -1,5 +1,5 @@
---
-title: Library Verification
+title: Verify Your Library
description: Get your library verified to increase visibility and build trust with developers
---
diff --git a/docs/library-owners.mdx b/docs/library-owners.mdx
new file mode 100644
index 00000000..837471a8
--- /dev/null
+++ b/docs/library-owners.mdx
@@ -0,0 +1,126 @@
+---
+title: Library Owners
+description: Claim your library and control how Context7 parses it with context7.json
+---
+
+If you maintain a library or framework, Context7 lets you control how its documentation is parsed and presented — so developers always receive current, trustworthy docs inside their coding environment.
+
+To simply add a public library, see [Adding Libraries](/adding-libraries). This page covers ownership and advanced configuration.
+
+## Claiming Your Library
+
+If you're the library owner, you can claim your library on Context7 to unlock a web-based admin panel for managing configuration. This allows you to:
+
+- Edit settings through a user interface instead of committing file changes
+- Invite team members to collaborate on configuration
+- Add and manage multiple versions of your library documentation
+- Get higher rate limits for refresh operations
+
+**[Learn more about claiming libraries →](/howto/claiming-libraries)**
+
+## Who Can Manage Configuration?
+
+- **Library authors**: Claim ownership via `context7.json` and manage settings through the admin panel, or add configuration directly to your repository
+- **Contributors**: Submit pull requests to add or update the configuration
+
+## Advanced Configuration with `context7.json`
+
+For more control over how Context7 parses and presents your library, you can add a `context7.json` file to the root of your repository. This file works similarly to `robots.txt` and tells Context7 how to handle your project.
+
+### Configuration Fields
+
+Here's an example `context7.json` file with all available options:
+
+```json
+{
+ "$schema": "https://context7.com/schema/context7.json",
+ "projectTitle": "Upstash Ratelimit",
+ "description": "Ratelimiting library based on Upstash Redis",
+ "folders": [],
+ "excludeFolders": ["src"],
+ "excludeFiles": [],
+ "rules": ["Use Upstash Redis as a database", "Use single region set up"],
+ "previousVersions": [
+ {
+ "tag": "v1.2.1"
+ }
+ ]
+}
+```
+
+<Note>
+ **Pro Tip**: Including the `$schema` field enables autocomplete, validation, and helpful tooltips
+ in modern code editors like VS Code, making it easier to create and maintain your configuration.
+</Note>
+
+## Field Descriptions
+
+- **`projectTitle`** (string): Suggested display name for your project in Context7. Only used when the LLM cannot generate a name with high confidence.
+
+- **`description`** (string): Suggested description for your project in Context7. Only used when the LLM cannot generate a description with high confidence.
+
+- **`branch`** (string): The name of the git branch to parse. If not provided, the default branch will be used.
+
+- **`folders`** (array): Specific folder paths to include when parsing. If empty, Context7 scans the entire repository. Root-level markdown files are always included.
+
+- **`excludeFolders`** (array): Patterns to exclude from documentation parsing. Supports simple names, paths, and glob patterns (see Exclusion Patterns below).
+
+- **`excludeFiles`** (array): Specific file names to exclude. Use only the filename, not the full path. Examples: `CHANGELOG.md`, license files, or non-documentation content.
+
+- **`rules`** (array): Best practices or important guidelines that coding agents should follow when using your library. These appear as recommendations in the documentation context provided to coding agents.
+
+- **`previousVersions`** (array): Information about previous versions of your library that should also be available in Context7.
+ - **`tag`**: The Git tag or version identifier
+
+- **`branchVersions`** (array): Information about previous versions (branch-based) of your library that should also
+ be available in Context7.
+ - **`branch`**: The Git branch
+
+### Exclusion Patterns
+
+The `excludeFolders` parameter supports various pattern types for flexible exclusion:
+
+- **Simple folder names**: `"node_modules"` - Excludes any folder named "node_modules" anywhere in the tree
+- **Root-specific patterns**: `"./xyz"` - Excludes the folder only at repository root (e.g., excludes `/xyz` but not `/dist/xyz`)
+- **Path patterns**: `"app-sdk/v2.3"` - Excludes specific paths and everything under them
+- **Glob patterns**: `"*.test"`, `"temp*"` - Excludes folders matching the pattern
+- **Globstar patterns**: `"**/dist"`, `"docs/**/internal"` - Advanced path matching
+- **Complex patterns**: `"src/**/*.test.js"` - Exclude test files in the src directory
+
+Examples:
+
+- `"node_modules"` - Excludes all node_modules folders anywhere
+- `"./build"` - Excludes the build folder only at root (not `src/build`)
+- `"app-sdk/v2.3"` - Excludes the app-sdk/v2.3 path and all its contents
+- `"*.test"` - Excludes folders ending with .test
+- `"docs/**/internal"` - Excludes any "internal" folder under docs
+- `"**/temp"` - Excludes any folder named "temp" anywhere
+
+### Default Exclusions
+
+If you don't specify `excludeFiles` or `excludeFolders` in your `context7.json` file, Context7 uses these default patterns:
+
+#### Default Excluded Files
+
+```
+CHANGELOG.md, changelog.md, CHANGELOG.mdx, changelog.mdx
+LICENSE.md, license.md
+CODE_OF_CONDUCT.md, code_of_conduct.md
+```
+
+#### Default Excluded Folders
+
+```
+*archive*, *archived*, old, docs/old, *deprecated*, *legacy*
+*previous*, *outdated*, *superseded*
+i18n/zh*, i18n/es*, i18n/fr*, i18n/de*, i18n/ja*, i18n/ko*
+i18n/ru*, i18n/pt*, i18n/it*, i18n/ar*, i18n/hi*, i18n/tr*
+i18n/nl*, i18n/pl*, i18n/sv*, i18n/vi*, i18n/th*
+zh-cn, zh-tw, zh-hk, zh-mo, zh-sg
+```
+
+These defaults help coding agents avoid irrelevant, outdated, and non-technical content.
+
+## Need Help?
+
+If you encounter issues or need assistance adding your project, please [open an issue](https://github.com/upstash/context7/issues/new/choose) or reach out to our community.
diff --git a/docs/overview.mdx b/docs/overview.mdx
index 209e5182..970cfc1e 100644
--- a/docs/overview.mdx
+++ b/docs/overview.mdx
@@ -1,6 +1,7 @@
---
title: Intro
sidebarTitle: Intro
+description: Context7 brings up-to-date, version-specific library documentation into your AI coding assistant
---
Context7 brings up-to-date, version-specific documentation and code examples directly into your AI coding assistant. That means no more outdated code or hallucinated APIs.
diff --git a/docs/resources/troubleshooting.mdx b/docs/resources/troubleshooting.mdx
index d3a5d2bb..a82db88b 100644
--- a/docs/resources/troubleshooting.mdx
+++ b/docs/resources/troubleshooting.mdx
@@ -1,5 +1,6 @@
---
title: Troubleshooting
+description: Resolve common issues when setting up or using the Context7 MCP server
---
This guide helps you resolve common issues when setting up or using Context7 MCP.
diff --git a/docs/security/auth-and-access-control.mdx b/docs/security/auth-and-access-control.mdx
index 175cd3fd..a726ae6e 100644
--- a/docs/security/auth-and-access-control.mdx
+++ b/docs/security/auth-and-access-control.mdx
@@ -28,4 +28,11 @@ This guide covers the authentication mechanisms and access controls available in
- Audit logs for compliance
- Custom authentication policies
+### Setup Guides
+
+For step-by-step configuration on self-hosted deployments, see:
+
+- [Microsoft Entra ID (SSO)](/enterprise/security/entra-sso) — wire up Entra ID sign-in for an On-Premise instance
+- [Azure API Management](/enterprise/azure-apim) — proxy the Context7 MCP server through Azure APIM with Entra authentication
+
Contact our sales team at [context7.com/contact](https://context7.com/contact) for Enterprise plan details.
\ No newline at end of file
diff --git a/docs/security/best-practices.mdx b/docs/security/best-practices.mdx
index 54d2bb69..6ae95557 100644
--- a/docs/security/best-practices.mdx
+++ b/docs/security/best-practices.mdx
@@ -1,6 +1,7 @@
---
title: Best Practices for Users
sidebarTitle: Best Practices
+description: Recommendations for using Context7 securely across credentials, repository access, and network usage
---
These recommendations cover how to use Context7 securely across credentials, repository access, and network usage.
diff --git a/docs/security/compliance-and-reporting.mdx b/docs/security/compliance-and-reporting.mdx
index bc660fe7..a7d256bd 100644
--- a/docs/security/compliance-and-reporting.mdx
+++ b/docs/security/compliance-and-reporting.mdx
@@ -1,5 +1,6 @@
---
title: Compliance and Reporting
+description: How Context7 handles security reporting, transparency, and compliance certifications
---
How Context7 handles security reporting, transparency, and compliance.
diff --git a/docs/security/data-privacy.mdx b/docs/security/data-privacy.mdx
index 7bd90b25..505baa0e 100644
--- a/docs/security/data-privacy.mdx
+++ b/docs/security/data-privacy.mdx
@@ -1,5 +1,6 @@
---
title: Data Privacy
+description: How Context7 handles query storage, retrieval scope, and your data
---
How Context7 handles privacy, retrieval scope, and data.
diff --git a/docs/security/data-safety.mdx b/docs/security/data-safety.mdx
index 7e4e3833..a8f84911 100644
--- a/docs/security/data-safety.mdx
+++ b/docs/security/data-safety.mdx
@@ -1,5 +1,6 @@
---
title: Data Safety
+description: How Context7 detects prompt injection and malicious content in indexed documentation
---
## Prompt Injection and Malware Pattern Detection
diff --git a/docs/security/infrastructure.mdx b/docs/security/infrastructure.mdx
index 3b739774..6657a793 100644
--- a/docs/security/infrastructure.mdx
+++ b/docs/security/infrastructure.mdx
@@ -1,6 +1,7 @@
---
title: Infrastructure Security
sidebarTitle: Infrastructure
+description: The platform-level protections behind Context7, including hosting, abuse prevention, and secure development
---
The operational and platform-level protections behind Context7, including hosted infrastructure, abuse prevention, and secure development practices.
diff --git a/docs/security/overview.mdx b/docs/security/overview.mdx
index a17fd54e..c2cc56ea 100644
--- a/docs/security/overview.mdx
+++ b/docs/security/overview.mdx
@@ -1,6 +1,7 @@
---
title: Security
sidebarTitle: Overview
+description: An overview of Context7's security practices, data handling, and compliance measures
---
Context7 takes security and privacy seriously. This page outlines our security practices, data handling, and compliance measures.