gitpro
Read-only checks of which git name, email and SSH key a repository uses, and why.
Runs on your machine from its package; the steps are below.
What it does
- Reads
- Writes
- High impact
At most: only reads or looks up information.
What it costs
FreeOdel charges nothing per call. The publisher may charge for its own service.
Runs locally over stdio
This server isn't hosted — your MCP client launches it from a package registry. Use one of the commands below, or drop the config into your client (e.g. Claude Desktop).
Run
uvx gitpro
MCP client config
{
"mcpServers": {
"gitpro": {
"command": "uvx",
"args": [
"gitpro"
]
}
}
}
gitpro
The right Git identity, SSH key and signature for every repository.
gitpro.dev · PyPI · VS Code · made by Yantrakar
Work on a company repository, commit with your work email. Switch to a personal project, use your personal identity. Gitpro chooses by remote URL, not by where you happened to clone the repository.
Useful when you have more than one GitHub/GitLab account, separate work and personal keys, or keep finding the wrong email on your commits.
Try it
Requires Linux or macOS, Git 2.36+, Python 3.9+ and OpenSSH. Install from PyPI with pipx.
pipx install gitpro
gitpro setup --write
The wizard helps you choose identities, Git hosts and owners, existing SSH keys, and optional signing. No TOML editing is needed for basic setup. Review the configuration before saving; nothing is applied to Git or SSH yet.
gitpro plan # see exactly what would change
gitpro apply -y # explicitly apply the reviewed changes
Then, inside a repository:
gitpro why # see the expected identity and anything overriding it
Already have a config? Run gitpro setup --write to add another identity without losing
your existing settings or comments. Prefer editing files? The
user guide covers the full TOML format.
What you get
- Work/personal separation: names, emails, SSH keys and signing per host/owner.
- Answers, not guesswork:
gitpro whyexplains mismatches and suggests a fix. - A safety net: optional hooks can block wrong-identity commits and pushes.
- Editor and container support: see your identity in VS Code and carry it into dev containers.
Gitpro generates ordinary Git and SSH configuration; it needs no background service. Changes can be previewed, existing hand-written files are backed up, and key creation or uploads are never part of the setup wizard.
Using VS Code?
Run gitpro: Set Up Identities from the Command Palette to open the same wizard in a terminal. The extension also shows the current identity and helps find repository-level overrides. Install the extension.
Go further when you need to
For agents, the versioned workflow provides structured preflight, identity-scoped execution and durable idempotency for commits, pushes and GitHub PRs. Persistent changes use exact proposals, human approval by default, optional operator-scoped preauthorization, and recoverable apply. MCP execution is opt-in.
| I want to… | Start here |
|---|---|
| Understand matching, SSH keys or signing | Configuration |
| Find wrong identities or forgotten work | Daily use · Finding things |
| Use dev containers | Container setup |
| Configure team policy, CI or AI assistants | Teams and CI · AI assistants |
| Look up a command or undo changes | Command reference · Undo |
| Troubleshoot or contribute | Troubleshooting · Development |
The detailed TOML, YAML and command examples live in the guide, not on the getting-started path.
Problems and questions
Run gitpro report to draft an issue with the versions and a redacted
gitpro why; it shows you the draft and opens nothing until you say yes.
Or open an issue at github.com/Yantrakar/gitpro/issues.
Report a security problem privately with gitpro report --security, as the
security policy describes,
not in a public issue.
