github-core-clone-01 MCP Server
Serves git smart HTTP for clone, fetch, and push operations, supporting protocol v2 and v0, shallow fetches, packfile/delta handling, and per-ref push validation.
Provides a GitHub-compatible API surface, including REST v3 and GraphQL v4 endpoints for repositories, branches, commits, contents, issues, comments, labels, pull requests, files, and merges.
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: one Node 22 process that serves git smart HTTP (protocol v2 and v0), the GitHub REST v3 API, GitHub GraphQL v4 and the Model Context Protocol over streamable HTTP, all from its own in-memory store. No UI, no dependencies, no git binary.
What it serves
Route | What it is |
| 200 |
| the API root, with |
| REST v3: repositories, branches, commits, contents, issues, comments, labels, pull requests, files and merges |
| GraphQL v4 for the documents |
| MCP over streamable HTTP: initialize, tools/list and tools/call |
| git smart HTTP: |
Everything lives in memory: git objects are SHA-1 addressed and every tree and commit this server writes is byte-identical to what git writes for the same data. The packfile reader resolves deltas, the writer emits packs, and pushes are validated per ref (fast-forward checks, sideband reports).
Related MCP server: github-core-clone-01
Run it
MAKEFUN_ENV_URL=http://127.0.0.1:8080 node --experimental-strip-types main.tsmain.ts is the trial lifecycle: bind an ephemeral port, POST it to $MAKEFUN_ENV_URL/register,
poll /done and exit 0. app.ts builds the server; store.ts holds the object store and the
REST resources; git-http.ts, rest.ts, graphql.ts and mcp.ts answer the four surfaces.
Layout
main.ts— the entry/env lifecycle (register, then poll/done)app.ts— the HTTP router and the serverstore.ts— git objects, refs, repositories, issues and pull requestsgit-http.ts— smart HTTP: v2 ls-refs and fetch, v0 receive-pack, pkt-lines and packfilesrest.ts— REST v3 resources, contents commits and squash mergesgraphql.ts— GraphQL v4 documentsmcp.ts— MCP streamable HTTP transport and tools
MIT licensed (see LICENSE).
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
Remote MCP server exposing SMI Aware tools, resources, and skills over Streamable HTTP.
Streamable HTTP MCP gateway for NV oOS fleets — one API key, namespaced tools, quotas and policy.
Create, deploy, and operate MCP servers directly from your GitHub repositories.
Host any HTTP API as MCP tools with a tamper-evident cross-agent settlement ledger.
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 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 an MCP Streamable HTTP endpoint that lets clients create and fetch repositories, create and list issues, and create and merge pull requests against a self-hosted, GitHub-compatible git forge. It also supports server discovery via the 2026-07-28 protocol plus legacy initialize.MIT
- AlicenseNot gradedqualityBmaintenanceEnables MCP clients to discover, initialize, list tools, and invoke tools over Streamable HTTP against a GitHub-compatible git forge.MIT