Context7 MCP

GitHub Actions

Automatically refresh your Context7 library when your docs change
1 min read

Keep your Context7 documentation in sync by triggering a refresh whenever you push to your main branch.

Setup#

Get your API key

Go to your Context7 dashboard and copy your API key.

Add the API key as a repository secret

In your GitHub repository, go to SettingsSecrets and variablesActions and add a new secret:

NameValue
CONTEXT7_API_KEYYour API key from the Context7 dashboard

Create the workflow file

Add the following file to your repository at .github/workflows/context7-refresh.yml:

This uses ${{ github.repository }} to automatically resolve to your repository's owner/repo (e.g., vercel/next.js). If your library ID on Context7 differs from your GitHub repository name, replace it with the correct value (e.g., /your-org/your-repo).

Refreshing a Specific Branch#

To refresh a non-default branch, add the branch field to the request body. The branch value must match a branch name that already exists on your library in Context7.

Note

If the branch has not been added to your library on Context7, the refresh will fail with a branch_not_found error.

Private Repositories#

For private repositories, include a gitToken so Context7 can access your code:

Note

Private sources require a Pro or Enterprise plan. See the Private Sources guide for more details.