forge
Provides a Git smart-HTTP server so real Git clients can clone, fetch, push, and pull, including protocol v2/v0, shallow and deepen fetches, pack handling, annotated-tag peeling, unborn HEAD, and fast-forward validation.
Provides a GitHub-compatible REST v3 API for managing repositories, branches, commits, refs, contents, labels, issues, comments, and pull requests, including files, diff stats, and squash merges.
Provides a GraphQL v4 API for reading viewer, repository, issue, and pull request data, with introspection, cursor pagination, node lookups, and mutations for creating/closing issues, creating/merging pull requests, and adding 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.
forge
A GitHub-compatible git forge in one dependency-free Node process: git smart-HTTP (protocol v2 and v0), the GitHub REST v3 API, the GraphQL v4 API and the Model Context Protocol, all over the same in-memory store. No git binary, no database, no network — the whole forge is the standard library.
Run
node --experimental-strip-types main.tsmain.ts is the entrypoint the harness runs: it listens on an ephemeral port,
registers it at $MAKEFUN_ENV_URL/register, polls $MAKEFUN_ENV_URL/done
until the trial ends, then exits 0. The bearer token for every API call is
$MAKEFUN_SHOP_TOKEN.
For local development:
MAKEFUN_SHOP_TOKEN=dev-token node --experimental-strip-types dev.ts 8080Then the forge listens on http://127.0.0.1:8080 and the token is dev-token.
Related MCP server: tinyforge
What it serves
Git smart-HTTP —
/{owner}/{repo}.git/info/refs,git-upload-pack(v2ls-refsandfetch, with a v0 fallback) andgit-receive-pack(v0,report-status+ sideband). Clone, fetch, push and pull work end-to-end with a realgitclient: shallow and deepen fetches, thin packs, OFS and REF deltas, annotated-tag peeling, unborn HEAD, and per-ref fast-forward validation (a non-fast-forward push isngand the ref does not move).REST v3 (
/api/v3) — repositories (create/list/get/patch/delete, with paginationLinkheaders), branches, commits, git refs, contents (create/update/delete with real git blob SHAs), labels, issues and comments, pull requests with files, diff stats and squash merges. A repository belongs to the login the token names; the same name under another owner is 404.GraphQL v4 (
/api/graphql) —viewer,repository,issueandpullRequestreads,__typeintrospection, issue lists withstates,orderByand cursor pagination,node(id:)with stable opaque Relay ids, thecreateIssue,closeIssue,createPullRequest,mergePullRequestandaddCommentmutations, and batched operation arrays.MCP (
/mcp) — JSON-RPC 2.0 Streamable HTTP:server/discoverfor the modern revision andinitializefor the legacy handshake,tools/listwith the six tools (create_repo,get_repo,create_issue,list_issues,create_pull_request,merge_pull_request), andtools/callacting on the same store as REST.
Layout
main.ts— the harness lifecycle (listen, register, poll/done, exit).app.ts— the HTTP server: routing, bearer auth, request ids, JSON bodies.dev.ts— the local runner.src/store.ts— the forge state: repos, objects, refs, issues, pull requests, the deterministic clock and id counters, fetch selection and the three-way squash merge.src/gitobj.ts— SHA-1 object ids, pkt-lines, pack read/write with delta resolution, tree/commit/tag parsing.src/gitproto.ts— the git wire: advertisements, ls-refs, fetch, receive-pack.src/rest.ts— the REST v3 dispatcher.src/graphql.ts— a hand-rolled GraphQL parser and executor.src/mcp.ts— the MCP endpoint.src/scenario.ts— the scenario seed: the viewer and teammate logins are derived from the same seed the harness uses, so the forge and the suite agree on who the token names.
Determinism
Nothing a check can read depends on the wall clock or on randomness:
timestamps come from MAKEFUN_TRIAL_NOW (falling back to a fixed epoch) plus
a monotonic counter, and ids come from counters. The same trial replays to the
same answers.
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.
AI Reasoning Cache & Consensus Layer with 11 MCP tools via Streamable HTTP.
Streamable HTTP MCP gateway for NV oOS fleets — one API key, namespaced tools, quotas and policy.
Host any HTTP API as MCP tools with a tamper-evident cross-agent settlement ledger.
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 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
- 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