Connect Claude Desktop once. Control repository access in Secure Git Bridge.

1. Install Secure Git Bridge once

Add the Git repositories you want Secure Git Bridge to protect. Each repository keeps its own isolated helper, rotating broker capability, protected-file policy, audit chain, and patch proposal store.

2. Connect Claude Desktop once

Open Claude Desktop in Secure Git Bridge and choose Connect Claude Desktop. Secure Git Bridge opens its Claude Desktop extension and copies one opaque provider pairing value. Install or update the extension, choose Configure, and paste that value once. If Claude does not accept the file handoff automatically, Secure Git Bridge opens Claude and reveals the extension file so you can use Claude Desktop → Settings → Extensions → Advanced settings → Install Extension.

The distributed extension is static and contains no repository path, repository ID, repository broker credential, or installation-specific provider credential. Claude stores the pairing value as sensitive extension configuration. The pairing authenticates the Claude connector to Secure Git Bridge; it does not select or grant a repository by itself.

Anthropic directory review is a separate provider approval. Secure Git Bridge does not describe the extension as Anthropic-reviewed or Anthropic-verified until that listing is actually approved.

Managed Claude organizations: if your organization enforces Claude Desktop's extension allowlist, your Claude administrator must allow Secure Git Bridge before the desktop extension can be installed. Claude also supports organization-scoped custom extension uploads. Neither mechanism grants repository authority; repository binding still happens only inside Secure Git Bridge.

3. Bind Claude Desktop to a repository in Secure Git Bridge

Select the approved repository in Secure Git Bridge and choose Bind to this repository. Secure Git Bridge creates the internal route only after that human action. Claude Desktop cannot enumerate, choose, or switch repositories through its connector.

If you later choose Move, Secure Git Bridge closes the previous provider session and moves the same installed connector to the newly selected repository. No reinstall is required.

4. Work through the Secure Git Bridge tools

• Read only policy-permitted repository content.
• Protected files and path escapes remain blocked.
• Git status, log, and diff remain repository-scoped.
• The AI may create patch proposals for local review.
• There is no Secure Git Bridge shell, repository picker, approval, rejection, or Apply tool for the AI.

Apply remains human-only inside Secure Git Bridge.

No Anthropic API key is required by Secure Git Bridge for the local Claude Desktop connector.

Disconnect without reinstalling

Unbind removes Claude Desktop's repository route while leaving the provider connector configured. Disconnect This Repository revokes every AI route to that repository. Disconnect All AI Access revokes all repository routes. Provider connectors can remain installed and be rebound later.

What “Connected,” “Bound,” and “Active” mean

Connector ready means the one-time provider setup has been handed off and no repository authority is implied. Bound means Secure Git Bridge has authorized one repository route. Active is shown only after Secure Git Bridge sees a live provider MCP session.

Provider account and data flow

Your Claude Desktop account, plan, usage, retention, and provider-side privacy terms remain with the provider. Repository content you intentionally authorize the AI to inspect can be transmitted to that provider through the normal AI interaction. Secure Git Bridge controls the local repository boundary and records access; it does not claim provider-side data handling.

Next steps

Download Secure Git Bridge Open the quick start

For the trust boundary and release model, see Security and How It Works.