GitEasy MCP

Name: GitEasy MCP
Author: greenmtnsun

by greenmtnsunversion 1.6.2i★ –iRuns in the cloud

Registry nameio.github.greenmtnsun/giteasy

Install

Overview

Description from the maker (original English)

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

PopNx MCP’s three pillars

These three are never merged into one score: opinions, measurements and popularity are different things.

User voiceiNo reviews yetReviews open together with accounts in a later step
Our basic checksi3 of 3 passedChecked from public information; code not scanned yet
UsageiNot measured yet★ –

What you can do with it

We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.

Connection: Runs in the cloud
Transport: Streamable HTTP
Category: Developer tools
You need to fill in: X-Api-Key

Install

Pick the AI app you use, then copy the settings.

Before you install

Basic checks: 3 of 3 passed
Runs on the maker’s server: what you ask it goes through their server.
Can do 22 things (tools) push, show_diagnostic, set_vault, restore_file …
You fill in yourself: X-Api-Key

Values marked secret are keys to your account. Never share them or paste them into a chat.

You need

Runs in the cloudNothing to install; it connects over the internet

Which app do you use?

ClaudeClaude CodeCursorVS CodeChatGPT

Pick your app above. We remember it, so next time the button says “Install in …”.

This address needs a key in a request header, which the add-connector menu cannot set. Use Claude Code, Cursor or VS Code instead.

Run this in your terminal

claude mcp add --transport http giteasy https://giteasy-mcp.azurewebsites.net/mcp --header 'X-Api-Key: your-value'

Fill in the empty values before running it.

Open in Cursor

Or copy the settings yourself

Paste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json

{
  "mcpServers": {
    "giteasy": {
      "url": "https://giteasy-mcp.azurewebsites.net/mcp",
      "headers": {
        "X-Api-Key": "your-value"
      }
    }
  }
}

Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.

Open in VS Code

Or copy the settings yourself

Paste into .vscode/mcp.json in your project

{
  "servers": {
    "giteasy": {
      "type": "http",
      "url": "https://giteasy-mcp.azurewebsites.net/mcp",
      "headers": {
        "X-Api-Key": "your-value"
      }
    }
  }
}

Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.

This address needs a key in a request header, which the add-connector menu cannot set. Use Claude Code, Cursor or VS Code instead.

Your choice stays on this device in a cookie; no account needed.

Values you fill in

X-Api-Key secret required HTTP header
Free key (500 write calls/month) at https://detentpoint.com/giteasy

These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.

What it can do

Tool names and descriptions exactly as the server reported them on Nov 7, 2026. The maker wrote them, not us; we show them as plain text.

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.
show_diagnostic
Show git repository diagnostic info: current branch, upstream, HEAD SHA, remote URLs, and status summary.
set_vault
Configure the git credential helper to use a specific vault path. Returns new credential helper value.
restore_file
Restore a single file to its HEAD state, discarding uncommitted changes. Returns restored file path.
reset_login
Clear stored git credentials by unsetting the credential helper in local git config. Returns confirmation.
set_ssh
Change a remote URL to its SSH equivalent. Returns old and new remote URLs.
save_work
Stage changes, commit with a message, and optionally push to remote. Returns commit SHA and push result.
get_vault_status
Report current git credential helper configuration. Returns helper name and scope.
test_login
Test whether git credentials are working by attempting ls-remote against the origin. Returns success/failure and remote refs count.
show_releases
List all tags/releases in the repository, newest first. Returns tag names, target SHAs, and annotation messages.
show_change
Show the diff for a specific file or all changed files. Returns unified diff text.
new_release
Create an annotated git tag and push it to the remote. Returns the tag name and target commit SHA.
find_changes
List changed files: staged, unstaged, and untracked. Returns file counts and paths by status group.
show_remote
Show all remote names and their fetch/push URLs. Returns list of remotes with URL and type.
get_updates
Fetch from remote and show incoming commits not yet in local branch. Returns count and commit summaries.
undo_changes
Discard uncommitted changes. If filePath given, restores that file; otherwise restores all tracked files. Returns list of restored paths.
switch_work
Switch to an existing branch. Returns the branch switched to and current HEAD SHA.
search_history
Search commit history for commits whose message matches a search term. Returns matching commits with SHA, author, date, and message.
show_history
Show recent commit history. Returns commits with SHA, author, date, and message.
new_work_branch
Create a new branch from current HEAD and switch to it. Returns branch name and base commit SHA.
set_token
Store a personal access token for HTTP git authentication. Returns confirmation (token value is never echoed).
clear_junk
Remove untracked files and directories from the working tree (git clean -fd). Returns list of removed paths.

