github-core-clone-01
Provides a GitHub-compatible forge with REST v3 and GraphQL v4 APIs plus git smart HTTP, supporting repositories, branches, commits, contents, issues, labels, collaborators, pull requests, files, merges, and clone/push workflows.
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 forge
A self-contained forge for the github-core-clone-01 contest: a single Node 22 process that speaks GitHub's REST v3 API, GraphQL v4, the Model Context Protocol, and real git smart HTTP, all over one in-memory repository model. It uses only the Node standard library - no dependencies, no network, and no git binary.
The server is split by surface: app.ts routes requests, rest.ts serves repositories, contents,
git data, issues, labels, collaborators and pull requests; graphql.ts parses and executes GraphQL
documents (including variables, fragments, aliases, introspection, mutations and batching);
mcp.ts implements server/discover, the legacy handshake and six repository tools; githttp.ts
serves protocol v0/v2 advertisements, ls-refs, shallow and incremental fetches, and pushes with
per-ref report-status. store.ts holds the forge state and real git object graph, and lib.ts
implements SHA-1 object framing, trees, commits, pkt-lines, packs and deltas. Every surface mutates
the same forge, so a repository created over REST can be pushed over git, read over GraphQL, and
merged through MCP.
Run it
node --experimental-strip-types main.tsSet MAKEFUN_ENV_URL to the trial env's origin (the contest harness does this); the process binds an
ephemeral port, registers it with the env, serves until the env reports done, then exits 0. The kit's
own local runner grades the same conformance suite.
Related MCP server: github-core-clone
Surface
Route | What it serves |
|
|
| GitHub REST v3: users, orgs, repos, branches, commits, contents, git data, issues, comments, labels, collaborators, pulls, files and merges |
| GitHub GraphQL v4 documents and operation batches |
| MCP over HTTP: discover, initialize, tools/list, tools/call |
| git smart HTTP: info/refs, upload-pack (v2/v0), receive-pack |
anything else |
|
Authentication is bearer-token based: REST and GraphQL require Authorization: Bearer <token>,
MCP refuses unauthenticated tool calls, and git object transfer stays open so a real client can
clone and push. Every REST response carries an x-github-request-id header.
Layout
main.ts- the env lifecycle: bind, register, wait for done.app.ts- onenode:httpserver and the routing table.lib.ts- git primitives: object ids, trees, commits, pkt-lines, packs and deltas.store.ts- the forge model: users, repositories, refs, objects, issues and pulls.rest.ts- the REST v3 handlers.graphql.ts- the GraphQL lexer, parser and executor.mcp.ts- the MCP endpoint and its six tools.githttp.ts- the git smart-HTTP transport.
Licensed under the MIT licence in 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
AI-native git hosting — repos, PRs, issues, CI gates, and AI code review over MCP (60 tools).
Verified component catalog over remote MCP: agents pick component ids and get a stamped project repo that builds. Connect at https://www.botkelp.com/mcp. Auth: MCP OAuth 2.1, or a Bearer bk_live_ API key; initialize and tools/list are open.
Repository knowledge graph MCP server for codebase understanding and debugging.
A MCP server built for developers enabling Git based project management with project and personal…
Related MCP Servers
- AlicenseNot gradedqualityBmaintenanceEnables MCP clients to discover, initialize, list tools, and invoke tools over Streamable HTTP against a GitHub-compatible git forge.MIT
- AlicenseNot gradedqualityCmaintenanceEnables MCP clients to initialize, list tools, and invoke GitHub-compatible operations over streamable HTTP in a self-contained git forge.MIT
- AlicenseNot gradedqualityCmaintenanceEnables MCP clients to create and inspect repositories, push and clone code, and manage issues and pull requests, including merging, through JSON-RPC tools with defined input schemas and modern/legacy handshakes.MIT
- AlicenseNot gradedqualityCmaintenanceEnables repository, issue, and pull request management through six MCP tools that share state with the forge's Git, REST, and GraphQL surfaces.MIT