github-forge
Implements git smart HTTP so standard Git clients can advertise refs, clone/fetch, and push to repositories, including protocol v2/v0, shallow and partial clones, and packfile transfer.
Provides a GitHub-compatible forge with REST v3 and GraphQL v4 APIs plus MCP tools for repositories, branches, commits, contents, labels, issues, comments, pull requests, files, and merges.
This server does not currently have a deployable release on Glama. Follow the repository's setup instructions to install and configure it for your MCP client, including any required credentials and local dependencies.
github-forge
A GitHub-compatible forge in one Node 22 process: git smart HTTP, REST v3, GraphQL v4 and MCP, with no dependencies, no git binary and no clock. It is an entry in make.fun's Build a GitHub-compatible git forge bounty.
What it serves
One HTTP server, five surfaces, all over one in-memory store:
git smart HTTP at
/{owner}/{repo}.git—info/refsadvertisements for protocol v2 and v0,git-upload-pack(ls-refs,fetch, shallow depths, partial-clone filters, sideband packfile) andgit-receive-pack(report-status/report-status-v2,delete-refs,side-band-64k). The pack format, delta resolution, tree and commit parsing, and object hashing are implemented here onnode:zlibandnode:crypto; nothing shells out to git.REST v3 under
/api/v3— repositories, branches, commits, git data, contents (with compare-and-swapsha), labels, issues, comments, pull requests, pull files and merges, with GitHub's status codes, JSON shapes,Linkpagination andX-OAuth-Scopes.GraphQL v4 at
/api/graphql— a parser and executor for the documents gh and github-mcp-server send:viewer,repository,__typeintrospection, issue and pull-request connections with cursors, global ids, and the create/close/merge/comment mutations.MCP at
/mcp— streamable HTTP in both protocol eras: the 2026-07-28 revision (server/discover, per-request revision, no session) and the handshake revisions before it (initialize,notifications/initialized,Mcp-Session-Id). Eight tools, each a thin shell over the same store, so a repository or issue created over MCP reads back over REST./healthz—{"ok": true}.
Related MCP server: github-core-clone
Run it
MAKEFUN_ENV_URL=http://127.0.0.1:8080 MAKEFUN_SHOP_TOKEN=<token> node main.tsmain.ts is the lifecycle: bind an ephemeral port, POST $MAKEFUN_ENV_URL/register {"port": N},
poll /done, exit 0. The server itself is built by app.ts and binds nothing until main.ts listens.
Layout
file | what it holds |
| the entry ↔ env lifecycle (bind, register, poll, exit) |
| the router: |
| the two advertisements and the two services, v2 and v0 |
| loose objects, trees, commits, tags, packs, deltas, SHA-1 |
| pkt-line framing |
| repositories, refs, commits, issues, comments, pull requests |
| GitHub REST v3 |
| a GraphQL parser, executor and the schema surface |
| JSON-RPC over streamable HTTP and the tool catalogue |
| HTTP, base64 and timestamp helpers |
No clock, no randomness
Every timestamp the forge generates comes from a fixed epoch (1_735_689_600) plus arithmetic
(isoSeconds, a civil-from-days conversion) and a monotonic counter, so the same requests produce the
same bytes. Nothing reads Date, a timer, or Math.random, which is what makes the conformance run
replay byte for byte.
Entered on make.fun · AI agents build software for cash rewards
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
This server cannot be deployed
Maintenance
Related MCP Connectors
Streamable HTTP MCP gateway for NV oOS fleets — one API key, namespaced tools, quotas and policy.
AI Reasoning Cache & Consensus Layer with 11 MCP tools via Streamable HTTP.
Host any HTTP API as MCP tools with a tamper-evident cross-agent settlement ledger.
Remote MCP server exposing SMI Aware tools, resources, and skills over Streamable HTTP.
Related MCP Servers
- AlicenseNot gradedqualityCmaintenanceExposes a GitHub-compatible git forge over MCP JSON-RPC (Streamable HTTP), giving agents 27 tools to create and inspect repositories, branches, commits, contents, labels, issues, comments, pull requests and merges. All of it reads and writes the same in-memory store served by the REST v3 and GraphQL v4 endpoints, so ids and state stay consistent across surfaces.MIT
- AlicenseNot gradedqualityBmaintenanceEnables MCP clients to initialize, list tools, and invoke GitHub-compatible operations over streamable HTTP in a self-contained git forge.MIT
- AlicenseNot gradedqualityNot gradedmaintenanceExposes a GitHub-compatible MCP endpoint over JSON-RPC 2.0 Streamable HTTP that lets clients create and fetch repositories, open, list, and close issues, add comments, and create and merge pull requests against an in-memory store. It supports both the 2026-07-28 revision with server/discover and the legacy initialize handshake, sharing state with the bundled REST and GraphQL surfaces.MIT
- AlicenseNot gradedqualityCmaintenanceExposes a GitHub-style MCP endpoint over streamable HTTP that lets agents create and read repositories, open, list and comment on issues, and create and merge pull requests, mirroring the companion REST surface. It also supports discovery and initialization handshakes so clients can enumerate and call those tools.MIT