Other Git Integration

Context7 can clone and index repositories from any self-managed Git host that isn’t GitHub or GitLab, such as Gerrit, Gitea, or self-hosted Bitbucket, over HTTPS or SSH. Configure the host under Settings → Integrations → Other Git, choose the HTTPS or SSH tab, then add repositories with their normal clone URL.

These hosts have no GitHub-style webhooks. Drive re-indexing on merge from your CI (for example Jenkins) by calling POST /api/gitops/reconcile or POST /api/projects/<id>/refresh after a push. See GitOps.

HTTPS (basic auth)

On the HTTPS tab, fill in the host and an account’s credentials:

Other Git HTTPS settings: host, username, and HTTP password under Settings, Integrations

Field	Description
Host	The Git host, without `https://`. For example, `gerrit.your-company.com`. Repositories whose `https://` URL is on this host are cloned with the credentials below.
Username	The account username. This is required, because HTTP basic auth needs a username (for Gerrit, generate an HTTP password in its settings and use that account’s username).
HTTP Password / Token	The account’s HTTP password or access token.

Then add a repository with its HTTPS clone URL, for example https://gerrit.your-company.com/a/platform/sdk.

Presenting a private or self-signed TLS certificate? Point NODE_EXTRA_CA_CERTS at your CA bundle (recommended), or set GIT_TLS_INSECURE=true for testing only. Always use https:// for credentialed clones. A plaintext http:// host to a non-loopback address is logged as a warning.

SSH (deploy key)

When a repository is added with an ssh:// URL, for example ssh://<user>@gerrit.your-company.com:29418/platform/sdk, Context7 authenticates with a deploy key. Register the key’s public half on a service account in your Git host that can read the repositories you want to index, then give Context7 the private half one of two ways.

Paste the key in the UI (recommended)

On the SSH tab, paste the private key. It is stored encrypted and used for all ssh:// clones. Optionally paste a known_hosts entry to pin the host key; if you leave it blank, the host key is trusted on first use.

Other Git SSH settings: private key and known hosts under Settings, Integrations

Generate the known_hosts entry with ssh-keyscan, for example:

ssh-keyscan -p 29418 gerrit.your-company.com

That’s all you need. Add repositories with their ssh:// URL and they clone with the pasted key.

Mount a key into the container (alternative)

If you prefer the private key never touch the application (it is never written to the database or included in backups), mount it into the container instead and point Git at it with GIT_SSH_COMMAND. Leave the UI SSH key blank, and a mounted key is used whenever no key is configured in the UI.

Kubernetes
Docker

apiVersion: v1
kind: Secret
metadata:
  name: context7-git-ssh
type: Opaque
stringData:
  id_ed25519: |
    -----BEGIN OPENSSH PRIVATE KEY-----
    ...
    -----END OPENSSH PRIVATE KEY-----
  known_hosts: |
    [gerrit.your-company.com]:29418 ssh-ed25519 AAAA...

spec:
  containers:
    - name: context7
      env:
        - name: GIT_SSH_COMMAND
          value: "ssh -i /etc/git-ssh/id_ed25519 -o UserKnownHostsFile=/etc/git-ssh/known_hosts"
      volumeMounts:
        - name: git-ssh
          mountPath: /etc/git-ssh
          readOnly: true
  volumes:
    - name: git-ssh
      secret:
        secretName: context7-git-ssh
        defaultMode: 0400

docker run -d -p 3000:3000 -v context7-data:/data \
  -v /path/to/id_ed25519:/etc/git-ssh/id_ed25519:ro \
  -v /path/to/known_hosts:/etc/git-ssh/known_hosts:ro \
  -e GIT_SSH_COMMAND="ssh -i /etc/git-ssh/id_ed25519 -o UserKnownHostsFile=/etc/git-ssh/known_hosts" \
  -e LLM_API_KEY=sk-... \
  ghcr.io/context7/enterprise

The on-premise image ships with an SSH client, so no extra packages are needed either way.

Add a repository

Once the host is configured, add repositories the same as any other source:

Open Add Repository

From Add Repository, choose the Other Git source.

Paste the clone URL

Enter the repository’s clone URL. The scheme selects how it authenticates:

HTTPS: https://gerrit.your-company.com/a/platform/sdk (uses the HTTPS credentials above).
SSH: ssh://<user>@gerrit.your-company.com:29418/platform/sdk (uses the deploy key).

Parse

Context7 clones, indexes the documentation, and serves it over MCP. Re-index later with the project’s Refresh action or from CI. See GitOps.

You can also declare these repositories in a GitOps manifest to manage the whole index as code.

Overview

How To

Enterprise

Security

Clients

SDKs

Agentic Tools

API Reference

Integrations

Resources

HTTPS (basic auth)

SSH (deploy key)

Paste the key in the UI (recommended)

Mount a key into the container (alternative)

Add a repository

​HTTPS (basic auth)

​SSH (deploy key)

​Paste the key in the UI (recommended)

​Mount a key into the container (alternative)

​Add a repository

HTTPS (basic auth)

SSH (deploy key)

Paste the key in the UI (recommended)

Mount a key into the container (alternative)

Add a repository