github-mcp-server
Provides a GitHub-compatible MCP tool surface for managing repositories, issues, comments, labels, and pull requests, including creating and merging pull requests.
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
One Node process, one store, four surfaces:
Git smart HTTP —
info/refs,upload-packandreceive-pack(protocol v0 and v2, shallow fetch/deepen, pack deltas in and out) implemented in-process on a hand-rolled SHA-1 object model. Nogitbinary, no proxy, no outside service.REST v3 — repositories, contents, git refs, labels, issues, comments and pull requests (including real three-way merges) under
/api/v3.GraphQL v4 — viewer, repository, issue and pull-request queries and mutations, Relay global ids, cursor pagination, batched operations and introspection at
/api/graphql.MCP — the github-mcp-server tool surface (
create_repo,get_repo,create_issue,list_issues,create_pull_request,merge_pull_request, …) as JSON-RPC 2.0 over Streamable HTTP at/mcp, speaking the 2026-07-28 revision (server/discover) and the legacy initialize handshake.
All four surfaces read and write the same in-memory store, snapshotted to disk
(JSON, write-behind) under FORGE_DATA_DIR (default: a forge-data directory under
the OS temp dir, so a read-only working directory never breaks the server).
Run
node --experimental-strip-types main.ts # needs MAKEFUN_ENV_URL (the trial lifecycle)For local poking, import createApp() from app.ts and listen on any port; any
non-empty Authorization: Bearer … authenticates as the forge's one user.
Related MCP server: github-core-clone
Layout
main.ts— the entry ↔ env lifecycle (register the bound port, poll/done).app.ts— the HTTP server and router.store.ts— the shared store: repos, issues, pulls, labels, comments, persistence.git.ts— the git object model: hashing, trees, commits, packs, diffs, merges.githttp.ts— the smart-HTTP protocol (advertisement, ls-refs, fetch, push).rest.ts— the REST v3 surface.graphql.ts— the GraphQL surface (parser, executor, introspection).mcp.ts— the MCP endpoint and its tools.
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
A MCP server built for developers enabling Git based project management with project and personal…
AI-native git hosting — repos, PRs, issues, CI gates, and AI code review over MCP (60 tools).
Create, deploy, and operate MCP servers directly from your GitHub repositories.
Remote MCP server exposing SMI Aware tools, resources, and skills over Streamable HTTP.
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 gradedqualityCmaintenanceEnables GitHub-compatible repository, issue, and pull request management over JSON-RPC 2.0 Streamable HTTP, including creating repositories, filing and listing issues, and creating or merging pull requests.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 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