GitHub
Connect AI assistants to GitHub - manage repos, issues, PRs, and workflows through natural language.
作者提供的说明(英文原文)
Local git operations over MCP: status, diff, log, branches and commits.
这三项永远不会合并成一个分数:意见、测量和人气是不同的东西。
我们还没有为它写通俗的介绍。下面是我们从注册中心读取到的事实。
选择你使用的 AI 应用,然后复制设置。
你需要
你用的是哪个应用?
在上方选择你的应用。我们会记住它,下次按钮会显示“安装到 …”。
打开 Claude Desktop → Settings → Developer → Edit Config,把下面的内容粘贴到 claude_desktop_config.json
{
"mcpServers": {
"repoport": {
"command": "npx",
"args": [
"-y",
"@reneturcios/repoport",
"mcp"
]
}
}
}在终端中运行这条命令
claude mcp add repoport -- npx -y @reneturcios/repoport mcp粘贴到项目中的 .cursor/mcp.json,或 ~/.cursor/mcp.json
{
"mcpServers": {
"repoport": {
"command": "npx",
"args": [
"-y",
"@reneturcios/repoport",
"mcp"
]
}
}
}浏览器会先询问是否打开应用,然后应用会显示设置并请你确认。密钥的值会留空,由你自己填写。
粘贴到项目中的 .vscode/mcp.json
{
"servers": {
"repoport": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"@reneturcios/repoport",
"mcp"
]
}
}
}浏览器会先询问是否打开应用,然后应用会显示设置并请你确认。密钥的值会留空,由你自己填写。
这个服务器在你的电脑上运行,而 ChatGPT 只能连接互联网上的服务器。请选择其他应用。
你的选择通过 Cookie 保存在这台设备上,无需账户。
这些设置是根据作者在注册中心的条目生成的。如果 README 的写法不同,请以 README 为准。
它在你的电脑上运行;安装后,工具列表会显示在你的 AI 应用中。
我们检查的是任何人都能看到的信息;我们没有阅读代码。不适用的检查项不计入总数。 · 检查于 2026年11月8日
注册名称已通过 GitHub 账户 CloudCorpRecords 验证,该账户拥有此仓库
我们还没有从 GitHub 读取这个仓库
我们还没有从 GitHub 读取这个仓库
它在你的电脑上运行,没有互联网端点
在你的电脑上运行,改用本地设置
它在你的电脑上运行;我们只能读取互联网端点的工具列表
与注册中心里这个分类中所有活跃的服务器比较。只有当发布者拥有该仓库时,星标数才计入。
它在 1 项适用的基础检查中通过了 1 项。我们没有阅读代码。在添加密钥或令牌之前,请先看看这个服务器要求哪些权限,并使用只具备所需权限的密钥。
注册中心没有列出必需的密钥,不过有些服务器会在首次使用时要求你登录。
它在你的电脑上运行。你的 AI 应用会在需要时启动它,数据不会经过作者的服务器(除非它自己调用在线服务)。
GitHub 仓库最后更新于–,最新版本(0.1.0)于11天前进入注册中心。
支持 MCP 的应用,例如 Claude Desktop、Claude Code、Cursor 和 VS Code。你的电脑上还需要有 Node.js, Docker。
同一分类中有:GitHub, Desktop Commander, Cloudflare MCP
同一分类中其他作者的服务器,按星标数排序。
如何看卡片:↓ 每周下载量i★ GitHub 星标i三大支柱:评价 · 检查 · 使用情况i更新 = 最新版本发布到注册中心的时间i
Connect AI assistants to GitHub - manage repos, issues, PRs, and workflows through natural language.
MCP server for terminal commands, file operations, and process management
按原文从作者的仓库复制。PopNx MCP 没有审查或背书其内容。HTML、图片和脚本已被移除。链接会离开本站。
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.