Skip to main content

​
Overview

Context7 maintains a growing registry of library documentation. If your favorite library isn’t available, you can submit it to be indexed and made available to the entire Context7 community.
All submitted libraries go through a review process to ensure quality and security.

​
Who Can Submit Libraries?

Anyone can submit a library to Context7:
  • Library maintainers
  • Contributors
  • Users who want documentation for a library
  • Organizations managing internal libraries

​
Submission Process

1

Check if the library exists

Before submitting, verify the library isn’t already in Context7:
  1. Search on context7.com
  2. Try using it in your AI assistant with Context7
  3. Use the SDK to search: 
    const libraries = await client.searchLibrary(
  "general query",
  "library-name"
);
2

Visit the submission page

Go to context7.com/docs/adding-libraries for the official submission form and detailed instructions.
3

Provide required information

You’ll need to provide:
  • Library name
  • Repository URL (GitHub, GitLab, etc.)
  • Documentation URL (if different from repository)
  • Brief description
  • Primary language/framework
4

Wait for review

The Context7 team will review your submission. This typically takes 1-3 business days.
5

Get notified

You’ll receive an email when your library is indexed and available.

​
Submission Requirements

For a library to be accepted into Context7, it should meet these criteria:

​
Documentation Quality

The library must have publicly accessible documentation. This can be:
  • README files
  • Dedicated documentation site
  • Wiki pages
  • API reference docs
  • Code comments (JSDoc, etc.)
The library should be actively maintained:
  • Recent commits (within last 6-12 months)
  • Responsive to issues
  • Regular releases
Exceptions may be made for stable, widely-used libraries with slower release cycles.
The library must have a clear open-source license or be commercially available with public documentation.
Libraries are scanned for security issues before indexing.

​
What Gets Indexed

Context7’s crawlers index:
  • README and markdown documentation files
  • Documentation websites
  • API reference pages
  • Code examples
  • Tutorial content
  • Migration guides
  • Changelog information
Private or internal documentation cannot be indexed. Only publicly accessible content is crawled.

​
Library ID Format

Once indexed, your library will have an ID following this format: 
/owner/repository
Examples:
  • /facebook/react
  • /vercel/next.js
  • /supabase/supabase
  • /mongodb/docs
This ID is used in prompts and SDK calls: 
use library /owner/repository for API and docs

​
Submitting Specific Versions

By default, Context7 indexes the latest version and recent major versions. If you need a specific version indexed:
  1. Mention it in your submission notes
  2. Provide a link to that version’s documentation
  3. Explain why that version is important (e.g., widely used legacy version)

​
Private or Internal Libraries

Context7 currently focuses on public, open-source libraries. For private or internal documentation:

Use the SDK

Build your own integration using the Context7 SDK for internal tools.

Self-hosted option

Contact Context7 about enterprise self-hosted options for private documentation.

​
After Submission

​
Review Process

Your submission goes through several checks:
  1. Automated checks: URL validation, documentation accessibility
  2. Security scan: Malware and security issue detection
  3. Quality review: Documentation completeness and clarity
  4. Indexing: Crawling and processing documentation
  5. Testing: Verification that the library works with Context7

​
Approval Timeline

1

Automated checks (minutes)

Initial validation of URLs and accessibility.
2

Security scan (hours)

Automated security scanning.
3

Manual review (1-3 days)

Team review for quality and completeness.
4

Indexing (varies)

Time depends on documentation size. Small libraries may be indexed in hours, large ones may take a day or two.

​
Rejection Reasons

Common reasons for rejection:
The library has minimal or no documentation beyond a basic README.Solution: Improve documentation before resubmitting.
No activity for 2+ years with no indication it’s feature-complete.Solution: Fork and maintain the project, or find an active alternative.
Documentation requires authentication or is behind a paywall.Solution: Make documentation publicly accessible.
Security scan found issues.Solution: Address security concerns and resubmit.
The library already exists in Context7.Solution: Use the existing library ID.

​
Updating Indexed Libraries

Context7 automatically crawls and updates indexed libraries on a regular schedule. However, if you need an immediate update:
  1. Visit context7.com/docs/adding-libraries
  2. Submit an update request with the library ID
  3. Mention what changed (new version, major documentation update, etc.)
Major version releases are usually re-crawled automatically within 24-48 hours.

​
Reporting Issues

If you find problems with indexed documentation:
  1. Outdated content: Request a re-crawl
  2. Missing pages: Report via the issue button on context7.com
  3. Incorrect information: Use the “Report” button on the library’s Context7 page
  4. Suspicious content: Report immediately via the “Report” button
Context7 projects are community-contributed. If you encounter suspicious, inappropriate, or potentially harmful content, please report it immediately.

​
Best Practices for Library Maintainers

If you’re submitting your own library, optimize for Context7 indexing:

​
Documentation Structure

 docs/
 ├── README.md (overview, quick start)
 ├── getting-started.md
 ├── api-reference.md
 ├── guides/
 │   ├── authentication.md
 │   ├── deployment.md
 │   └── best-practices.md
 └── examples/
     ├── basic-usage.md
     └── advanced-patterns.md

​
Include Code Examples

Ensure your documentation includes practical code examples: 
## Authentication

Here's how to authenticate users:

```typescript
import { createClient } from 'your-library';

const client = createClient({
  apiKey: process.env.API_KEY
});

await client.auth.signIn({
  email: '[email protected]',
  password: 'secure-password'
});
```

​
Version Documentation

Maintain documentation for major versions: 
docs/
├── v3/ (latest)
│   └── ...
├── v2/ (legacy, still supported)
│   └── ...
└── v1/ (deprecated, for reference)
    └── ...

​
Use Clear Headings

Structure documentation with clear, searchable headings: 
# Library Name

## Installation
## Quick Start  
## Core Concepts
## API Reference
## Examples
## Troubleshooting
This helps Context7’s AI better understand and retrieve relevant sections.

​
Community Contributions

Context7 relies on community contributions:
  • Submit libraries you use and want others to benefit from
  • Report issues with existing libraries
  • Suggest improvements to the indexing process
  • Share feedback on documentation quality

Join the discussion

Connect with the Context7 community on Discord.

​
FAQ

Initial indexing typically completes within 24 hours after approval. Large documentation sites may take longer.
Yes! Anyone can submit any public library. You don’t need to be the maintainer.
You’ll receive feedback on why it was rejected and what you can do to address the issues. You can resubmit after making improvements.
Context7 automatically re-crawls popular libraries weekly. Others are crawled monthly or when update requests are submitted.
Yes. If you’re the library maintainer, contact Context7 support to request removal.
No hard limit, but mass submissions may be rate-limited. Submit libraries genuinely useful to the community.

​
Next Steps

Submit a library

Ready to submit? Visit the official submission page.

Browse libraries

Explore what’s already available in Context7.

Build docs developers (and LLMs) love

Get started for freeTalk to us