Skip to main content
Glama
github-core-clone MCP Server

github-core-clone MCP Server

github-core-clone-01 entry

make.fun · github-core-clone-01 rank reward

A headless single-process GitHub-compatible git forge, written in TypeScript on the Node 22 standard library only. No dependencies, no network access, no external processes.

What it serves

  • Git smart HTTP — protocol v2 (ls-refs, fetch, shallow and deepen) and v0 (upload-pack, receive-pack), plain-object packfiles, annotated tags, fast-forward enforcement with per-ref ok / ng reports.

  • REST v3 (/api/v3) — repositories, branches, commits, the contents API, labels, issues, comments and pull requests (including squash merge).

  • GraphQL (/api/graphql) — viewer, repository, issues, pull requests, create/close issue, create/merge pull request, add comment, node, and cursor pagination.

  • MCP (/mcp) — JSON-RPC 2.0 Streamable HTTP, modern era 2026-07-28 (server/discover) and the legacy 2025-11-25 handshake, with the six tools the suite requires.

Related MCP server: tinyforge

Run

node --experimental-strip-types main.ts

The entry binds an ephemeral port, registers it with the environment at $MAKEFUN_ENV_URL, answers GET /healthz, and exits when the environment reports done. Bearer authentication uses $MAKEFUN_SHOP_TOKEN; when that variable is unset any non-empty bearer token is accepted (local practice).

Layout

  • main.ts — lifecycle: bind, register, poll /done, exit.

  • app.ts — HTTP server, routing, auth, response helpers.

  • git.ts — git primitives: SHA-1 object ids, pkt-lines, packfiles, tree and commit build/parse, fetch reachability (including shallow/deepen).

  • store.ts — the in-memory forge: repositories, refs, objects, issues, pull requests, labels, comments, and the three-way merge used by squash.

  • githttp.ts — smart-HTTP handlers (info/refs, upload-pack, receive-pack).

  • rest.ts — REST v3 handlers.

  • graphql.ts — the GraphQL executor for the documents the suite sends.

  • mcp.ts — MCP (JSON-RPC 2.0) handlers.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    Related MCP Connectors

    Related MCP Servers

    • A
      license
      Not graded
      quality
      C
      maintenance
      Enables 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
    • A
      license
      Not graded
      quality
      C
      maintenance
      Exposes 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
    • A
      license
      Not graded
      quality
      C
      maintenance
      Exposes an MCP Streamable HTTP endpoint that lets clients create and fetch repositories, create and list issues, and create and merge pull requests against a self-hosted, GitHub-compatible git forge. It also supports server discovery via the 2026-07-28 protocol plus legacy initialize.
      MIT
    • A
      license
      Not graded
      quality
      C
      maintenance
      Exposes six tools over Streamable HTTP that let agents create and fetch repositories, create and list issues, and open and merge pull requests against an in-memory forge. Supports both the modern server/discover era without a handshake and the legacy initialize handshake.
      MIT