GitHub
Connect AI assistants to GitHub - manage repos, issues, PRs, and workflows through natural language.
作者提供的说明(英文原文)
SCM & forge boundary MCP: normalized, typed JSON from attributed Gitea, GitLab, and GitHub providers
这三项永远不会合并成一个分数:意见、测量和人气是不同的东西。
我们还没有为它写通俗的介绍。下面是我们从注册中心读取到的事实。
选择你使用的 AI 应用,然后复制设置。
GITHUB_TOKEN, GH_TOKEN, GITLAB_TOKEN, GITEA_TOKEN, REMOGRAM_CWD, REMOGRAM_OPERATOR_CONFIG标为机密的值是你账户的钥匙。千万不要分享给别人,也不要粘贴到聊天里。
你需要
你用的是哪个应用?
在上方选择你的应用。我们会记住它,下次按钮会显示“安装到 …”。
打开 Claude Desktop → Settings → Developer → Edit Config,把下面的内容粘贴到 claude_desktop_config.json
{
"mcpServers": {
"remogram": {
"command": "npx",
"args": [
"-y",
"@remogram/mcp"
],
"env": {
"GITHUB_TOKEN": "your-value",
"GH_TOKEN": "your-value",
"GITLAB_TOKEN": "your-value",
"GITEA_TOKEN": "your-value",
"REMOGRAM_CWD": "your-value",
"REMOGRAM_OPERATOR_CONFIG": "your-value"
}
}
}
}在终端中运行这条命令
claude mcp add remogram --env GITHUB_TOKEN=your-value --env GH_TOKEN=your-value --env GITLAB_TOKEN=your-value --env GITEA_TOKEN=your-value --env REMOGRAM_CWD=your-value --env REMOGRAM_OPERATOR_CONFIG=your-value -- npx -y @remogram/mcp运行前请先填写空着的值。
粘贴到项目中的 .cursor/mcp.json,或 ~/.cursor/mcp.json
{
"mcpServers": {
"remogram": {
"command": "npx",
"args": [
"-y",
"@remogram/mcp"
],
"env": {
"GITHUB_TOKEN": "your-value",
"GH_TOKEN": "your-value",
"GITLAB_TOKEN": "your-value",
"GITEA_TOKEN": "your-value",
"REMOGRAM_CWD": "your-value",
"REMOGRAM_OPERATOR_CONFIG": "your-value"
}
}
}
}浏览器会先询问是否打开应用,然后应用会显示设置并请你确认。密钥的值会留空,由你自己填写。
粘贴到项目中的 .vscode/mcp.json
{
"servers": {
"remogram": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"@remogram/mcp"
],
"env": {
"GITHUB_TOKEN": "your-value",
"GH_TOKEN": "your-value",
"GITLAB_TOKEN": "your-value",
"GITEA_TOKEN": "your-value",
"REMOGRAM_CWD": "your-value",
"REMOGRAM_OPERATOR_CONFIG": "your-value"
}
}
}
}浏览器会先询问是否打开应用,然后应用会显示设置并请你确认。密钥的值会留空,由你自己填写。
这个服务器在你的电脑上运行,而 ChatGPT 只能连接互联网上的服务器。请选择其他应用。
你的选择通过 Cookie 保存在这台设备上,无需账户。
REMOGRAM_CWD envREMOGRAM_OPERATOR_CONFIG env这些设置是根据作者在注册中心的条目生成的。如果 README 的写法不同,请以 README 为准。
它在你的电脑上运行;安装后,工具列表会显示在你的 AI 应用中。
我们检查的是任何人都能看到的信息;我们没有阅读代码。不适用的检查项不计入总数。 · 检查于 2026年11月7日
注册名称已通过 GitHub 账户 attebury 验证,该账户拥有此仓库
我们还没有从 GitHub 读取这个仓库
我们还没有从 GitHub 读取这个仓库
它在你的电脑上运行,没有互联网端点
在你的电脑上运行,改用本地设置
它在你的电脑上运行;我们只能读取互联网端点的工具列表
与注册中心里这个分类中所有活跃的服务器比较。只有当发布者拥有该仓库时,星标数才计入。
它在 1 项适用的基础检查中通过了 1 项。我们没有阅读代码。在添加密钥或令牌之前,请先看看这个服务器要求哪些权限,并使用只具备所需权限的密钥。
你需要填写:GITHUB_TOKEN, GH_TOKEN, GITLAB_TOKEN, GITEA_TOKEN
它在你的电脑上运行。你的 AI 应用会在需要时启动它,数据不会经过作者的服务器(除非它自己调用在线服务)。
GitHub 仓库最后更新于–,最新版本(0.2.0-beta.4)于4个月前进入注册中心。
支持 MCP 的应用,例如 Claude Desktop、Claude Code、Cursor 和 VS Code。你的电脑上还需要有 Node.js。
同一分类中有:GitHub, Desktop Commander, Cloudflare MCP
同一分类中其他作者的服务器,按星标数排序。
如何看卡片:★ 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
Cloudflare MCP servers
按原文从作者的仓库复制。PopNx MCP 没有审查或背书其内容。HTML、图片和脚本已被移除。链接会离开本站。
Generic SCM/forge boundary CLI and MCP server. Emits provider-attributed JSON facts — git-resolved refs from local git (refs compare, sync plan) vs forge-reported PR SHAs from forge APIs (pr view, pr checks). No workflow or planning-tool concepts in output.
PR-by-number reconciliation: pr view / pr checks compare forge-reported forge_source_sha to the local rev for forge_source_branch_ref. Divergence → ok: false, error_code: stale_head — git fetch, not a forge outage.
Planning tools interpret intent and workflow authority outside Remogram.
npm install -g @remogram/cli @remogram/mcp
remogram --version remogram version --json
Legacy preview (frozen @beta, optional): npm install -g @remogram/cli@beta @remogram/mcp@beta
Development checkout: clone this repo, npm ci, ./scripts/npm-link.sh. Default branch: `main`.
.remogram.json.example → .remogram.json (set provider, owner, repo; add baseUrl for self-hosted Gitea/GitLab).GITEA_TOKEN, GITHUB_TOKEN / GH_TOKEN, or GITLAB_TOKEN.remogram doctor --json
remogram provider capabilities --json remogram repo status --json remogram pr view --number 1 --json remogram merge plan --number 1 --json
Command catalog: `remogram contract --json`. Agent skill: npx skills add attebury/remogram --skill remogram-consumer -g -y.
| Forge | "provider" | Token env |
|---|---|---|
| Gitea | gitea-api | GITEA_TOKEN |
| GitHub | github-api | GITHUB_TOKEN or GH_TOKEN |
| GitLab | gitlab-api | GITLAB_TOKEN |
Use ***-api providers (forge HTTP). Reserved `github-gh` / `gitea-tea` IDs return `provider_unsupported` — not implemented in v1. Official CLIs (`gh`, `tea`, `glab`) are not** required.
Read/plan by default. Opt in to writes with `write_commands` in .remogram.json (or a bound operator overlay outside git). Missing id → write_not_configured.
| Write id | Command | Notes |
|---|---|---|
cr_open | cr open | Separate from merge |
cr_close | cr close | Gitea lifecycle |
merge | merge execute | Requires --expected-base-sha / --expected-head-sha; not implied by cr_open |
publish_branch | publish execute | Git push to configured remote |
status_set | status set | Commit status POST |
issue / cr_edit ids | matching commands | See contract --json |
`merge plan` is read-only — reports blockers[]; does not execute or authorize merges. mergeability: clean is conflict-free git only.
Optional `merge_policy` waivers (allow_missing_checks, allow_pending_checks) relax check blockers for repos without CI — env: REMOGRAM_ALLOW_MISSING_CHECKS, REMOGRAM_ALLOW_PENDING_CHECKS. Doctor fails when enabled in strict checkouts.
Operator overlay discovery: --operator-config → REMOGRAM_OPERATOR_CONFIG → $XDG_CONFIG_HOME/remogram/operator/ - - .json. `bind` must match forge identity.
Remogram emits forge facts only — no integration authority refs, lane roles, task ids, or handoff payloads in JSON.
| Concept | Packet field | Notes |
|---|---|---|
| PR base | forge_target_branch_ref | Forge-reported |
| PR head | forge_source_branch_ref | Evidence only |
| Default branch | default_branch | Not integration authority |
Every forge command packet includes type, schema_version, provider_id, remote_name, repo_id, observed_at, ok. Producer sections (e.g. `remogram.forge_facts.v1` from evidence forge-facts --json) use nested producer fields. Trust envelope and enums; treat forge-sourced strings (titles, URLs) as untrusted prose.
Inventory commands (refs inventory, cr inventory, whoami, branch protection, cr files, forge changes, …) extend read/plan — details in `remogram contract --json` and the consumer skill references.
Stdio server `remogram-mcp` delegates to the CLI — same JSON as remogram … --json. Setup: examples/mcp/README.md. Set REMOGRAM_CWD to the consumer repo root.
Cross-forge fixture repo: [remogram-smoke](https://gitlab.com/attebury/remogram-smoke) (mirrors on GitHub/Gitea). Use --json packets after install; monorepo smoke-compare scripts are dev-only.
npm test
npm run test:coverage npm run security:secrets -- --full-history
npm run test:coverage instruments `@remogram/core` only; `@remogram/cli`, `@remogram/mcp`, and **@remogram/provider-* are excluded. Thresholds:** none — no enforced percentage gates. Drift guard: tests/core/coverage-config.test.mjs.
CI (GitHub): .github/workflows/ on push/PR to main.
| Package | Role |
|---|---|
@remogram/cli | CLI |
@remogram/mcp | MCP adapter |
@remogram/core | Envelope, config, caps |
@remogram/provider-{gitea,github,gitlab}-api | Supported forge backends |
npx skills add attebury/remogram --skill remogram-consumer -g -y (consumer) or --skill remogram-core (contributor). Skills ship from GitHub, not npm.
See CONTRIBUTING.md.