github-core-clone
Implements git smart-HTTP (protocol v2), enabling standard Git operations such as upload-pack and receive-pack for pushing and pulling code.
Provides a complete clone of the GitHub core surface, including REST v3 resources for managing repositories, issues, pull requests, and content, as well as GraphQL v4 endpoints.
Exposes a GraphQL v4 API endpoint for querying and manipulating the repository and project data.
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 from-scratch implementation of the GitHub core surface for
the contest: git smart-HTTP (protocol v2,
upload-pack and receive-pack), the REST v3 resources, GraphQL v4 and an MCP endpoint, all in one
Node process built on the standard library only — no dependencies, no git binary, no install
step. main.ts carries the entry lifecycle the harness drives the server with.
Run it
node --experimental-strip-types main.tsThe platform runs node /bot/main.ts on Node 22.18 or later, which strips TypeScript types on its
own; the flag is harmless there and makes an older local Node work too. There is nothing to install:
the program imports node:http and its own app.ts only, and the trial has no package manager and
no internet.
Related MCP server: github-mcp-bridge
The lifecycle (main.ts)
The env is a server the harness starts beside yours. Its origin is in MAKEFUN_ENV_URL
(http://store:8080 in a trial).
Bind an ephemeral port.
server.listen(0)lets the kernel pick one; read it withserver.address().port. Never bind 8080: that is the env's port, and on the one-pod layout it is on the same loopback.Register.
POST $MAKEFUN_ENV_URL/registerwith{"port": <the port you bound>}, as JSON. The env records the address the request came from plus that port as your base URL and dials it from then on. The first register wins: a later one is answered409and does not move the base URL.Wait for done.
GET $MAKEFUN_ENV_URL/doneanswers at once with{"done":false}while the suite runs and{"done":true}once its export is written. Poll it with a short backoff; never hold a request open, and never exit before it saystrue.Exit 0 when it does. Closing the server first is tidy; the harness stops the env afterwards, and the env's export is what the scorer reads.
A failed poll or register is retried with a short exponential backoff. If MAKEFUN_ENV_URL is unset
there is nothing to talk to, so main.ts exits 1 at once.
The surface the contest scores
Route | What it is |
| 200 |
| 200, |
| GitHub REST v3: repositories, branches, commits, contents, issues, comments, labels, pull requests, files, merges |
| GitHub GraphQL v4: the documents |
| Model Context Protocol over streamable HTTP: initialize, tools/list, tools/call |
| git smart HTTP: |
anything else | 404 |
The env presents every API call with Authorization: Bearer $MAKEFUN_SHOP_TOKEN (the same token is
in your environment); /healthz is the boot probe and takes none. Whether a missing or a wrong token
is refused is part of the protocol checks, not of this starter.
The score is feature + agent + perf (0..1000): the conformance checks over that surface, the MCP
checks again as the agent-native column, and four timed workloads. The version of the suite the trial
runs is in the kit under program/, so you can grade the same checks locally before you submit.
Rules and limits
The rules, the scoring weights, the deadline and the prizes are on the contest page:
https://make.fun/bounty/github-core-clone-01 (its Rules section). In short: Node 22 only, no
dependencies at run time, no internet and no git binary in the trial; your repository is mounted
read-only at /bot and you may write under /tmp only. The env at MAKEFUN_ENV_URL is the service
you answer; the model gateway, if your entry calls a model, is the only other endpoint it can reach.
The trial's CPU, memory and process limits are the rules'; its wall budget is 900 seconds.
Layout
main.ts: the lifecycle above.app.ts: HTTP routing and the REST v3 resources.src/:git/(object store, packfiles, smart-HTTP transport),graphql.ts,mcp.ts,pulls.ts,scenario.ts,store.ts(the in-memory store).test/: unit tests and a dev server for local runs.package.json,tsconfig.json,LICENSE(MIT): the entry's metadata and licence.
This entry is MIT licensed; see LICENSE.
Built by Puectjeck for the make.fun bounty — https://make.fun/r/g4gqv254
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.
Streamable HTTP MCP gateway for NV oOS fleets — one API key, namespaced tools, quotas and policy.
One MCP server for all your MCP servers: code mode, per-tool permissions, approvals and audit.
Related MCP Servers
- AlicenseNot gradedqualityDmaintenanceEnables Git repository operations and real-time monitoring via MCP tools, with support for WebSocket events, authentication, and observability.13 npm4MIT
- 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
- 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 gradedqualityBmaintenanceExposes GitHub-compatible operations over MCP, letting agents create and inspect repositories, issues, pull requests, and file contents against a shared in-memory forge store that stays consistent with the same server's REST, GraphQL, and git smart HTTP surfaces.MIT