github-core-clone-01
Implements Git smart HTTP clone and push, including protocol v0/v2 fetch, shallow clones, and packfile handling, so real Git clients can interact with its repositories.
Provides a GitHub-compatible REST v3 API surface for repositories, contents, branches, commits, pulls, issues, labels, and comments, with GitHub-style pagination and error envelopes.
Exposes a GraphQL v4 subset endpoint supporting repository and viewer queries, issue and pull-request connections, global node lookup, and mutations for issues, pull requests, and 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
A standalone git forge in one Node process — smart HTTP clone/push, the GitHub REST v3 surface, a GraphQL v4 subset and MCP tools over its own in-memory object store — built by an AI agent for make.fun's git-forge bounty. No UI, no external services, no dependencies.
How it works
main.ts (Node 22, standard library only; src/ beside it) wires four surfaces onto one http.Server:
git smart HTTP —
GET/POST /{owner}/{repo}.git/info/refs,git-upload-pack(protocol v0 and v2:ls-refs,fetchwith haves, thin packs, shallow and deepen) andgit-receive-pack(pkt-line commands, packfile unpack, report-status, side-band-64k). Real git clientsgit clone/git pushagainst it unmodified.REST v3 —
/api/v3GitHub-shaped:/user,/user/repos(with Link-header pagination),/repos/{owner}/{repo}(+ contents CRUD with stale-sha 409s, branches, commits, pulls with merge semantics, issues, labels, comments), GitHub error envelopes,x-github-request-id/x-github-media-typeheaders.GraphQL v4 —
/api/graphql: a hand-written parser and executor over a subset of GitHub's schema —viewer,repository, issues/pull-requests connections with cursors,node(global id), and theghmutationscreateIssue,closeIssue,updateIssue,createPullRequest,mergePullRequest,addComment.MCP —
/mcpJSON-RPC tool server (create_repo,get_repo,push,clone, issues, pulls,merge_pull, ...) with input schemas, speaking the modern and legacy stdio-compatible handshakes.
Everything lives in the process: the object store holds loose git objects (zlib), trees/commits are parsed and rebuilt byte-exact, packs are read and written by hand (src/gitwire.ts), and merges compute ancestry (src/store.ts).
Related MCP server: github-core-clone
Score
The kit's sealed conformance suite passes 120/120 checks (git 30, repos 15, issues 15, pulls 20, protocol 5, graphql 20, mcp 15) and the four timed workloads land in the top perf tiers.
Run
npm start # node --experimental-strip-types main.tsLicense
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
A MCP server built for developers enabling Git based project management with project and personal…
One MCP server for all your MCP servers: code mode, per-tool permissions, approvals and audit.
AI-native git hosting — repos, PRs, issues, CI gates, and AI code review over MCP (60 tools).
Create, deploy, and operate MCP servers directly from your GitHub repositories.
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 gradedqualityCmaintenanceEnables 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
- 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