mcpbeat Sign in

Giteasy MCP Server

by greenmtnsun Your server? Claim it
answering

Giteasy is answering right now. Last checked 4 min ago. It exposes 22 tools.

Plain-English git via MCP: 22 tools to branch, commit, push, and tag. No git jargon.

The linked repository no longer exists on GitHub — it was deleted or made private.

Uptime history 47 days of history · worst day 99%
47 days agonow
100.0%
Uptime 24h
92 of 92 checks
22
Tools
read from the server
868 ms
Response time
average over 24h
open, no key
Access
streamable-http

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

This one has been quiet for a while

Quiet is not dead — but it is worth knowing when it wakes up, or when someone else takes it over. We watch the repository and tell you either way.

Three servers free · no card

Connect this server

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

run in your terminal
claude mcp add giteasy --transport http https://giteasy-mcp.azurewebsites.net/mcp
~/Library/Application Support/Claude/claude_desktop_config.json
{
  "mcpServers": {
    "giteasy": {
      "url": "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
{
  "mcpServers": {
    "giteasy": {
      "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

URLTransportStateLatencyChecked
https://giteasy-mcp.azurewebsites.net/mcp streamable-http answering 861 ms 4 min ago

Alternatives to Giteasy

same job, measured the same way
Git
by abhishekkumar2021

Local Git via MCP: status, log, diff, file history, branches, and gated stage/commit. Pure-JS.

59 installs/wk local only
MCP Git Enhanced
by davidweb3-ctrl

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

45 installs/wk local only
Git Enhanced
by davidweb3-ctrl

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

local only
commit-check MCP
by commit-check

Validate commit messages, branch names, author info, push safety, and repo state.

401 installs/wk local only
Rankparse MCP
by abhibavishi

SEO MCP server — backlinks, domain authority, tech stack, and 18+ tools via Common Crawl.

73 tools answering
skanfirmy.pl
by bartosz-kuc

Verify Polish companies by NIP/KRS/REGON + EU VAT (VIES). 14 MCP tools, no key.

14 tools answering
Xiaohongshu (Little Red Book) MCP Server
by shanyang-me

Publish, search, and manage Xiaohongshu (Little Red Book) content via MCP tools.

133 installs/wk local only
Pare Git
by dave-london

Pare Git ג€” Structured git operations (status, log, diff, branch, commit, push) as typed JSON.

172 installs/wk local only

Giteasy — questions

Answers built from our own checks of this server.

What can Giteasy 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 mostly used for?
Its tools cluster around show, new and vault. 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 working right now?
We send a real MCP handshake every 15 minutes. Over the last 24 hours 92 of 92 checks got a reply (100.0%), average response time 868 ms. The bar chart above shows every period we have measured.
Is Giteasy still maintained?
The linked repository no longer exists on GitHub — it was deleted or made private. We show this because it changes what you can expect: an unmaintained server may keep answering for months and then stop without warning.
How do I connect Giteasy?
Copy the ready config from this page — we generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each with the file path that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address.
Does Giteasy need an API key?
No. Giteasy 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?
It answers our handshake in 868 ms on average, which is faster than 12% 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.