GitEasy MCP

io.github.greenmtnsun由 GitHub 账号 greenmtnsun 发布v1.6.2更新于 Oct 25, 2026

Plain-English git for agents: 22 tools to branch, commit, push and tag. Free tier.

已验证Streamable HTTP可网页运行文件与存储开发者工具

概览

AI 生成的概览

一个远程 MCP 服务器，让助手用通俗方式完成日常 Git 操作：建分支、提交、推送、打标签、查看历史和管理凭据。

可以做什么
保存工作：一步完成暂存、带说明提交并可选推送，或推送已提交内容，并创建附注标签和发布以将改动发布到远程仓库。查看状态：显示仓库诊断信息、变更文件、差异、远程地址、最近及按关键词搜索的提交历史、待拉取提交和发布列表。管理分支：从 HEAD 创建新分支、切换到已有分支，以及将单个文件恢复到 HEAD 状态。撤销改动：丢弃单个文件或全部已跟踪文件的未提交改动，并删除未跟踪的文件和目录。管理凭据：保存个人访问令牌、将远程地址改为 SSH、设置或查看凭据助手保管库、测试登录并清除已存凭据。
适用场景
适合让助手在不手写原始 Git 命令的情况下处理仓库的日常 Git 操作，例如保存并发布改动、查看改了什么、浏览历史或创建发布标签。
运行要求
通过 streamable HTTP 访问的远程端点，不安装本地包。需要在 X-Api-Key 请求头中提供 API 密钥；清单指向一个带每月写入调用上限的免费密钥。所操作的仓库需能被该服务访问。
安装前请注意
API 密钥是放在 X-Api-Key 请求头中的机密，免费额度限制每月写入调用次数，频繁使用可能需要付费密钥。多个工具会改变状态：push、save_work、new_release、switch_work、new_work_branch、set_ssh、set_vault、set_token 和 reset_login。restore_file、undo_changes 和 clear_junk 会丢弃未提交或未跟踪的内容且无法恢复。凭据工具会在所配置的环境中保存或清除 Git 登录信息。

安装

在 SourceWeft 中

  1. 打开 控制台中的 GitEasy MCP，将其添加到工作区。
  2. 连接 X-Api-Key 凭据。它们会被私密存储，绝不会在公开页面上展示。
  3. 为需要使用其工具的对话启用该服务。

Web executable，通过 Streamable HTTP。 远程服务在工作区中配置后即可从网页运行时运行。

交给智能体安装

把这段提示词粘贴到 Claude Code、Codex、Cursor 等智能体，或 SourceWeft 对话中。智能体会读取该服务器的安装指南，先向你展示发布者、端点和登录方式，经你同意后再把它添加到你的客户端。密钥不会写进任何命令。

阅读 https://sourceweft.com/mcp/io.github.greenmtnsun%2Fgiteasy/install.md，并按其中说明把这个 MCP 服务器接入我的客户端。修改任何配置之前，先告诉我它的发布者、端点和登录方式，等我确认。不要把 API 密钥写进命令或我会提交的文件；问我密钥应从哪里获取。

查看智能体所依据的安装指南

其他 MCP 客户端

把它添加到你客户端的 mcpServers 配置中。

{
  "mcpServers": {
    "giteasy": {
      "type": "http",
      "url": "https://giteasy-mcp.azurewebsites.net/mcp",
      "headers": {
        "X-Api-Key": "<YOUR_API_KEY>"
      }
    }
  }
}

README

GitEasy

