github-forge
Serves Git smart HTTP for cloning, fetching, pushing, shallow clones/deepening, tags, and packfile transfer, allowing standard Git clients to interact with the forge.
Provides a GitHub-compatible forge with repositories, branches, commits, contents, refs, issues, comments, pull requests, labels, and squash merges, exposed through REST v3, GraphQL, and MCP tools.
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 git forge (make.fun bounty github-core-clone-01)
A single Node.js process (stdlib only, no dependencies, no install step) that serves
git smart HTTP at /{owner}/{repo}.git, REST v3 at /api/v3, GraphQL at
/api/graphql, and MCP at /mcp, from its own in-memory store. Entry point is
main.ts (Node 22+, run as node --experimental-strip-types main.ts); it binds an
ephemeral port, POSTs {port} to $MAKEFUN_ENV_URL/register, then long-polls
$MAKEFUN_ENV_URL/done until the trial ends and exits 0.
Layout
main.ts— entry lifecycle (starter, unchanged): register + poll/done.app.ts— HTTP server: routing, auth, body reading, JSON/git responses.src/store.ts— in-memory store (repos, issues, pulls, comments, labels), deterministic timestamps fromMAKEFUN_TRIAL_NOW+ sequence, vieweradaiversen(id 1000).src/gitobjs.ts— SHA-1 objects, pack read/write (v2, full objects + OFS/REF delta resolve on read), pkt-lines, trees/commits, fetch collection, tag peeling.src/githttp.ts— v0/v2 advertisements, v2 ls-refs, v0/v2 fetch, receive-pack + sideband report.src/rest.ts— full REST v3 (repos, branches, commits, contents, refs, issues, comments, pulls + squash merge).src/graphql.ts— GraphQL: tokenizer + parser, validator, executor, introspection, opaque global ids, cursor pagination, all five mutations, batching.src/mcp.ts— MCP Streamable HTTP:server/discover(2026-07-28 + legacyinitialize), 6 tools (create_repo,get_repo,create_issue,list_issues,create_pull_request,merge_pull_request).test/— smoke test, real-gitCLI test, conformance runners, saved results.
Related MCP server: github-mcp-bridge
Auth
One bearer token (MAKEFUN_SHOP_TOKEN) is the viewer's. REST/GraphQL/MCP always
require it. Git reads of a public repo need no token (GitHub behaviour); private-repo
reads and all pushes require it. A missing repo is 404 on git endpoints regardless
of auth.
Protocol notes (verified against real git 2.43 and the kit's git-client)
Push report: report pkt-lines + flush inside the band-1 sideband data, then a bare flush — without the inner flush real git reports "the remote end hung up".
v2 fetch sections are emitted only when they carry content:
acknowledgmentsonly when the client sent haves (withACKlines + areadyline — withoutready, real git errors "expected no other sections to be sent after no 'ready'"),shallow-infoonly with shallow/unshallow lines, nowanted-refs, alwayspackfile.Shallow boundary = the deepest included commit generation, never the first excluded one.
deepen N: absolute depth per the kit client; treated as an increment when the request only re-asks already-held shallow boundaries with N no deeper than the current depth (real git--deepen).Incremental fetches never re-send objects reachable from the client's haves.
Annotated tags push as
tagobjects, peel to their commit in ls-refs/advertisements, and round-trip through fetch packs.
Local results (15 Nov 2026, this machine)
test/smoke.mjs— all checks pass (REST, GraphQL, MCP, protocol).test/git-cli.mjs— realgit2.43: clone (empty / with history / shallow / deepen), push, fetch, tags, non-fast-forward refusal, wrong-token refusal, 1 MiB file — all pass.Kit conformance
sdk/run.ts --perf— 120/120 checks, feature 600, agent 200, perf 118–126 across runs, total 918–923 (test/results/conformance-sdk-run.json).Sealed env harness
sdk/conformance/main.ts(register +/donelifecycle) — 120/120, perf 160 points, total 960 (test/results/conformance-env-state.json,test/results/conformance-env-perf.json). The house reference scores 120/120 with ~100 perf points (~900 total), so this entry beats it on performance.
License
MIT — see LICENSE.
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
A MCP server built for developers enabling Git based project management with project and personal…
Create, deploy, and operate MCP servers directly from your GitHub repositories.
Remote MCP server exposing SMI Aware tools, resources, and skills over Streamable HTTP.
Host any HTTP API as a standard MCP server; auto-distribute to 12+ mainstream agent platforms.
Related MCP Servers
- FlicenseNot gradedqualityDmaintenanceProfile-driven MCP server for safely inspecting and changing local Git repositories via a Streamable HTTP endpoint with deny-by-default security.1-
- AlicenseNot gradedqualityBmaintenanceA lightweight MCP server that exposes GitHub operations as tools over HTTP, enabling any MCP-compatible client to interact with GitHub repositories without a built-in connector.1MIT
- AlicenseAqualityBmaintenanceEnables MCP clients to read a Forgejo, Codeberg, or Gitea instance—including users, repositories, issues, pull requests, search, notifications, comments, reviews, and Actions runs—with opt-in, time-boxed guarded writes for repository, branch, issue, pull request, comment, migration, push-mirror, and workflow operations.592MIT
- AlicenseNot gradedqualityCmaintenanceEnables GitHub-compatible repository, issue, and pull request management over JSON-RPC 2.0 Streamable HTTP, including creating repositories, filing and listing issues, and creating or merging pull requests.MIT