github-core-clone-01
Serves Git smart HTTP for any repository, supporting clone/fetch over protocol v2 and v0, push via git-receive-pack with packfile creation and parsing, shallow fetch/deepen/unshallow, and fast-forward checks with per-ref report-status.
Emulates GitHub's API surface so real git clients, gh-style tooling and MCP clients can drive a forge: REST v3 endpoints for repositories, branches, commits, contents, labels, issues and pull requests, plus a GitHub-compatible GraphQL API and MCP tools for creating repos, issues and pull requests and merging them.
Provides a GraphQL endpoint supporting viewer/repository queries, issue and pull-request connections with cursor pagination, type introspection, global node IDs, and mutations such as createIssue, closeIssue, createPullRequest, mergePullRequest and addComment, including batched operations.
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 GitHub-compatible git forge
A single-process, in-memory forge written in TypeScript for Node 22+,
using only the Node standard library (node:http, node:crypto,
node:zlib). It speaks enough of GitHub's surface to be driven by a real
git client, by gh-style GraphQL documents, and by an MCP client — all
against the same store.
Running
MAKEFUN_SHOP_TOKEN=<token> node --experimental-strip-types main.tsmain.ts binds port 0, registers the port with the environment
($MAKEFUN_ENV_URL/register), then polls $MAKEFUN_ENV_URL/done until the
environment says it is finished and exits 0. For local development you can
start just the app instead:
MAKEFUN_SHOP_TOKEN=test-token-123 node --experimental-strip-types -e \
"import('./app.ts').then(m => m.createApp().listen(18080))"Related MCP server: github-core-clone-01
What it implements
REST v3 (
/api/v3): repositories (create/list/get/patch/delete,Linkpagination), branches, commits, contents (create/update with stale-sha 409, delete), labels, issues (create/list/get/patch/comments), pull requests (create/get/list/files, squash merge with conflict detection). Every response is JSON, carries a non-emptyX-GitHub-Request-Id, and unknown routes return 404 with amessage.Git smart HTTP (
/{owner}/{repo}.git):info/refsforgit-upload-pack(protocol v2 and v0) andgit-receive-pack(v0), packfile creation and parsing (OFS/REF deltas, thin packs, sideband), shallow fetch / deepen / unshallow, fast-forward push checks with per-refok/ngreport-status.GraphQL (
/api/graphql):viewer,repository(fields, issues and pull-request connections with cursor pagination,__typeintrospection forIssue/PullRequest/Repository/SearchType),node(id:)global IDs, and mutationscreateIssue,closeIssue,createPullRequest,mergePullRequest,addComment. Batched operation arrays are answered in order; unknown fields produce GraphQL errors with HTTP 200.MCP (
/mcp, streamable HTTP):server/discover(modern era) and legacyinitialize, plustools/listandtools/callfor six tools —create_repo,get_repo,create_issue,list_issues,create_pull_request,merge_pull_request— acting on the same store as REST and GraphQL.
Notes on the model
The store is in-memory and deterministic: generated commits use a fixed epoch plus a monotonic counter, and REST objects use fixed timestamps, so two runs export the same bytes.
Authentication is a Bearer token from
MAKEFUN_SHOP_TOKEN(if the variable is empty, any non-empty Bearer is accepted, for local use only)./healthzneeds no token. A repository under another owner is 404, never 403.Fetch responses are cached per (repository, wants, haves, shallow, depth); objects are content-addressed and immutable, so a cached pack can never go stale.
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…
This server cannot be deployed
Maintenance
Related MCP Connectors
Host any HTTP API as MCP tools with a tamper-evident cross-agent settlement ledger.
Host any HTTP API as a standard MCP server; auto-distribute to 12+ mainstream agent platforms.
Streamable HTTP MCP gateway for NV oOS fleets — one API key, namespaced tools, quotas and policy.
Hosted MCP endpoint with realistic fake data for prototyping agents. 12 tools, no setup.
Related MCP Servers
- 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
- AlicenseNot gradedqualityCmaintenanceExposes a GitHub-style MCP endpoint over streamable HTTP that lets agents create and read repositories, open, list and comment on issues, and create and merge pull requests, mirroring the companion REST surface. It also supports discovery and initialization handshakes so clients can enumerate and call those tools.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