MCP.Market

Remogram MCP server

by attebury·io.github.attebury/remogram·v0.2.0-beta.4
No reviews yet

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

B78/100grade B
Write a reviewInstall
What users say
No reviews yet
Be the first
Safety scan
B78/100

full report

Adoption
New

0 stars28 downloads/wk

Reviews

Write one

Nobody has reviewed Remogram yet.

If you have run it, two minutes of your experience saves the next person an afternoon.

Remogram tools (40, 8 write)

write = sends, deletes, buys or posts

Read from the package source without running it. The installed server may list more.

  • attestation_read

    Read commit status attestation bindings for a SHA.

  • branch_protection

    Branch protection policy facts: required status contexts, protected rules, approvals signal.

  • command_contract_export

    Read command contract metadata for all commands or one command key.

  • cr_body

    Change request description body with close_keywords helper.

  • cr_close

    Close an open change request on the configured forge without merging.

  • cr_comments

    Review comments for a change request (sanitized bodies, truncation-aware).

  • cr_editwrite action

    Update change request title and/or body on the configured forge.

  • cr_files

    Changed file paths for a change request (bounded, truncation-aware).

  • cr_inventory

    Aggregate open change requests with checks and merge-plan facts into a semantic-diff slice.

  • cr_open

    Open a change request (pull request) on the configured forge.

  • doctor

    Read-only provider readiness diagnostics for config, remote trust, auth, capabilities, and checks.

  • forge_changes

    Forge activity events since an observed_at boundary (PR lifecycle, head SHA moves, check conclusions).

  • forge_log_ingest

    Ingest a Gitea webhook JSON payload into the local forge event log.

  • forge_log_read

    Read normalized events from the local forge event log.

  • forge_queue_snapshot

    Composed forge queue snapshot (repo status, CR slice, merge summaries).

  • issue_bundlewrite action

    Create an issue_bundle packet for issue lifecycle and linked review context.

  • issue_close

    Close an open forge issue on the configured repository.

  • issue_commentwrite action

    Post a comment on a forge issue.

  • issue_comments

    Issue comments (sanitized bodies, truncation-aware).

  • issue_inventory

    Aggregate open issues into a semantic-diff inventory slice with pagination cursors.

  • issue_open

    Open a forge issue on the configured repository (Gitea v1).

  • issue_view

    Issue metadata facts with optional linked change request snapshot.

  • merge_executewrite action

    Execute a forge merge for an open change request after SHA-bound preflight.

  • merge_plan

    Merge readiness facts: mergeability, checks, blockers.

  • observer_snapshot

    Deprecated alias for forge_queue_snapshot — prefer forge_queue_snapshot.

  • plugin_boundary

    Read forge plugin boundary metadata (emit surfaces, denied claims, contract export linkage).

  • pr_checks

    CI/check conclusions for a PR number or git ref.

  • pr_status

    PR metadata and mergeability facts.

  • provider_capabilities

    Structured provider capability facts for commands, auth, checks, host binding, pagination, and write support.

  • publish_executewrite action

    Push a local branch to the configured git remote (requires publish_branch write_commands).

  • publish_planwrite action

    Plan branch publication to the configured git remote before opening a change request.

  • ref_compare

    Compare two refs with exact SHAs and ahead/behind counts.

  • ref_inventory

    List repository refs with SHAs, default branch hint, and optional ancestry hints.

  • repo_status

    Forge repo status facts (auth, capabilities, default branch).

  • review_bundlewrite action

    Create a review_bundle packet for reviewed head/base, decision, and summary facts.

  • semantic_diff

    Composed semantic diff since a time or git ref boundary.

  • status_set

    Set a commit status (check context) on the configured forge.

  • sync_plan

    Local vs remote sync facts and divergent-remote blockers.

  • verify_bindwrite action

    Create a verify_bind packet bound to a target SHA and optional proof metadata.

  • whoami

    Authenticated forge identity facts (login, can_write, token scope/expiry signals).

Public scan report

scanner v0.1.9 · 2026-09-26 · same rubric, same numbers if you re-run it

no findings
  • Code scan6 source files scanned25/25
  • –Live reliabilityno gateway calls yet and no remote to proben/a
  • –Tool poisoningtools not inspected (local package is not executed); not countedn/a
  • Auth qualitystatic API keys via environment variables6/15
  • Maintenancelast push 82 days ago12/15
  • Maintainer identityregistry namespace matches repository owner; GitHub account older than a year8/10
