github-core-clone
Implements Git smart HTTP so standard Git clients can clone, fetch, pull, push, and perform shallow clones against the forge.
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-core-clone
A standalone GitHub-compatible git forge in one process: git smart HTTP, REST v3, GraphQL and MCP, backed by its own in-memory object store. No UI, no outside service, no proxy, no git binary — the packfile codec, the three-way merge, the GraphQL executor and the MCP dispatcher are all hand-written on the Node.js standard library.
Built for the make.fun bounty "Build a GitHub-compatible git forge".
Run
node main.tsNode 22.18+ (erasable TypeScript, no build step, no dependencies). In trial
mode the process binds an ephemeral port, registers with
$MAKEFUN_ENV_URL/register, serves until $MAKEFUN_ENV_URL/done reports
done, then exits 0. Without MAKEFUN_ENV_URL it serves in dev mode on
$PORT (or an ephemeral port) until interrupted. MAKEFUN_SHOP_TOKEN is
the bearer token clients must present; MAKEFUN_TRIAL_NOW fixes every
timestamp the forge reports.
Related MCP server: teamsync
Layout
File | What it does |
| Process entrypoint: bind, register, poll |
| HTTP routing, auth, request ids, JSON error envelope. |
| Smart HTTP: info/refs, upload-pack (v2 + v0), receive-pack. |
| Object model, pkt-lines, pack read/write, fetch planning. |
| In-memory repos, refs, issues, pulls, merges, diffs. |
| REST v3: repos, branches, commits, contents, labels, issues, pulls. |
| GraphQL lexer/parser/executor, introspection, mutations, batching. |
| MCP: |
| Deterministic viewer identity derived from the published scenario seed. |
What works
Git smart HTTP. Protocol v2 advertisement,
ls-refs(peel, symrefs, unborn, ref-prefix filtering),fetch(wants/haves, shallow/deepen,blob:none/blob:limitfilters, unshallow), protocol v0 fetch (side-band-64k, ACK/NAK, noreadyline), and receive-pack with per-ref fast-forward enforcement,report-status, sideband reports and delete-refs. Packs are read with OFS/REF delta resolution and written as plain-object version 2 packs with verified checksums. Verified against the realgitCLI: clone, push, fetch, shallow clone.REST v3. Repo CRUD with pagination (
Link: rel="next"), branches, commit listing, contents read/write/delete (409 on stale sha, branch auto-fork on PUT), git refs, labels, issues (state/sort/direction, comments, label validation with 422), pull requests (files diff, squash merge, 405 on conflict). GitHub-shaped error bodies and theX-GitHub-Request-Idheader on every reply.GraphQL.
viewer,repository,node(id:)with fragments,__typeintrospection, issue/PR connections with cursor pagination, and thecreateIssue,closeIssue,createPullRequest,mergePullRequestandaddCommentmutations. Unknown fields return HTTP 200 witherrorsnaming the field. Batched arrays answer in order.MCP. Modern
server/discoverera and legacyinitializeera, a frozentools/list(byte-identical across calls), and the six toolscreate_repo,get_repo,create_issue,list_issues,create_pull_request,merge_pull_request, with REST parity.Determinism. No wall clock (all timestamps come from
MAKEFUN_TRIAL_NOW), no unseeded randomness, packs sorted by oid.
What does not work
No persistence. State lives in memory; a restart loses every repo. (The graded trials run one process per trial, so this is by design.)
No UI and no webhooks. The forge is API-only, as specified.
No merge methods other than squash via the merge endpoint; rebase and merge commits are not implemented.
No auth model beyond one bearer token. Every repo belongs to the login the token names; organizations, collaborators, teams, stars, forks, releases, actions, search and the Checks API are not implemented.
No pack deltas on write. Outgoing packs carry plain objects only; this is legal on the wire and keeps output deterministic, at the cost of larger pack bytes on big clones.
No
gitbinary compatibility beyond smart HTTP. The dumb protocol,git://and SSH transports are out of scope.GraphQL is a fixed-schema executor, not a general engine: no subscriptions, no
@skip/@includeevaluation, no custom scalars, and only the documented types and fields resolve.
Tests
npm testtests/smoke.test.ts boots the real server and exercises REST, GraphQL,
MCP and a full git clone / git push / git pull round trip with the
system git client. The kit's own conformance suite can be run against a
live server with node --experimental-strip-types sdk/run.ts --url http://127.0.0.1:PORT --token TOKEN --perf from the kit directory.
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
AI-native git hosting — repos, PRs, issues, CI gates, and AI code review over MCP (60 tools).
One MCP server for all your MCP servers: code mode, per-tool permissions, approvals and audit.
GitHub Copilot MCP: code, repo, PR, workflow tools for AI assistants.
A MCP server built for developers enabling Git based project management with project and personal…
Related MCP Servers
- AlicenseNot gradedqualityBmaintenanceMCP server providing maximum practical control over GitHub via REST and GraphQL APIs, exposing 22 tools for repository management, file operations, issues, PRs, Actions, and more.MIT
- AlicenseNot gradedqualityBmaintenanceEnables AI tools to drive role-aware Git collaboration through nine MCP tools, including starting tasks, staging/committing/pushing changes, submitting pull requests with GitHub-native auto-merge, checking status, syncing, and listing team rosters.MIT
- AlicenseNot gradedqualityCmaintenanceEnables MCP clients to initialize, list tools, and invoke GitHub-compatible operations over streamable HTTP in a self-contained git forge.MIT
- AlicenseNot gradedqualityCmaintenanceEnables MCP clients to create and inspect repositories, push and clone code, and manage issues and pull requests, including merging, through JSON-RPC tools with defined input schemas and modern/legacy handshakes.MIT