Prototype · Preview: every server in the official registry, synced every 30 minutes. Reviews and accounts come in a later step.
PopNx MCPMCP servers for people who use AI · explained in plain words

Remogram

by atteburyversion 0.2.0-beta.4i★ –iRuns on your computer
Registry nameio.github.attebury/remogram

Install

Overview

Description from the maker (original English)

SCM & forge boundary MCP: normalized, typed JSON from attributed Gitea, GitLab, and GitHub providers

PopNx MCP’s three pillars

These three are never merged into one score: opinions, measurements and popularity are different things.

What you can do with it

We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.

  • Connection: Runs on your computer
  • Transport: stdio
  • Category: Developer tools
  • You need to fill in: GITHUB_TOKEN, GH_TOKEN, GITLAB_TOKEN, GITEA_TOKEN

Install

Pick the AI app you use, then copy the settings.

Before you install

  • Basic checks: 1 of 1 passed
  • Runs on your computer with your user’s permissions (files, network, apps).
  • You fill in yourself: GITHUB_TOKEN, GH_TOKEN, GITLAB_TOKEN, GITEA_TOKEN, REMOGRAM_CWD, REMOGRAM_OPERATOR_CONFIG

Values marked secret are keys to your account. Never share them or paste them into a chat.

You need

  • npmNode.js installed (for the npx command)

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/mcp

Fill in the empty values before running it.

Open in Cursor

Or copy the settings yourself

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.

Open in VS Code

Or copy the settings yourself

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.

Values you fill in

  • GITHUB_TOKEN secret env
    GitHub API token for github-api repositories.
  • GH_TOKEN secret env
    Alternative GitHub API token for github-api repositories.
  • GITLAB_TOKEN secret env
    GitLab API token for gitlab-api repositories.
  • GITEA_TOKEN secret env
    Gitea API token for gitea-api repositories.
  • REMOGRAM_CWD env
    Repository root for Remogram to inspect when the MCP host launches from another working directory.
  • REMOGRAM_OPERATOR_CONFIG env
    Optional path to a local operator write-command overlay.

These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.

What it can do

Runs on your computer; the tool list appears in your AI app after you install it.

Basic checksi

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

  • ✓ Pass

    Maker matches the repo

    The registry name was verified with the GitHub account attebury, which owns the repo

  • … Not checked yet

    Still maintained

    We have not read this repo from GitHub yet

  • … Not checked yet

    Has a licence

    We have not read this repo from GitHub yet

  • – Not applicable

    Endpoint responds

    This one runs on your computer; there is no internet endpoint

  • – Not applicable

    Sign-in with OAuth

    Runs on your computer and uses local settings instead

  • … Not checked yet

    No hidden instructions in tool descriptions

    Runs on your computer; we can only read tool lists from internet endpoints

Compared with others in Developer toolsi

  • More stars than 0% of the other 1392 servers in this category
  • Published to the registry more recently than 30% of the other 1392 servers in this category
  • Basic checks equal to or better than 100% of the other 1392 servers in this category

Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.

Common questions

Is Remogram safe?

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.

What keys or codes does it need?

You need to fill in: GITHUB_TOKEN, GH_TOKEN, GITLAB_TOKEN, GITEA_TOKEN

Does it run on my computer or in the cloud?

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).

Is it still maintained?

The GitHub repo last changed –, and the latest version (0.2.0-beta.4) reached the registry 4 months ago.

Which apps can use it?

Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. You also need Node.js on your computer.

What can I use instead?

In the same category: GitHub, Desktop Commander, Cloudflare MCP

Alternatives

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

by 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.

Computer or cloud★ 34,245MITUpdated 3 days ago
Install

Desktop Commander

by wonderwhy-er

MCP server for terminal commands, file operations, and process management

Runs on your computer★ 10,225MITUpdated 15 days ago
Install

Cloudflare MCP

by cloudflare

Cloudflare MCP servers

Runs in the cloud★ 4,446Apache-2.0Updated 14 months ago
Install

README from the maker

Open the README

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.

Remogram

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.

Install

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`.

Quick start

  1. Copy .remogram.json.example → .remogram.json (set provider, owner, repo; add baseUrl for self-hosted Gitea/GitLab).
  2. Export token: GITEA_TOKEN, GITHUB_TOKEN / GH_TOKEN, or GITLAB_TOKEN.
  3. Bootstrap:
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.

Providers

Forge"provider"Token env
Giteagitea-apiGITEA_TOKEN
GitHubgithub-apiGITHUB_TOKEN or GH_TOKEN
GitLabgitlab-apiGITLAB_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.

Configuration

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 idCommandNotes
cr_opencr openSeparate from merge
cr_closecr closeGitea lifecycle
mergemerge executeRequires --expected-base-sha / --expected-head-sha; not implied by cr_open
publish_branchpublish executeGit push to configured remote
status_setstatus setCommit status POST
issue / cr_edit idsmatching commandsSee 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.

Boundary and trust

Remogram emits forge facts only — no integration authority refs, lane roles, task ids, or handoff payloads in JSON.

ConceptPacket fieldNotes
PR baseforge_target_branch_refForge-reported
PR headforge_source_branch_refEvidence only
Default branchdefault_branchNot 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.

MCP

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.

Live verification

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.

Testing

npm test

npm run test:coverage npm run security:secrets -- --full-history

Coverage policy

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.

Packages

PackageRole
@remogram/cliCLI
@remogram/mcpMCP adapter
@remogram/coreEnvelope, config, caps
@remogram/provider-{gitea,github,gitlab}-apiSupported forge backends

Agent skills

npx skills add attebury/remogram --skill remogram-consumer -g -y (consumer) or --skill remogram-core (contributor). Skills ship from GitHub, not npm.

Contributing

See CONTRIBUTING.md.

Ask PopNx