dip, or the Git MCP tools.
Create and clone a repository
Ask an MCP-connected agent to create a repository, or callgit_create_repository. Get its clone
address with git_get_clone_url, then clone with stock Git. A repository address has this form:
443 are equivalent.
A credential for another port is refused.
Use dip git clone to configure the credential helper for this command only. It answers only for the
exact Dippr Git host:
dip refreshes it from your existing sign-in when it
can. It does not save the credential or configure a global Git helper. Requests for GitHub, GitLab,
another tenant’s host, or a non-HTTPS address receive no credential.
Sign a commit and push
Dippr requires platform-issued SSH signing material for pushes. Run one Git command throughdip git sign:
dip places the key and
allowed-signers file in a private temporary directory for that command, then removes them on success,
failure, or interruption. The signed push also carries an owner attestation that binds the actor,
repository, ref, commit, and agent or app origin when one exists.
Push normally after the signed commit:
Roles and protected refs
Repository access follows your tenant role. There is no separate repository member list.
An act-as role never retains permissions from the wider role behind it. Protected refs can require
fast-forward updates and signed commits. Rules accept an exact
refs/... name or one bounded *
path segment; Dippr limits both the number of rules and their length.
Revocation and external remotes
Theplane_git entitlement turns this service on. If it is removed, clone, fetch, push, new
credentials, repository creation, and new app or agent bindings stop. Existing repository metadata
remains visible and repositories can still be deleted, so stored source is not hidden or stranded.
GitHub and GitLab remain independent remotes. Dippr never mirrors them, synchronizes changes, stores
their credentials, or imports their history automatically. Add and use an external remote explicitly
with Git when you need one.
What gets recorded
Repository creation, deletion, and committed ref updates appear in the tenant audit history asgit.repository_created, git.repository_deleted, and git.ref_updated. Refused pushes use
git.push_denied or git.signature_rejected. Entries include repository and ref identifiers and
the old and new object IDs when applicable. They exclude source files, diffs, commit messages,
credentials, and signing private keys.
Audit recording is best effort. A successful ref update remains successful if its later audit entry
or source-refresh notification is delayed or dropped.
Related
MCP tools
Manage repositories and ref proposals from an AI agent.
OAuth scopes
Compare Git read and write credentials.