github-core-clone-01
Provides Git smart HTTP endpoints for clone/fetch and push, supporting upload-pack v2 features such as ls-refs, fetch, shallow deepen, and thin packs, plus receive-pack v0 with a SHA-1 object model and non-fast-forward rejection.
Emulates GitHub's core APIs for repositories, branches, commits, refs, contents, labels, issues, comments, and pull requests, including squash merges with conflict detection, exposed through REST v3, GraphQL v4, and MCP tools.
Exposes a GraphQL API with viewer/repository queries, node lookup, introspection, cursor-paginated issue and pull request connections, and mutations for creating/closing issues, creating/merging pull requests, and adding comments.
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-01
Note: the rank/reward badge URLs above still carry the placeholders
Dhaniels033/makefun-github-core-clone-01— replace them with the real GitHub owner and repository name once the repository is created.
An entry for make.fun's github-core-clone-01 competition — a from-scratch, standard-library-only clone of GitHub's core: git smart HTTP, REST v3, GraphQL v4 and MCP, in a single Node process with an in-memory store.
What it serves
Git smart HTTP —
git-upload-packv2 (ls-refs,fetch, incl. shallowdeepenand thin-pack handling) andgit-receive-packv0, with a full SHA-1 object model (commit/tree/blob/tag), pack read (OFS/REF deltas) and pack write (no deltas), sideband framing, and non-fast-forward refusal.REST v3 under
/api/v3— repos (CRUD, pagination), branches, commits, git refs, contents (create/update/delete with blob-sha checks), labels, issues + comments, pull requests (create, files, squash merge with conflict detection).GraphQL at
/api/graphql—viewer,repository(incl. issues/PR connections with cursor pagination),node,__typeintrospection, and thecreateIssue/closeIssue/createPullRequest/mergePullRequest/addCommentmutations, plus batched operations.MCP at
/mcp— streamable HTTP,server/discover+initialize, and toolscreate_repo,get_repo,create_issue,list_issues,create_pull_request,merge_pull_request(plusget_issue,create_comment), mirroring the REST surface.
Related MCP server: tinyforge
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. There is nothing to install: the program imports
node:http, node:crypto and node:zlib only, and the trial has no package
manager and no internet.
The lifecycle (in main.ts, unchanged from the starter):
Bind an ephemeral port.
server.listen(0); never bind 8080 (the env's port).Register.
POST $MAKEFUN_ENV_URL/registerwith{"port": <port>}.Poll
GET $MAKEFUN_ENV_URL/doneuntil{done: true}, then exit 0.
Every API call carries Authorization: Bearer $MAKEFUN_SHOP_TOKEN;
missing/wrong token → 401. /healthz takes no auth.
Determinism
State is derived from a logical clock seeded by MAKEFUN_TRIAL_NOW
(falling back to 2025-01-01T00:00:00Z), advancing one second per created
object — no Date.now() or randomness in responses — so a live pass and its
replay leave byte-identical state.
The scenario's viewer login is adaiversen (id 1000, adaiversen@example.invalid).
That is the deterministic viewer the kit's sealed wire.ts derives from its
constant scenario seed (SCENARIO_SEED = 0x6a09e667f3bcc909n), verified by
running the kit's own buildScenario(); it is hardcoded in app.ts.
Local verification
Kit's own grader, practice trial 0, --driver process:
node cli/makefun.mjs grade-local --kit . \
--bot ~/workspace/makefun-work/entries/github-core-clone-01 \
--driver process --worktree --instances 1Result (2026-11-16, three runs): feature 600/600 (120/120 checks),
agent 200/200 (15/15 MCP), perf 120–173/200 depending on machine load
(the grading VM was heavily loaded during the later runs; the first run
scored 958/1000). Live pass exited 0 and its replay matched byte for byte
in every run. grade-local --driver docker was not run: Docker is not
available on this machine.
Files
main.ts— lifecycle (register / poll / exit), unchanged from the starter.app.ts— the whole server (git, REST, GraphQL, MCP).package.json,tsconfig.json,LICENSE(MIT)..makefun/owner.json— owner's linked Solana wallet.
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
Remote MCP server exposing SMI Aware tools, resources, and skills over Streamable HTTP.
Nifty's MCP server — exposes tasks, projects, messages, and files as tools for AI agents.
MCP server for your apps' tools and custom tools, plus hosted AI agents and approval-gated workflows
Host any HTTP API as a standard MCP server; auto-distribute to 12+ mainstream agent platforms.
Related MCP Servers
- AlicenseNot gradedqualityCmaintenanceExposes an MCP endpoint over JSON-RPC 2.0 with six tools, enabling agents to create and retrieve repositories, file and list issues, open pull requests, and merge them. It also supports discovery and initialization handshakes for client integration.MIT
- 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 gradedqualityCmaintenanceExposes an MCP endpoint over JSON-RPC 2.0 with seven tools that let agents create and manage repositories, issues, pull requests, labels, and comments, all backed by a shared store so changes are visible across the git, REST v3, and GraphQL 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