io.github.cyanheads/git-mcp-server MCP Server
io.github.cyanheads/git-mcp-server
Comprehensive Git MCP server with 28 tools for AI agents to clone, commit, branch, merge, and manage repositories.
What this kind of tool is for
- Automate a build, test, or deployment step you repeat by hand.
- Review or refactor code in an existing repository without leaving your agent.
- Bridge an internal service or CLI into the agent toolset.
How to compare servers like this
- Scope of control:
- Repos and CI are hard to undo; prefer tools that ask before anything irreversible.
- Environment fit:
- Match the runtime it expects (Node, Python, a container) to what you actually run.
- Maintenance signal:
- Check the last-commit date — dev tooling that lags upstream breaks first.
- Config surface:
- Prefer tools whose environment-variable or config keys are documented plainly.
This page carries your copy-paste config: pick your MCP client in the install section on this page and use the copy button.
What is the io.github.cyanheads/git-mcp-server MCP server?
The @cyanheads/git-mcp-server is a Git MCP server that exposes 28 native git operations to AI agents via STDIO and HTTP transports. It enables full repository management including cloning, committing, branching, merging, and advanced workflows like worktrees and cherry-picking, with built-in support for GPG/SSH signing, multi-repo sessions, and configurable git identity.
This server gives AI agents like Claude and Cursor direct access to comprehensive git operations. It supports repository initialization and cloning, staging and committing changes, branch management, history inspection, remote synchronization, and advanced workflows. With features like commit signing, working directory management, and safety confirmations for destructive operations, it's designed for AI-driven development workflows that need full version control capabilities.
How to install io.github.cyanheads/git-mcp-server
Copy-paste configuration for popular MCP clients.
MCP_LOG_LEVELSets the minimum log level for output (e.g., 'debug', 'info', 'warn').
GIT_BASE_DIROptional absolute path to restrict all git operations to a specific directory tree. Provides security sandboxing for multi-tenant or shared environments.
MCP_HTTP_HOSTThe hostname for the HTTP server.
MCP_HTTP_PORTThe port to run the HTTP server on.
MCP_HTTP_ENDPOINT_PATHThe endpoint path for the MCP server.
MCP_AUTH_MODEAuthentication mode to use: 'none', 'jwt', or 'oauth'.
{
"mcpServers": {
"git-mcp-server": {
"command": "bun",
"args": [
"-y",
"@cyanheads/git-mcp-server",
"run",
"start:stdio"
],
"env": {
"MCP_LOG_LEVEL": "<YOUR_MCP_LOG_LEVEL>",
"GIT_BASE_DIR": "<YOUR_GIT_BASE_DIR>",
"MCP_HTTP_HOST": "<YOUR_MCP_HTTP_HOST>",
"MCP_HTTP_PORT": "<YOUR_MCP_HTTP_PORT>",
"MCP_HTTP_ENDPOINT_PATH": "<YOUR_MCP_HTTP_ENDPOINT_PATH>",
"MCP_AUTH_MODE": "<YOUR_MCP_AUTH_MODE>"
}
}
}
}Tools & capabilities
Tools this server exposes to the agent.
git_init— Initialize a new git repositorygit_clone— Clone a repository from a remotegit_status— Check repository statusgit_clean— Clean untracked filesgit_add— Stage changes for commitgit_commit— Create a commitgit_diff— Compare changes between versionsgit_log— View commit historygit_show— Inspect git objectsgit_blame— Trace authorship of linesgit_reflog— View reference logsgit_changelog_analyze— Gather git context and instructions for LLM-driven changelog analysisgit_branch— Manage branchesgit_checkout— Switch branches or contextsgit_merge— Integrate changes from one branch to anothergit_rebase— Reapply commits on top of another branchgit_cherry_pick— Apply specific commits to current branchgit_remote— Configure remote repositoriesgit_fetch— Fetch updates from remotesgit_pull— Synchronize repositories
Use cases
- Clone repositories and manage multiple branches for AI-assisted development workflows
- Automate commit creation with proper git identity and GPG/SSH signing for secure version control
- Analyze commit history and generate changelogs using LLM-driven changelog analysis
- Manage complex workflows using worktrees, cherry-picks, and rebases for multi-feature development
- Review and inspect code changes with diff, blame, and log tools before committing
io.github.cyanheads/git-mcp-server MCP server FAQ
It's an MCP server that exposes 28 git operations to AI agents, enabling full repository management including cloning, committing, branching, merging, and advanced workflows through STDIO or HTTP transports.
Yes, the git-mcp-server is open-source under the Apache 2.0 license and available via npm as @cyanheads/git-mcp-server.
Add it to your MCP client config (e.g., cline_mcp_settings.json) with command 'npx @cyanheads/git-mcp-server@latest' or 'bunx @cyanheads/git-mcp-server@latest' for Bun, setting environment variables like GIT_USERNAME and GIT_EMAIL.
No authentication is required by default (auth_mode: none), but it supports optional JWT and OAuth modes for authenticated deployments.
Yes, it supports GPG/SSH signing for commits, merges, rebases, cherry-picks, and tags via the GIT_SIGN_COMMITS environment variable, with automatic fallback to unsigned commits if signing fails.
It works with Node.js >= 20.0.0 or Bun >= 1.2.0, with auto-detection of the runtime. Configuration is done via environment variables like GIT_BASE_DIR, GIT_USERNAME, and GIT_EMAIL.
README (reference)
Source of truth, from the repository.
Tools
28 git operations organized into seven categories:
| Category | Tools | Description |
|---|---|---|
| Repository Management | git_init, git_clone, git_status, git_clean | Initialize repos, clone from remotes, check status, clean untracked files |
| Staging & Commits | git_add, git_commit, git_diff | Stage changes, create commits, compare changes |
| History & Inspection | git_log, git_show, git_blame, git_reflog | View commit history, inspect objects, trace authorship, view ref logs |
| Analysis | git_changelog_analyze | Gather git context and instructions for LLM-driven changelog analysis |
| Branching & Merging | git_branch, git_checkout, git_merge, git_rebase, git_cherry_pick | Manage branches, switch contexts, integrate changes, apply specific commits |
| Remote Operations | git_remote, git_fetch, git_pull, git_push | Configure remotes, fetch updates, synchronize repositories, publish changes |
| Advanced Workflows | git_tag, git_stash, git_reset, git_worktree, git_set_working_dir, git_clear_working_dir, git_wrapup_instructions | Tag releases (list/create/delete/verify), stash changes, reset state, manage worktrees, set/clear session directory |
Resources
| Resource | URI | Description |
|---|---|---|
| Git Working Directory | git://working-directory | The current session working directory, set via git_set_working_dir. |
Prompts
| Prompt | Description | Parameters |
|---|---|---|
| Git Wrap-up | Workflow protocol for completing git sessions: review, document, commit, and tag changes. | changelogPath, createTag. |
Getting started
Runtime
Works with both Bun and Node.js. Runtime is auto-detected.
| Runtime | Command | Minimum Version |
|---|---|---|
| Node.js | npx @cyanheads/git-mcp-server@latest | >= 20.0.0 |
| Bun | bunx @cyanheads/git-mcp-server@latest | >= 1.2.0 |
MCP client configuration
Add the following to your MCP client config (e.g., cline_mcp_settings.json). Update the environment variables to match your setup — especially the git identity fields.
{
"mcpServers": {
"git-mcp-server": {
"type": "stdio",
"command": "npx",
"args": ["@cyanheads/git-mcp-server@latest"],
"env": {
"MCP_TRANSPORT_TYPE": "stdio",
"MCP_LOG_LEVEL": "info",
"GIT_BASE_DIR": "~/Developer/",
"LOGS_DIR": "~/Developer/logs/git-mcp-server/",
"GIT_USERNAME": "cyanheads",
"GIT_EMAIL": "casey@caseyjhand.com",
"GIT_SIGN_COMMITS": "true"
}
}
}
}
Bun users: replace "command": "npx" with "command": "bunx".
For Streamable HTTP, set MCP_TRANSPORT_TYPE=http and MCP_HTTP_PORT=3015.
Features
Built on mcp-ts-template.
| Feature | Details |
|---|---|
| Declarative tools | Define capabilities in single, self-contained files. The framework handles registration, validation, and execution. |
| Error handling | Unified McpError system for consistent, structured error responses. |
| Authentication | Supports none, jwt, and oauth modes. |
| Pluggable storage | Swap backends (in-memory, filesystem, Supabase, Cloudflare KV/R2) without changing business logic. |
| Observability | Structured logging (Pino) and optional auto-instrumented OpenTelemetry for traces and metrics. |
| Dependency injection | Built with tsyringe for decoupled, testable architecture. |
| Cross-runtime | Auto-detects Bun or Node.js and uses the appropriate process spawning method. |
| Provider architecture | Pluggable git provider system. Current: CLI. Planned: isomorphic-git for edge deployment. |
| Working directory management | Session-specific directory context for multi-repo workflows. |
| Configurable git identity | Override author/committer info via environment variables, with fallback to global git config. |
| Commit signing | GPG/SSH signing (enabled by default) for commits, merges, rebases, cherry-picks, and tags. Silent fallback to unsigned on failure with signed/signingWarning fields in responses. |
| Safety | Destructive operations (git clean, git reset --hard) require explicit confirmation flags. |
Security
- All file paths are validated and sanitized to prevent directory traversal.
- Optional
GIT_BASE_DIRrestricts operations to a specific directory tree for multi-tenant sandboxing. - Git commands use validated arguments via process spawning — no shell interpolation.
- JWT and OAuth support for authenticated deployments.
- Optional rate limiting via the DI-managed
RateLimiterservice. - All operations are logged with request context for auditing.
Configuration
All configuration is validated at startup in src/config/index.ts. Key environment variables:
| Variable | Description | Default |
|---|---|---|
MCP_TRANSPORT_TYPE | Transport: stdio or http. | stdio |
MCP_SESSION_MODE | HTTP session mode: stateless, stateful, or auto. | auto |
MCP_RESPONSE_FORMAT | Response format: json (LLM-optimized), markdown (human-readable), or auto. | json |
MCP_RESPONSE_VERBOSITY | Detail level: minimal, standard, or full. | standard |
MCP_HTTP_PORT | HTTP server port. | 3015 |
MCP_HTTP_HOST | HTTP server hostname. | 127.0.0.1 |
MCP_HTTP_ENDPOINT_PATH | MCP request endpoint path. | /mcp |
MCP_AUTH_MODE | Authentication mode: none, jwt, or oauth. | none |
STORAGE_PROVIDER_TYPE | Storage backend: in-memory, filesystem, supabase, cloudflare-kv, r2. | in-memory |
OTEL_ENABLED | Enable OpenTelemetry. | false |
MCP_LOG_LEVEL | Minimum log level: debug, info, warn, error. | info |
GIT_SIGN_COMMITS | GPG/SSH signing for commits, merges, rebases, cherry-picks, and tags. Falls back to unsigned on failure (see response signed/signingWarning). | true |
GIT_AUTHOR_NAME | Git author name. Aliases: GIT_USERNAME, GIT_USER. Falls back to global git config. | (none) |
GIT_AUTHOR_EMAIL | Git author email. Aliases: GIT_EMAIL, GIT_USER_EMAIL. Falls back to global git config. | (none) |
GIT_BASE_DIR | Absolute path to restrict all git operations to a specific directory tree. | (none) |
GIT_WRAPUP_INSTRUCTIONS_PATH | Path to custom markdown file with workflow instructions. | (none) |
MCP_AUTH_SECRET_KEY | Required for jwt auth. 32+ character secret key. | (none) |
OAUTH_ISSUER_URL | Required for oauth auth. OIDC provider URL. | (none) |
Running the server
Via package manager (no install)
npx @cyanheads/git-mcp-server@latest
Configure through environment variables or your MCP client config.
Local development
# Build and run
npm run rebuild
npm run start:stdio # or start:http
# Dev mode with hot reload
npm run dev:stdio # or dev:http
# Checks and tests
npm run devcheck # lint, format, typecheck
npm test
Cloudflare Workers
npm run build:worker # Build the worker bundle
npm run deploy:dev # Run locally with Wrangler
npm run deploy:prod # Deploy to Cloudflare
Project structure
| Directory | Purpose |
|---|---|
src/mcp-server/tools | Tool definitions (*.tool.ts). Git capabilities live here. |
src/mcp-server/resources | Resource definitions (*.resource.ts). Git context data sources. |
src/mcp-server/transports | HTTP and STDIO transport implementations, including auth. |
src/storage | StorageService abstraction and provider implementations. |
src/services | Git service provider (CLI-based git operations). |
src/container | DI container registrations and tokens. |
src/utils | Logging, error handling, performance, security utilities. |
src/config | Environment variable parsing and validation (Zod). |
tests/ | Unit and integration tests, mirroring src/ structure. |
Response format
Configure output format and verbosity via MCP_RESPONSE_FORMAT and MCP_RESPONSE_VERBOSITY.
JSON format (default, optimized for LLM consumption):
{
"success": true,
"branch": "main",
"staged": ["src/index.ts", "README.md"],
"unstaged": ["package.json"],
"untracked": []
}
Markdown format (human-readable):
# Git Status: main
## Staged (2)
- src/index.ts
- README.md
## Unstaged (1)
- package.json
The LLM always receives the complete structured data via responseFormatter — full file lists, metadata, timestamps — regardless of what the client displays. Verbosity controls how much detail is included: minimal (core fields only), standard (balanced), or full (everything).
Development guide
See AGENTS.md for architecture, tool development patterns, and contribution rules.
Testing
Tests use Bun's test runner with Vitest compatibility.
bun test # Run all tests
bun test --coverage # With coverage
bun run devcheck # Lint, format, typecheck, audit
Roadmap
The server uses a provider-based architecture for git operations:
- CLI provider (current) — Full 28-tool coverage via native git CLI. Requires local git installation.
- Isomorphic git provider (planned) — Pure JS implementation for edge deployment (Cloudflare Workers, Vercel Edge, Deno Deploy). Uses isomorphic-git.
- GitHub API provider (maybe) — Cloud-native operations via GitHub REST/GraphQL APIs, no local repo required.
Contributing
Issues and pull requests are welcome. Run checks before submitting:
npm run devcheck
npm test
License
Apache 2.0. See LICENSE.
<div align="center"> <p>Built with the <a href="https://github.com/cyanheads/mcp-ts-template">mcp-ts-template</a></p> <p> <a href="https://github.com/sponsors/cyanheads">Sponsor this project</a> · <a href="https://www.buymeacoffee.com/cyanheads">Buy me a coffee</a> </p> </div>
Related MCP servers
Look up allele frequencies by ancestry, gene constraint, variants, and coverage over gnomAD.
Search Grants.gov funding opportunities and read full records: eligibility, awards, deadlines.
Guardian Open Platform — search and retrieve full article text from The Guardian archive.
MCP server for Project Gutenberg — 75,000+ public-domain ebooks with full plain-text retrieval.
Browse Hacker News feeds, threads, and user profiles with full-text search.
Search ILOSTAT labour indicators, query and compare series, build country profiles, run SQL.
