Developer · Local MCP server
Remogram
SCM & forge boundary MCP: normalized, typed JSON from attributed Gitea, GitLab, and GitHub providers.
What the MCP Registry states
The entry as published to the official MCP Registry (read 2026-10-04), latest version.
- Registry name
io.github.attebury/remogram- Version
- 0.2.0-beta.4
- Status
- Active
- Category
- developer
- Transport
- stdio (local process)
- Package
- npm
- Published
- 2026-07-04
- Updated
- 2026-07-04
- Publisher
- attebury (GitHub)
- Namespace
- Namespace verified by the MCP Registry via GitHub (github.com/attebury) · how
- Listed under
- GitHub MCP servers, GitLab MCP servers, Gitea MCP servers
- Repository
- github.com/attebury/remogram
- Source
- Registry API entry
Packages
| Registry | Package | Version | Transport |
|---|---|---|---|
| npm | @remogram/mcp | 0.2.0-beta.4 | stdio |
How to connect Remogram
Remogram runs locally from a Node.js package published to the npm registry: @remogram/mcp version 0.2.0-beta.4. It speaks MCP over stdio, so the client starts it as a program and talks to it through standard input and output. It needs Node.js; clients usually start it with npx - the usual command is npx -y @remogram/mcp@0.2.0-beta.4. It reads these environment variables: GITHUB_TOKEN (secret), GH_TOKEN (secret), GITLAB_TOKEN (secret), GITEA_TOKEN (secret), REMOGRAM_CWD and REMOGRAM_OPERATOR_CONFIG; set them in the client's configuration for this server.
In the mcpServers JSON format that many desktop and editor MCP clients read, the entry looks like this (placeholders in angle brackets):
{
"mcpServers": {
"remogram": {
"command": "npx",
"args": [
"-y",
"@remogram/mcp@0.2.0-beta.4"
],
"env": {
"GITHUB_TOKEN": "<secret>",
"GH_TOKEN": "<secret>",
"GITLAB_TOKEN": "<secret>",
"GITEA_TOKEN": "<secret>",
"REMOGRAM_CWD": "<value>",
"REMOGRAM_OPERATOR_CONFIG": "<value>"
}
}
}
}Derived from the registry entry, not tested here. What the server does, and on what terms, is set by its publisher; check its repository or website before giving it access to your accounts or files. How to add an MCP server to an assistant · Before you connect
More developer servers
| Server | Runs |
|---|---|
| RememLocal-first automatic memory for Claude Code and Codex: capture, distill, recall from SQLite. | Local · stdio |
| Remembra RelayCross-agent handoff: the next coding agent starts from the last one's facts, not a blank page. | Local · stdio |
| RemembrallMCPPersistent knowledge memory for AI agents. Hybrid search, code graph, pgvector. | Local · stdio |
| RemiApple Reminders CLI and MCP server with section support and iCloud sync. | Local · stdio |
| Remote AgentsControl fleets of remote machines via AI agents: exec, files, git, fleet ops, map/reduce. | Local · stdio |
| Remote BridgeSync code to remote servers via SSH/rsync and deploy from any AI IDE. | Local · stdio |
| Remote Browser MCP Server from MCPBundlesAutomate cloud Chrome-navigate, click, type, screenshot, run code, record screen video. | Remote · HTTPLive check: sign-in required |
| Remote FilesystemMCP server for remote filesystem operations on cloud storage (Google Cloud Storage). | Local · stdio |