Basic checksi

We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 7, 2026

✓ Pass
Maker matches the repo
The registry name was verified with the GitHub account greenmtnsun, which owns the repo
… Not checked yet
Still maintained
We have not read this repo from GitHub yet
… Not checked yet
Has a licence
We have not read this repo from GitHub yet
✓ Pass
Endpoint responds
Responded in 272 ms (HTTP 200)
– Not applicable
Sign-in with OAuth
No sign-in needed
✓ Pass
No hidden instructions in tool descriptions
Read 22 tool descriptions and found no hidden instructions to the AI

Compared with others in Developer toolsi

More stars than 0% of the other 4900 servers in this category
Published to the registry more recently than 73% of the other 4900 servers in this category
Basic checks equal to or better than 100% of the other 4900 servers in this category

Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.

Common questions

Is GitEasy MCP safe?

It passed 3 of 3 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.

What keys or codes does it need?

You need to fill in: X-Api-Key

Does it run on my computer or in the cloud?

It runs in the maker’s cloud. Connect over the internet with nothing to install, but what you send passes through the maker’s servers.

Is it still maintained?

The GitHub repo last changed –, and the latest version (1.6.2) reached the registry 13 days ago.

Which apps can use it?

Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. It connects by URL, so apps that accept remote MCP servers work too, such as ChatGPT in developer mode.

What can I use instead?

In the same category: GitHub, Desktop Commander, Cloudflare MCP

Alternatives

Servers in the same category from other makers, sorted by stars.

Reading a card:★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi

GitHub

by github

GitHub’s official server lets AI read and manage code, issues and pull requests in your account. Use GitHub’s hosted version or run it locally with Docker.

Computer or cloud★ 34,245MITUpdated 4 days ago

Install

Desktop Commander

by wonderwhy-er

MCP server for terminal commands, file operations, and process management

Runs on your computer★ 10,225MITUpdated 16 days ago

Install

Cloudflare MCP

by cloudflare

Cloudflare MCP servers

Runs in the cloud★ 4,446Apache-2.0Updated 14 months ago

Install

README from the maker

Open the README

Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.

GitEasy

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.

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):

$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 $ModuleDir Import-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:

Install-Module GitEasy -Scope CurrentUser

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

Quickstart

# In any folder that is already a Git repo:

Find-CodeChange Save-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

Command	What it does
`Find-CodeChange`	Show what has changed in your project folder.
`Save-Work`	Save changes and publish them (or save locally with `-NoPush`).
`Show-History`	Show recent saved points.
`Show-Remote`	Show where the project folder is published.
`Show-Diagnostic`	Open or list the diagnostic log files.
`New-WorkBranch`	Start a new working area for an isolated task.
`Switch-Work`	Switch to another existing working area.
`Restore-File`	Restore a single file to its last saved state.
`Undo-Changes`	Throw away unsaved changes (requires `-Force` or `-Confirm`).
`Clear-Junk`	List or remove obvious temporary files.
`Test-Login`	Verify connectivity to the published location.
`Set-Token`	Configure HTTPS-based login.
`Set-Ssh`	Configure SSH-based login.
`Set-Vault`	Choose where saved logins are stored.
`Get-VaultStatus`	Report the configured credential helper.
`Reset-Login`	Forget the saved login so it can be set up again.

Each command has full comment-based help — Get-Help -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.

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).

GitEasy MCP

Overview

PopNx MCP’s three pillars

What you can do with it

Install

Before you install

Values you fill in

What it can do

Basic checksi

Maker matches the repo

Still maintained

Has a licence

Endpoint responds

Sign-in with OAuth

No hidden instructions in tool descriptions

Compared with others in Developer toolsi

Common questions

Alternatives

GitHub

Desktop Commander

Cloudflare MCP

README from the maker

GitEasy

From Keith

Notes

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

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

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

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

What it gives you

Install

Quickstart

The full command surface

Diagnostic logs

Documentation

Compatibility

Status

Contributing

License

Author