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.
Description from the maker (original English)
Local git operations over MCP: status, diff, log, branches and commits.
These three are never merged into one score: opinions, measurements and popularity are different things.
We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.
Pick the AI app you use, then copy the settings.
You need
Which app do you use?
Pick your app above. We remember it, so next time the button says “Install in …”.
Open Claude Desktop → Settings → Developer → Edit Config, and paste this into claude_desktop_config.json
{
"mcpServers": {
"repoport": {
"command": "npx",
"args": [
"-y",
"@reneturcios/repoport",
"mcp"
]
}
}
}Run this in your terminal
claude mcp add repoport -- npx -y @reneturcios/repoport mcpPaste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json
{
"mcpServers": {
"repoport": {
"command": "npx",
"args": [
"-y",
"@reneturcios/repoport",
"mcp"
]
}
}
}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.
Paste into .vscode/mcp.json in your project
{
"servers": {
"repoport": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"@reneturcios/repoport",
"mcp"
]
}
}
}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 one runs on your computer, and ChatGPT can only connect to servers on the internet. Pick another app.
Your choice stays on this device in a cookie; no account needed.
These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.
Runs on your computer; the tool list appears in your AI app after you install it.
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 6, 2026
The registry name was verified with the GitHub account CloudCorpRecords, which owns the repo
We have not read this repo from GitHub yet
We have not read this repo from GitHub yet
This one runs on your computer; there is no internet endpoint
Runs on your computer and uses local settings instead
Runs on your computer; we can only read tool lists from internet endpoints
Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.
It passed 1 of 1 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.
The registry does not list a required key, though some servers ask you to sign in on first use.
It runs on your computer. Your AI app starts it when needed, and data does not pass through the maker’s servers (unless it calls an online service itself).
The GitHub repo last changed –, and the latest version (0.1.0) reached the registry 10 days ago.
Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. You also need Node.js, Docker on your computer.
In the same category: GitHub, Desktop Commander, Cloudflare MCP
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’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.
MCP server for terminal commands, file operations, and process management
Cloudflare MCP servers
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.
repoport gives an agent hands on a local git repository without giving it a shell. It covers the everyday loop — check status, read diffs, stage files, commit, read the log, inspect a revision, and move between branches — and it does so by calling the git CLI directly, with every argument passed as data rather than stitched into a shell string.
The repository path is checked before anything runs: it must exist and must be inside a git work tree. Revision-like values that begin with a dash are refused, so a branch name or revision cannot smuggle an extra git flag into a call.
npx @reneturcios/repoport status .
Or run the container image:
docker run -i ghcr.io/cloudcorprecords/repoport
The container defaults to the MCP server (see below). Pass CLI arguments to use it as a CLI instead. The image and the npm package both expect a git binary and access to the repository you point at; mount or run against a local checkout accordingly.
# Working tree status for a repository
repoport status ~/src/my-project
repoport log ~/src/my-project repoport log ~/src/my-project 25
repoport --version
Exit codes: 0 on success, 1 when git or the repository check fails (the error carries git's own message), 2 for usage errors.
One bin serves both faces. The mcp subcommand starts a stdio MCP server:
npx -y @reneturcios/repoport mcp
MCP client configuration:
{
"mcpServers": { "repoport": { "command": "npx", "args": ["-y", "@reneturcios/repoport", "mcp"] } } }
| Tool | Input | What it returns |
|---|---|---|
git_status | repo_path (required) | The long-form git status output for the repository. |
git_diff_unstaged | repo_path (required), context_lines (optional, default 3) | A unified diff of unstaged working-tree changes. |
git_diff_staged | repo_path (required), context_lines (optional, default 3) | A unified diff of changes staged for the next commit. |
git_diff | repo_path, target (both required), context_lines (optional) | A unified diff against the given target revision. |
git_add | repo_path, files (array of strings, both required) | Stages the named files; paths are passed after --. |
git_reset | repo_path (required) | Unstages everything (git reset), leaving working-tree edits in place. |
git_commit | repo_path, message (both required) | Commits whatever is currently staged with the given message. |
git_log | repo_path (required), max_count (optional, default 10), start_timestamp, end_timestamp (optional ISO strings) | Recent commits newest first; timestamp bounds are applied against each commit's author date. |
git_show | repo_path, revision (both required) | The git show output for that revision. |
git_create_branch | repo_path, branch_name (both required), base_branch (optional) | Creates a branch without switching to it. |
git_checkout | repo_path, branch_name (both required) | Switches the work tree to the named branch. |
git_branch | repo_path (required), branch_type (optional: local, remote or all, default local), contains, not_contains (optional) | Branch listing, optionally filtered to branches that contain or do not contain a commit. |
Every tool returns git's stdout as its text result. Failures — a missing path, a path that is not a repository, a git error, or a rejected dash-prefixed value — come back as tool errors carrying the underlying message.
execFile argument array.branch_name, target, revision, contains and not_contains values starting with - are rejected before git ever sees them.git_commit only commits what is already staged; it never stages on your behalf.npm install
npm run build # tsc -> dist/ npm test # node test runner over test/*.test.ts, no network npm run dev # run the CLI from source via tsx
Tests build a throwaway repository in a temp directory (initialising git and setting a local test identity there) and exercise the full loop against it, so they need a git binary on PATH but no network and no pre-existing checkout.
MIT — see LICENSE.