[GitEasy — Plain-English Git for everyone who isn't a developer]

A PowerShell module that lets a Git-clueless person save and publish their work without learning Git jargon.

From Keith

I'm Keith Ramsey. For a living, I'm a SQL Server database administrator, and in my spare time, I'm a massive PowerShell enthusiast. For the past thirteen years, I've worked on the same team, quietly building internal tools to solve our specific headaches. GitEasy is a new chapter for me. It's the first tool I've ever released to the public, and honestly, the process of designing for strangers—polishing the code, writing in plain English just to be helpful—has been an absolute blast.

If you're checking out this module, I don't just hope you like it—I hope it gives you a sense of relief. I'll admit it: Git used to scare me. I've messed up commits, walked away from my desk in frustration, and told myself I'd figure it out tomorrow. While full-time developers breeze through Git, I work alongside DBAs, compliance teams, and change managers. We're the folks who just want our old TFS check-ins back. Git isn't just a tool; it's a whole new vocabulary filled with traps.

For a long time, we managed to avoid it. But eventually, the mandate came down: Git is here, learn it. Sitting there, feeling like I was studying for a final exam just to save a file, the concept for GitEasy clicked. What if we could strip away the jargon? What if checking in code didn't require an entirely new vocabulary?

Enter GitEasy. Just five simple commands. No confusing raw Git text. One log file per action. It's a frictionless wrapper—if you know Git, you can bypass it anytime. If you don't, you'll never need to see the scary stuff.

One important note: for now, I'm the only one making changes to GitEasy. Setting up the right legal paperwork to accept code changes from other people involves a lawyer, and I'd rather put my time and money into shipping more useful code than into legal forms I might have to redo. It's not a permanent stance; I'm just taking it slow. But rest assured, GitEasy is licensed under MPL 2.0, which means anyone is free to pick up the code and continue with it on their own. The project's survival doesn't depend on me.

I completely understand if that decision gives you pause. I'm just a guy figuring out the open-source world one step at a time. The door isn't bolted, it's just closed for today. I am fully open to bug reports and feature ideas — head to the GitHub project and open an Issue, tell me what you need, and I'll read it. No code necessary. If you want to chat, find me at @greenmtnsun on GitHub.

If you've ever closed PowerShell because the Git error message felt scarier than the change you were trying to save: this was built for you. I hope it brings some relief — and that you enjoy using it. Take care.

Notes

Short status notes from Keith. Newest at top. Edit / extend as the project moves.

2026-05-22 — Direction for CI and AI-agent users has its own page

Added docs/USING-IN-CI-AND-AGENTS.md. It's a single contract for anyone who wants to use GitEasy from a CI pipeline (GitHub Actions, Azure Pipelines, GitLab) or an AI coding agent. Deliberately does not ask consumers to run my own test suite or jargon audit — those are my quality bars, not theirs.

2026-05-22 — Contribution door is closed for now

No CLA in place; I'm not investing in legal until there's a real reason to. Bug reports as Issues are welcome. PRs won't be reviewed. When that changes, this note will say so.

2026-05-21 — v1.5.3 staged, holding the PowerShell Gallery publish

1.5.3 is feature-complete, manifest-ready (icon, in-repo LicenseUri, inline plaintext release notes, 14 audience-tagged keywords), and the .nupkg builds cleanly with per-doc PDFs included. I'm holding the actual PSGallery publish until I decide whether to flip the repo to public. The first outside user (Tycro) is installing from a private-repo clone right now — that's working fine.

2026-05-20 — Security review pass complete (v1.5.2)

Three credential-surface findings closed (F-04 / F-05 / F-06) covering sibling-pattern bugs the 1.5.1 review missed. Full kill-test suite added in Tests/GitEasy.AuthHardening.Tests.ps1. If you're using GitEasy with a credential helper, you want at least 1.5.2.

What it gives you

A small set of plain-English commands. The complicated stuff stays inside the engine; what you see and type stays simple.

powershell
Find-CodeChange         # What has changed?Save-Work 'fix readme'  # Save and publish in one step.Show-History            # Recent saved points.Show-Remote             # Where this folder is published.

When something goes wrong, you get a plain-English message and a path to a self-contained log file with the technical detail. No raw Git output is ever shown to the user.

Install

Friend-fast install (PS 5.1 and PS 7, no admin needed):

powershell
$Edition = if ($PSVersionTable.PSEdition -eq 'Core') { 'PowerShell' } else { 'WindowsPowerShell' }$ModuleDir = Join-Path $HOME "Documents\$Edition\Modules\GitEasy"git clone https://github.com/greenmtnsun/GitEasy.git $ModuleDirImport-Module GitEasy

That drops GitEasy into your user-scope PowerShell module folder (which is on $env:PSModulePath by default), so Import-Module GitEasy works from anywhere. See docs/HOW-TO-USE-GITEASY.md for the offline-install path and all-users scope.

Once a PowerShell Gallery release lands, the install becomes:

powershell
Install-Module GitEasy -Scope CurrentUser

The PowerShell Gallery page (when published) will be at powershellgallery.com/packages/GitEasy.

Quickstart

powershell
# In any folder that is already a Git repo:Find-CodeChangeSave-Work 'first save'Show-History -Count 5

If the repo has not been published anywhere yet, Save-Work will tell you so and save locally. When you connect a published location later, the next Save-Work will publish everything you have saved up to that point.

The full command surface

CommandWhat it does
Find-CodeChangeShow what has changed in your project folder.
Save-WorkSave changes and publish them (or save locally with -NoPush).
Show-HistoryShow recent saved points.
Show-RemoteShow where the project folder is published.
Show-DiagnosticOpen or list the diagnostic log files.
New-WorkBranchStart a new working area for an isolated task.
Switch-WorkSwitch to another existing working area.
Restore-FileRestore a single file to its last saved state.
Undo-ChangesThrow away unsaved changes (requires -Force or -Confirm).
Clear-JunkList or remove obvious temporary files.
Test-LoginVerify connectivity to the published location.
Set-TokenConfigure HTTPS-based login.
Set-SshConfigure SSH-based login.
Set-VaultChoose where saved logins are stored.
Get-VaultStatusReport the configured credential helper.
Reset-LoginForget the saved login so it can be set up again.

Each command has full comment-based help — Get-Help <Command> -Full for the friendly version.

Diagnostic logs

Every public command writes a small log file under %LOCALAPPDATA%\GitEasy\Logs. Successful runs log silently. Failures throw a plain-English message and tell you the log path so a Git-aware person can read what happened.

powershell
Show-Diagnostic           # Open the most recent log.Show-Diagnostic -List     # List recent logs.Show-Diagnostic -All      # Open the logs folder.

Logs older than 30 days are pruned automatically.

Documentation

The full documentation lives in the GitHub Wiki. Every public command has its own page with synopsis, examples, safety notes, and a related-commands cross-reference. Every private helper has a similar page for maintainers.

Compatibility

  • Windows PowerShell 5.1+
  • PowerShell 7+ (Windows; cross-platform may work but is not the design target)
  • Git must be installed and on PATH.

Running GitEasy from a CI job or an AI agent? See docs/USING-IN-CI-AND-AGENTS.md — one-page contract for consumers.

Status

GitEasy is at 1.5.3 — feature-complete public surface (21 commands), 569 Pester tests on both PowerShell hosts, and full plain-English contract.

See CHANGELOG.md for the history.

Contributing

GitEasy is maintained by a single author and is not currently accepting outside pull requests — no contributor agreement is in place. Bug reports as Issues are welcome.

The author's quality bar (test discipline, no-jargon rule, diagnostic-log session pattern) is documented in CONTRIBUTING.md for transparency.

License

Mozilla Public License 2.0. File-level copyleft: anyone can use, modify, and embed this code in proprietary or open projects, but modifications to GitEasy's own files must be released under MPL-2.0.

Author

Keith Ramsey (@greenmtnsun).

来源：README.md，提交 ced9265

工具

22

push

Send already-committed work to the remote without making a new commit. Pushes the current branch; on a branch's first push, sets the remote branch as its upstream automatically.

输入参数remoteNameworkingDirectory

show_diagnostic

Show git repository diagnostic info: current branch, upstream, HEAD SHA, remote URLs, and status summary.

输入参数workingDirectory

set_vault

Configure the git credential helper to use a specific vault path. Returns new credential helper value.

输入参数vaultPathworkingDirectory

restore_file

Restore a single file to its HEAD state, discarding uncommitted changes. Returns restored file path.

输入参数filePathworkingDirectory

reset_login

Clear stored git credentials by unsetting the credential helper in local git config. Returns confirmation.

输入参数workingDirectory

set_ssh

Change a remote URL to its SSH equivalent. Returns old and new remote URLs.

输入参数sshUrlremoteNameworkingDirectory

save_work

Stage changes, commit with a message, and optionally push to remote. Returns commit SHA and push result.

输入参数filesmessagepushToRemoteworkingDirectory

get_vault_status

Report current git credential helper configuration. Returns helper name and scope.

输入参数workingDirectory

test_login

Test whether git credentials are working by attempting ls-remote against the origin. Returns success/failure and remote refs count.

输入参数remoteNameworkingDirectory

show_releases

List all tags/releases in the repository, newest first. Returns tag names, target SHAs, and annotation messages.

输入参数workingDirectory

show_change

Show the diff for a specific file or all changed files. Returns unified diff text.

输入参数stagedfilePathworkingDirectory

new_release

Create an annotated git tag and push it to the remote. Returns the tag name and target commit SHA.

输入参数messagetagNameremoteNameworkingDirectory

find_changes

List changed files: staged, unstaged, and untracked. Returns file counts and paths by status group.

输入参数workingDirectory

show_remote

Show all remote names and their fetch/push URLs. Returns list of remotes with URL and type.

输入参数workingDirectory

get_updates

Fetch from remote and show incoming commits not yet in local branch. Returns count and commit summaries.

输入参数remoteNameworkingDirectory

undo_changes

Discard uncommitted changes. If filePath given, restores that file; otherwise restores all tracked files. Returns list of restored paths.

输入参数filePathworkingDirectory

switch_work

Switch to an existing branch. Returns the branch switched to and current HEAD SHA.

输入参数branchNameworkingDirectory

search_history

Search commit history for commits whose message matches a search term. Returns matching commits with SHA, author, date, and message.

输入参数limitsearchTermworkingDirectory

show_history

Show recent commit history. Returns commits with SHA, author, date, and message.

输入参数limitbranchNameworkingDirectory

new_work_branch

Create a new branch from current HEAD and switch to it. Returns branch name and base commit SHA.

输入参数branchNameworkingDirectory

set_token

Store a personal access token for HTTP git authentication. Returns confirmation (token value is never echoed).

输入参数tokenworkingDirectory

clear_junk

Remove untracked files and directories from the working tree (git clean -fd). Returns list of removed paths.

输入参数workingDirectory

版本历史

2
  1. v1.6.2最新Oct 25, 2026
  2. v1.6.1Sep 16, 2026

评分

已满足适用检查项的 100%

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

  • 近 30 天内可连通必需25 分
  • 已声明认证方式必需10 分
  • 已列出工具必需15 分
  • 描述必需15 分
  • 图标10 分
  • 文档15 分
  • 许可证10 分