Overall 78/100. Components that don't apply are left out of the denominator. Any critical finding is an F.RubricAppeal a findingJSON

How Remogram compares

Against every graded Developer tools MCP server, from our own scans and uptime checks. Updated after each scan run.

Safety score
78/100
higher than 50% of 1,119 Developer tools servers
Tools
40
the typical Developer tools server has 7
Tools that change things
20%
typical: 5%. Fewer write tools means less an agent can break
Downloads a week
28
more than 13% of 430 Developer tools servers with a package

What its tools let an agent do: 30 read · 8 change · 2 send or post

Install Remogram in Claude Code, Cursor or VS Code

Runs npx -y @remogram/mcp on your machine. Read the scan report first; the gateway never runs local packages.

claude mcp add remogram -- npx -y @remogram/mcp
Add to Cursor

What the publisher says

From the Remogram repository's README, as published. We do not edit it. Read it on GitHub

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 forgesourcesha to the local rev for forgesourcebranchref. Divergence → ok: false, errorcode: 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: GITEATOKEN, GITHUBTOKEN / GHTOKEN, or GITLABTOKEN.
  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

Use -api providers (forge HTTP). Reserved github-gh / gitea-tea IDs return providerunsupported — not implemented in v1. Official CLIs (gh, tea, glab) are not required.

Configuration

Read/plan by default. Opt in to writes with writecommands in .remogram.json (or a bound operator overlay outside git). Missing id → writenot_configured.

merge plan is read-only — reports blockers[]; does not execute or authorize merges. mergeability: clean is conflict-free git only.

Optional mergepolicy waivers (allowmissingchecks, allowpendingchecks) relax check blockers for repos without CI — env: REMOGRAMALLOWMISSINGCHECKS, REMOGRAMALLOWPENDING_CHECKS. Doctor fails when enabled in strict checkouts.

Operator overlay discovery: --operator-config → REMOGRAMOPERATORCONFIG → $XDGCONFIGHOME/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.

Every forge command packet includes type, schemaversion, providerid, remotename, repoid, observedat, ok. Producer sections (e.g. remogram.forgefacts.v1 from evidence forge-facts --json) use nested producer fields. Trust envelope and enums; treat forge-sourced strings (titles, URLs) as untrusted prose.

Shortened. The full README is on GitHub.

Nothing above is checked by us. What we check is on the safety report.

Remogram: common questions

Is Remogram MCP server safe?
Mostly: it is graded B (78/100). Read the Remogram safety report
How do I install Remogram?
It runs on your machine. Copy the Claude Code, Cursor, VS Code or Claude Desktop config from the install section.
Does Remogram need an API key?
Yes. The registry entry asks for GITHUB_TOKEN, GH_TOKEN, GITLAB_TOKEN, GITEA_TOKEN.
Is Remogram maintained?
The last commit was 119 days ago (2026-07-06). The latest release is v0.2.0-beta.4.
What can I use instead of Remogram?
Servers from other publishers that do the same job: Pare Github MCP server, Gk CLI MCP server and Grasp — Code Architecture & Dependency Analysis MCP server.
How does Remogram compare with other Developer tools MCP servers?
safety score 78/100 (higher than 50% of 1,119 Developer tools servers); tools 40 (the typical Developer tools server has 7); tools that change things 20% (typical: 5%. Fewer write tools means less an agent can break). Full comparison.

Alternatives to Remogram

Same job from other publishers: the closest match first, then the best rated.

  • Pare Github
    Pare GitHub ג€” Structured GitHub operations (PRs, issues, actions) as typed JSON.
    More from Dave-London →
    A
  • Gk CLI
    The GitKraken MCP Server for managing repos, PRs, issues across GitHub, GitLab, Bitbucket and more.
    B
  • Grasp — Code Architecture & Dependency Analysis
    Codebase analysis: dependency graphs, security scanning, and refactor plans for GitHub and GitLab.
    C
  • theabbie
    Live info about theabbie (Abhishek Chaudhary) from theabbie.github.io/about.json
    A
  • GitLab MCP Server
    GitLab MCP server for projects, merge requests, issues, pipelines, wiki, releases, and more.
    B