github-core-clone-01
Provides a GitHub-compatible git forge with MCP tools for managing repositories, branches, commits, contents, issues, comments, labels, pull requests, files, and squash merges, alongside GitHub-compatible REST v3 and GraphQL v4 APIs.
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 GitHub-compatible git forge
Entry for make.fun bounty github-core-clone-01 — build a GitHub-compatible git forge:
https://make.fun/bounty/github-core-clone-01
One process, Node 22 standard library only, no UI, no outside service, no git binary. It serves, from a single shared in-memory store:
git smart HTTP —
upload-packprotocol v2 (ls-refs, fetch, shallow/deepen) andreceive-packv0 (push with per-ref fast-forward reports) at/{owner}/{repo}.git, with real SHA-1 objects and PACK v2 packfiles.REST v3 under
/api/v3— repositories, branches, commits, contents, issues, comments, labels, pull requests, files and squash merges.GraphQL v4 at
/api/graphql— the documentsghandgithub-mcp-serversend, including introspection, cursor pagination and the create/close/merge mutations.MCP at
/mcp— streamable HTTP, revision 2026-07-28 (server/discover,initialize,tools/list,tools/call) with six tools that act on the same store as REST.
Run it
node --experimental-strip-types main.tsmain.ts binds an ephemeral port, registers it with the trial env at
$MAKEFUN_ENV_URL/register, then polls $MAKEFUN_ENV_URL/done until the
suite finishes and exits 0. app.ts is the whole forge. DESIGN.md is the
store/API contract the implementation follows.
Related MCP server: tinyforge
Local grade
Against the kit's sealed suite (program/env/server.mjs):
120/120 conformance checks (git 30/30, repos 15/15, issues 15/15,
pulls 20/20, graphql 20/20, mcp 15/15, protocol 5/5), perf 174/200
(push 39, clone 35, read 50, write 50) — local score 974/1000.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
MCP server for your apps' tools and custom tools, plus hosted AI agents and approval-gated workflows
Nifty's MCP server — exposes tasks, projects, messages, and files as tools for AI agents.
AI Reasoning Cache & Consensus Layer with 11 MCP tools via Streamable HTTP.
AI-native git hosting — repos, PRs, issues, CI gates, and AI code review over MCP (60 tools).
Related MCP Servers
- AlicenseNot gradedqualityDmaintenanceStateless Streamable HTTP MCP server exposing 5 GitHub tools (user info, repository metadata, file contents, issue listing, and issue creation) with token-based authentication required only for tool calls.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 gradedqualityNot gradedmaintenanceExposes a GitHub-compatible MCP endpoint over JSON-RPC 2.0 Streamable HTTP that lets clients create and fetch repositories, open, list, and close issues, add comments, and create and merge pull requests against an in-memory store. It supports both the 2026-07-28 revision with server/discover and the legacy initialize handshake, sharing state with the bundled REST and GraphQL surfaces.MIT
- AlicenseNot gradedqualityCmaintenanceExposes a JSON-RPC 2.0 Streamable HTTP MCP endpoint with six tools that let clients create and read repositories, file and list issues, and create and merge pull requests against the same in-memory store served by the REST and GraphQL APIs.MIT