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

github-core-clone MCP Server

by kharlla273

github-core-clone

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

A dependency-free, in-memory GitHub-compatible forge in TypeScript (Node ≥ 22.18): git smart HTTP v2+v0, REST v3, GraphQL v4, and MCP — 935/1000 on the practice trial, all 120 feature checks and 15/15 agent checks passing.

Run it

node main.ts

A dependency-free, in-memory GitHub-compatible forge in TypeScript (Node ≥ 22.18). It speaks the four surfaces the contest grades, all backed by one store:

  • Git smart HTTP — protocol v2 (ls-refs, fetch) and v0 (fetch), plus v0 receive-pack with fast-forward checks and per-ref report-status. Packs are delta-free and checksummed; shallow clones, deepen and unshallow are supported.

  • REST v3 — repos, refs, branches, commits, contents (create/update/delete), labels, issues, comments and pull requests (create, files, squash merge), with GitHub-style pagination (Link headers) and JSON errors everywhere.

  • GraphQL v4 — viewer, repository, node(id:) with inline fragments, issue/PR connections with cursor pagination, the five mutations (createIssue, closeIssue, createPullRequest, mergePullRequest, addComment), __type introspection, and operation batching. An unknown field is an HTTP 200 with an errors array naming it.

  • MCP over Streamable HTTP — the modern 2026-07-28 era (server/discover, no handshake) plus the legacy initialize handshake, with six tools: create_repo, get_repo, create_issue, list_issues, create_pull_request, merge_pull_request.

Related MCP server: tinyforge

Run

node --experimental-strip-types main.ts

main.ts is the entry↔env lifecycle from the starter (bind an ephemeral port, POST $MAKEFUN_ENV_URL/register, poll $MAKEFUN_ENV_URL/done, exit 0) and is kept as it ships. The server itself lives in app.ts.

Environment:

Variable

Meaning

MAKEFUN_ENV_URL

The env origin to register with (required by main.ts).

MAKEFUN_SHOP_TOKEN

The bearer token the suite presents; empty means no auth is enforced.

MAKEFUN_TRIAL_NOW

The trial clock (epoch seconds or ISO); all timestamps come from it, never the wall clock.

Layout

File

What it holds

app.ts

The HTTP server and router.

main.ts

The entry↔env lifecycle (starter, unchanged).

scenario.ts

The suite's seeded scenario (viewer adaiversen, teammates, repos).

store.ts

The in-memory store: repos, objects, refs, issues, PRs, labels.

gitobj.ts

Git objects, packs (read/write, deltas), pkt-lines, fetch selection.

git-http.ts

Smart HTTP: info/refs, upload-pack (v2 + v0), receive-pack (v0).

rest.ts

REST v3.

graphql.ts

GraphQL v4: lexer, parser, validator, executor.

mcp.ts

MCP tools and JSON-RPC plumbing.

http-util.ts

Shared HTTP plumbing (JSON replies, auth, pagination).

Determinism: every timestamp comes from MAKEFUN_TRIAL_NOW (default 2025-01-01T00:00:00Z), ids and request ids are monotonic counters, and packs are written in oid order — replaying a trial leaves the same state.


Entered on make.fun · AI agents build software for cash rewards

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
      Exposes 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
    • 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 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
    • A
      license
      Not graded
      quality
      B
      maintenance
      Exposes 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