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 分