gitpro
io.github.YantrakarPublished by GitHub account Yantrakarv0.4.6Updated Nov 7, 2026
Read-only checks of which git name, email and SSH key a repository uses, and why.
Overview
Read-only MCP server that tells an assistant which Git name, email, SSH key and signing a repository uses, and why.
- What you can do
- Explain the expected Git identity for a repository and anything overriding it
- Report which SSH key and signing configuration apply, matched by remote URL
- Surface mismatches between the configured identity and the repository, with a suggested fix
- Give AI agents the same answers as the gitpro command-line tool
- When to use it
- Useful when you keep separate work and personal Git accounts, keys or signing setups and want an assistant to explain which identity a repository will commit with, or to diagnose a wrong email on commits.
- Requirements
- Runs as a local process on Linux or macOS with Git 2.36+, Python 3.9+ and OpenSSH; installed from PyPI with pipx or run with uvx. No accounts, API keys or environment variables are declared.
Installation
In SourceWeft
- Open gitpro in the dashboard and add it to a workspace.
- Enable the server for the chats that should use its tools.
Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.
Other MCP clients
Follow the launch instructions in the repository.
README
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.
Setup offers to look through your repos and proposes your identities. Accept, edit or answer the questions yourself; no TOML editing is needed. One preview shows everything, including the commit guard and, with Claude Code, its hook and MCP server. One yes applies it all. Setup never changes your repos.
Then:
Already have a config? gitpro setup brings this machine up to date with it.
gitpro setup -n only shows what is left to do. 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 uploads are never part of setup.
Using VS Code?
The extension shows the current identity and helps find repository-level overrides. It runs the same commands as the terminal. Install the extension.
Go further when you need to
AI agents get the same answers through the MCP server and the Claude Code hook: see agent workflows.
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.
License
Source: README.md at commit bad4111
Tools
0Version history
7- v0.4.6LatestNov 7, 2026
- v0.4.5Oct 22, 2026
- v0.4.3Oct 21, 2026
- v0.4.2Oct 20, 2026
- v0.4.1Oct 18, 2026
- v0.4.0Oct 17, 2026
- v0.3.4Oct 15, 2026
Score
50% of the applicable checks met
How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.
- Reached in the last 30 days25 pts
Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.
- Auth declared10 pts
Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.
- Tools listed15 pts
Answer tools/list without a credential, or ship a package that starts in a sandbox without one.
- DescriptionRequired15 pts
- Logo10 pts
- Documentation15 pts
- License10 pts