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)
SCM & forge boundary MCP: normalized, typed JSON from attributed Gitea, GitLab, and GitHub providers
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.
GITHUB_TOKEN, GH_TOKEN, GITLAB_TOKEN, GITEA_TOKEN, REMOGRAM_CWD, REMOGRAM_OPERATOR_CONFIGValues marked secret are keys to your account. Never share them or paste them into a chat.
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": {
"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"
}
}
}
}Run this in your terminal
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/mcpFill in the empty values before running it.
Paste into .cursor/mcp.json in your project, or ~/.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"
}
}
}
}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": {
"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"
}
}
}
}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.
REMOGRAM_CWD envREMOGRAM_OPERATOR_CONFIG envThese 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 attebury, 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.
You need to fill in: GITHUB_TOKEN, GH_TOKEN, GITLAB_TOKEN, GITEA_TOKEN
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.2.0-beta.4) reached the registry 4 months ago.
Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. You also need Node.js 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.
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.