GitEasy MCP Server

by greenmtnsun Your server? Claim it

answering

GitEasy MCP is answering right now. Last checked 13 min ago. It exposes 22 tools. Last commit 25 Oct 2026.

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

Uptime history 91 days of history · worst day 99%

91 days agonow

100.0%

Uptime 24h

91 of 91 checks

Tools

read from the server

697 ms

Response time

average over 24h

Stars

last commit 25 Oct 2026

What changed 1

Every tool that appeared, vanished or quietly changed what it asks for. Recorded since 10 August 2026. No other catalogue keeps this.

9 Aug a tool changed version

Nothing serious here today

Today is the operative word: we check GitEasy MCP every 15 minutes and re-read its code on every release. Watch it and you find out the day that stops being true.

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 13 min ago.

Claude Code Claude Desktop Codex Cursor VS Code

run in your terminal

claude mcp add giteasy --transport http https://giteasy-mcp.azurewebsites.net/mcp

Settings → Connectors → Add custom connector, then paste this address

https://giteasy-mcp.azurewebsites.net/mcp

~/.codex/config.toml

[mcp_servers.giteasy]
url = "https://giteasy-mcp.azurewebsites.net/mcp"

.cursor/mcp.json

{
  "mcpServers": {
    "giteasy": {
      "url": "https://giteasy-mcp.azurewebsites.net/mcp"
    }
  }
}

.vscode/mcp.json

{
  "servers": {
    "giteasy": {
      "type": "http",
      "url": "https://giteasy-mcp.azurewebsites.net/mcp"
    }
  }
}

Available tools 22

Read directly from the server with tools/list, grouped by what they act on. If a tool disappears, we record the date.

show

show_change

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

show_diagnostic

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

show_history

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

show_releases

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

show_remote

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

new

new_release

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

new_work_branch

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

vault

get_vault_status

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

set_vault

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

changes

find_changes

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

clear

clear_junk

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

history

search_history

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

push

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.

reset

reset_login

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

restore

restore_file

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

save

save_work

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

ssh

set_ssh

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

switch

switch_work

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

test

test_login

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

token

set_token

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

undo

undo_changes

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

updates

get_updates

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

Endpoints

URL	Transport	State	Latency	Checked
https://giteasy-mcp.azurewebsites.net/mcp	streamable-http	answering	717 ms	13 min ago

Alternatives to GitEasy MCP

same job, measured the same way

commit-check MCP

by commit-check

Commit policy as code for AI agents: check commit messages, branch names and authors before a push

155 installs/wk local only

VerifyUK Property Check

by namnam57

Cited English property planning-constraint screening and batch tools for AI agents.

answering

nlqdb — analytical memory for AI agents

by nlqdb

Analytical memory for AI agents: a real Postgres queried in plain English over MCP. One command.

answering

Hexis

by bevel-software

Git-backed platform for skills, tools, and context for AI agents

answering

JKTJJ MCP Server

by jktjj

BJJ gym, coach, event, and city data for AI agents. Free base tools, x402-paid premium.

13 tools answering

Htag Docs

by htagai

Public HTAG discovery for MCP tools, API endpoints, OpenAPI ops, and agents.

8 tools answering

Quartermaster

by surewhynot-quartermaster

x402 toolkit for AI agents: paid web, AI, and Base chain tools per call in USDC. Free tools too.

49 tools answering

MCP Git Enhanced

by davidweb3-ctrl

Enhanced Git MCP Server - Code review, commit analysis, and branch management

64 installs/wk local only

GitEasy MCP — questions

Answers built from our own checks of this server.

What can GitEasy MCP do?

It exposes 22 tools, read directly from the server on our last check. Among them: clear_junk, find_changes, get_updates, get_vault_status, new_release, new_work_branch and 16 more. The full list with descriptions is on this page — we take it from the server itself via tools/list, not from a README. How MCP servers expose tools in the first place →

What is GitEasy MCP mostly used for?

Its tools cluster around show, vault and new. That is what this server is built to work with — the grouping comes from the actual tool names, not from a category we assigned.

Is GitEasy MCP working right now?

We send a real MCP handshake every 15 minutes. Over the last 24 hours 91 of 91 checks got a reply (100.0%), average response time 697 ms. The bar chart above shows every period we have measured.

How do I connect GitEasy MCP?

Copy the ready config from this page. We generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each in the form that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address.

Does GitEasy MCP need an API key?

No. GitEasy MCP completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 22 of them are readable on this page. This is what we observed, not what the docs claim.

How fast is GitEasy MCP?

It answers our handshake in 697 ms on average, which is faster than 13% of all working MCP servers we measure. That is on the slow side — worth knowing if the tool sits inside an interactive loop. The comparison comes from our own checks across the whole registry, every 15 minutes.

Is GitEasy MCP open source?

The code is open source: it is published under the MPL-2.0 licence, written in PowerShell and 1 stars on GitHub. The licence covers the code in the repository, not the hosted service at giteasy-mcp.azurewebsites.net, which runs on its operator's own terms.