gitpro

io.github.Yantrakar由 GitHub 账号 Yantrakar 发布v0.4.6更新于 Nov 7, 2026

Read-only checks of which git name, email and SSH key a repository uses, and why.

已验证STDIO仅桌面开发者工具安全与监控

概览

AI 生成的概览

只读 MCP 服务器,让助手查明某个仓库使用哪个 Git 姓名、邮箱、SSH 密钥和签名,以及原因。

可以做什么
  • 解释仓库预期的 Git 身份以及任何覆盖它的设置
  • 说明按远程 URL 匹配到的 SSH 密钥与签名配置
  • 指出配置身份与仓库之间的不一致,并给出修复建议
  • 让 AI 代理获得与 gitpro 命令行工具相同的答案
适用场景
适合同时维护工作与个人 Git 账号、密钥或签名配置的人,用来让助手说明某个仓库提交时会用哪个身份,或排查提交中出现的错误邮箱。
运行要求
作为本地进程运行,需要 Linux 或 macOS、Git 2.36+、Python 3.9+ 和 OpenSSH;从 PyPI 用 pipx 安装或用 uvx 运行。未声明任何账号、API 密钥或环境变量。
安装前请注意
该 MCP 服务器被描述为只读,但 gitpro 工具本身会写入 Git 和 SSH 配置,并可安装可选的提交与推送拦截钩子;在你同意后,安装过程可能读取你的仓库、SSH 配置和编辑器最近记录。安装过程不包含上传密钥。

安装

在 SourceWeft 中

  1. 打开 控制台中的 gitpro,将其添加到工作区。
  2. 为需要使用其工具的对话启用该服务。

Desktop only,通过 STDIO。 STDIO 服务会启动本地进程,因此需要 SourceWeft 桌面宿主。

其他 MCP 客户端

参照 仓库 中的启动说明。

README

[gitpro]

gitpro

The right Git identity, SSH key and signature for every repository.

gitpro.dev · PyPI · VS Code · made by Yantrakar

[gitpro refuses a commit in a work repo that would use the personal email, removes the repo's own email setting, and the commit then uses the work email, while a personal repo keeps the personal one]

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.

sh
pipx install gitprogitpro setup

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.

mermaid
flowchart LR  S["gitpro setup"] --> HC{"Config <br/>exists?"}  HC -->|no| L["Read your repos, <br/>SSH config and <br/>editor recents, <br/>if you agree"]  L --> Q["Propose <br/>identities; you <br/>accept or edit"]  Q --> I  HC -->|yes| I["Inspect config, <br/>Git and SSH files, <br/>keys, guard, <br/>agent hook, MCP"]  I -->|all current| OK["Nothing <br/>to do"]  I -->|something to do| PV["One preview, <br/>each part with <br/>its undo"]  PV --> ASK{"Apply <br/>all?"}  ASK -->|no| NONE["Nothing <br/>written"]  ASK -->|yes| AP["Write it, print <br/>the public keys <br/>to register"]  AP --> NX["Next: <br/>gitpro scan"]

Then:

sh
gitpro why               # inside a repository: the expected identity and anything overriding itgitpro scan              # repos that need a fix, with the command for each

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 why explains 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.

I want to…Start here
Understand matching, SSH keys or signingConfiguration
Find wrong identities or forgotten workDaily use · Finding things
Use dev containersContainer setup
Configure team policy, CI or AI assistantsTeams and CI · AI assistants
Look up a command or undo changesCommand reference · Undo
Troubleshoot or contributeTroubleshooting · Development

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

MIT

来源:README.md,提交 bad4111

工具

0
SourceWeft 尚未在沙箱中启动过该软件包,因此其工具未知。

版本历史

7
  1. v0.4.6最新Nov 7, 2026
  2. v0.4.5Oct 22, 2026
  3. v0.4.3Oct 21, 2026
  4. v0.4.2Oct 20, 2026
  5. v0.4.1Oct 18, 2026
  6. v0.4.0Oct 17, 2026
  7. v0.3.4Oct 15, 2026

评分

已满足适用检查项的 50%

该评分衡量此收录条目的完整程度,依据注册中心条目、端点与公开来源计算得出。它不是对服务器本身的评价,也不表示服务器安全或当前可用:可连通性是带日期的检查结果,评分也不包含安装量或用户评价。

  • 近 30 天内可连通25 分

    请保持端点能够响应 MCP 握手;SourceWeft 每 30 天探测一次。

  • 已声明认证方式10 分

    请在注册中心条目中声明凭据请求头,或保持端点能够响应探测,以便判定其认证方式。

  • 已列出工具15 分

    请让服务器在无凭据时响应 tools/list,或发布可在沙箱中无凭据启动的软件包。

  • 描述必需15 分
  • 图标10 分
  • 文档15 分
  • 许可证10 分