Other formats agents might prefer:
markdownjsonllms.txt

Agent? You probably want markdown or json, or Pod over MCP.

Reported issues for git-mcp-server

Pod holds 19 of 26 problems reported by people outside the maintainer team. Issues filed by the project's own owners, members and collaborators are excluded entirely — a maintainer's release checklist is not a warning to a prospective user.

Back to git-mcp-server.

Most discussed

Error responses include structuredContent that fails output schema validation

Summary

When a git operation fails, the error response includes structuredContent with a different structure than the declared outputSchema. This causes MCP clients to reject the response with a schema validation error, masking the actual git error message.

Impact

When git operations fail (auth issues, network errors, conflicts, etc.), users see:

Error in git_push_git
Tool execution failed: MCP error -32602: Structured content does not match the tool's output schema: 
data must 

[Read the thread](https://github.com/cyanheads/git-mcp-server/issues/40) · 2026-02-23 · closed · external user · 4 comments

### Server Shutdown Due to Uncaught Exception While Creating Logs Directory

I'm using the Jetbrains Copilot plugin and I'm getting the following error when the server is started.

{"level":60,"time":1770759758405,"env":"development","version":"2.6.5","pid":34406,"applicationName":"@cyanheads/git-mcp-server","applicationVersion":"2.6.5","nodeEnvironment":"development","requestId":"4BSPF-LUKJJ","timestamp":"2026-02-10T21:42:38.350Z","operation":"ServerStartup","err":{"type":"Object","message":"ENOENT: no such file or directory, mkdir 'logs'","stack":"Error: ENOENT: no

Read the thread · 2026-02-10 · closed · external user · 2 comments

Cannot find Git on Windows

Git is installed and it's in the system path. And yet MCP can't find it:

{
	"level": 50,
	"time": 1765540389216,
	"env": "development",
	"version": "2.6.0",
	"pid": 52588,
	"requestId": "FUFHK-39BCW",
	"timestamp": "2025-12-12T11:53:09.196Z",
	"operation": "HandleToolRequest",
	"input": {
		"path": "D:\\Projects\\MyProj",
		"maxCount": 10,
		"oneline": false,
		"stat": false,
		"patch": false,
		"showSignature": false
	},
	"critical": false,
	"errorCode": -32603,
	"originalErrorType": "

[Read the thread](https://github.com/cyanheads/git-mcp-server/issues/37) · 2025-12-12 · open · external user · 3 comments

### Doesn't work on Windows with an absolute path

It doesn't work on Windows with an absolute path no matter how it's specified. If I specify GIT_BASE_DIR as "D:\\Projects", I get the following 

Server stderr: file:///C:/Users/username/AppData/Local/Temp/bunx-2483025435-@cyanheads/git-mcp-server@latest/node_modules/@cyanheads/git-mcp-server/dist/index.js:4658 throw new McpError(-32008 /* ConfigurationError */, "Invalid application configuration.", { ^

McpError: Invalid application configuration. at parseConfig (file:///C:

Read the thread · 2025-12-11 · closed · external user · 2 comments

MCP crashing on start

Running npx @cyanheads/git-mcp-server@latest package crashes immediately. "MCP Server running in STDIO mode." The process then terminates.

Last Known Working Version: 2.3.5

Environment:

  • Operating System: Windows 11
  • Node.js Version: v22.20.0

Steps to Reproduce:

  1. Open a terminal on Windows 11.
  2. Run the command: npx @cyanheads/git-mcp-server (or npx @cyanheads/git-mcp-server@latest)

Expected Behavior: The MCP server should start and remain running, awaiti

Read the thread · 2025-10-16 · closed · external user · 5 comments

MCP Git-Server Commit Function Fails with Schema Error

Description

The git_commit function of the MCP Git-Server throws a schema error despite correct parameters.

Error

MCP error -32602: Structured content does not match the tool's output schema: data should NOT have additional properties

Steps to Reproduce

  1. Initialize MCP Git-Server
  2. Add files to git
  3. Execute commit using git_commit
  4. Error occurs

Code Example

// This fails:
mcp_Git-MCP-Server_git_commit({
  message: "test: simple commit message"

[Read the thread](https://github.com/cyanheads/git-mcp-server/issues/24) · 2025-09-26 · open · external user · 7 comments

### feat(git): Add Git worktree MCP functions

## Description
Implement Git worktree functionality in the Git MCP server to support multi-branch development workflows.

## Background
Currently, there are no MCP tools that provide Git worktree capabilities. This limits the ability to work on multiple branches simultaneously, which is a key requirement for efficient multi-agent development.

## Proposed Solution
Add new MCP functions to support Git worktree operations:

1. `git___worktree_list` - List all worktrees
2. `git___worktree_add` - Cr

[Read the thread](https://github.com/cyanheads/git-mcp-server/issues/11) · 2025-05-24 · closed · external user · 2 comments

### Claude desktop error on macos

Looks like the server startup message is parsed by Claude.

my config
"git-mcp-server": {
  "command": "node",
  "args": ["/<masked>/git-mcp-server/dist/index.js"],
  "disabled": false,
  "autoApprove": [],
  "env": {
    "MCP_LOG_LEVEL": "error"
  }
},

error

2025-05-14T07:28:29.957Z [git-mcp-server] [error] Unexpected end of JSON input {"context":"connection","stack":"SyntaxError: Unexpected end of JSON input\n at JSON.parse ()\n

Read the thread · 2025-05-14 · closed · external user · 2 comments

Most recent

Propagate current working directory from parent process when initializing the server

The usage pattern "git_set_working_dir" -> "git_*" creates a problem when using git-mcp-server with oneshot-loading MCP servers:

  • server initializes on-demand
  • cwd is set with git_set_working_dir
  • server unloads
  • server initializes on-demand with a regular git command and fails to figure out cwd

See https://github.com/mcp-shark/lazy-tool/issues/5?reload=1 Related to https://github.com/cyanheads/git-mcp-server/issues/32

Read the thread · 2026-08-06 · open · external user · 0 comments

Advisory badge for git-mcp-server?

You've been shipping the git MCP hard (saw the early-July push). There's a public card at https://mcpindex.ai/server/io-github-cyanheads-git-mcp-server — if you want a README badge that tracks the advisory screen (not a safety cert), this is paste-ready:

mcpindex

If the title/blurb is off, reply with the fix and I'll update it.

Thank you, GB

Read the thread · 2026-07-12 · closed · external user · 1 comment

Argument/option injection in git ref parameters leads to arbitrary file write (git_log / git_diff / git_show)

reported on 5 June 2026 https://github.com/cyanheads/git-mcp-server/security/advisories/GHSA-265x-r5m8-w5v2 - no response, so trying here:

Summary

The ref/object parameters of several read tools (git_log branch, git_diff source/target, git_show object) are typed as a plain string with no leading-dash or format validation, and are placed into the git command line as positional arguments. git therefore interprets a value beginning with "-" as an option. Using git's --output= option, an attac

Read the thread · 2026-07-08 · open · external user · 1 comment

npm package declares missing dist/index.d.ts types entry

Summary

The published @cyanheads/git-mcp-server@2.15.1 npm package declares TypeScript types at dist/index.d.ts, but the tarball does not include that file.

Evidence

The package metadata declares both the root types field and the export-condition types field:

{
  "name": "@cyanheads/git-mcp-server",
  "version": "2.15.1",
  "main": "dist/index.js",
  "files": ["dist"],
  "exports": {
    ".": {
      "types": "./dist/index.d.ts",
      "import": "./dist/index.js"
    

[Read the thread](https://github.com/cyanheads/git-mcp-server/issues/50) · 2026-06-11 · closed · external user · 0 comments

### SSH Agent not picked up.

VS Code is passing along `SSH_AUTH_SOCK` in a dev container.

git is setup for ssh signing of commits and tags. Working in windows, wsl, and dev container envs. Key is unlocked and agent uses it just fine.

`git_commit` tool call (from Continue VS Code extension, in this case) results in passphrase error.

Files staged, but not committed.

---

### Tool Call Error

git_mcp_git_commit failed with the message: [{"type":"text","text":"Error: Git commit failed: Exit Code: 128\nStderr: error: Ente

Read the thread · 2026-05-16 · open · external user · 0 comments

GPT reports problem with the tool schema

Hi! Getting this error when using your server with gpt-5-codex, any chance you've seen anything like this?

{
  "error": {
    "message": "Invalid schema for function 'git_git_remote': In context=('properties', 'url', 'type', '0'), 'uri' is not a valid format.",
    "type": "invalid_request_error",
    "param": "tools[23].parameters",
    "code": "invalid_function_parameters"
  }
}

Read the thread · 2026-05-06 · closed · external user · 1 comment

feat: Add programmatic interactive rebase operations (squash, fixup, drop, autosquash)

Summary

Add high-level MCP tools for common interactive rebase operations that don't require TTY/editor interaction. This enables LLM agents to programmatically clean up commit history.

Motivation

Interactive rebase (git rebase -i) is essential for maintaining clean git history, but it requires an interactive editor session. LLM agents need programmatic access to these operations for workflows like:

  • Squashing WIP commits before PR
  • Applying fixup commits
  • Removing accidental/debug

Read the thread · 2026-02-21 · open · external user · 0 comments

Select functions fail to import: conv mcp tool input schema fail(unmarshal)

Description

Some operations of git-mcp-server fail to register with the MCP host. Each operation fails with the following warning structure:

Warning: Failed to load MCP server 'git-mcp-server': conv mcp tool input schema fail(unmarshal): json: cannot unmarshal number into Go struct field SchemaBis.properties.exclusiveMinimum of type bool, tool name: <tool operation here>

Furthermore, each warning stops the registration of any other operations not previously registered. Pictured

Read the thread · 2025-11-29 · open · external user · 1 comment

Unable to use MCP server: No session working directory set. Please specify a 'path' or use 'git_set_working_dir' first.

Just installed the extension on IntelliJ IDEA. Executing: "Summarize the last local commit" prompt to test the MCP server, from JetBrains AI chat when a project with git, I'm getting error:

No session working directory set. Please specify a 'path' or use 'git_set_working_dir' first.

Anything

My config:

{
  "mcpServers": {
    "git-mcp-server": {
      "command": "npx",
      "args": [
        "@cyanheads/git-mcp-server@latest"
      ],
      "env": {
        "MCP_TRANSPORT_TYPE": "

[Read the thread](https://github.com/cyanheads/git-mcp-server/issues/32) · 2025-11-16 · closed · external user · 1 comment

### [BUG] Error: Git command not found. Please ensure Git is installed and in your PATH.

I've configured the server on Roo Code on VS Code and after the agent sets up the working tree, any command will output said error. I've tried with bunx and npx commands with the same results.

[Read the thread](https://github.com/cyanheads/git-mcp-server/issues/31) · 2025-11-14 · open · external user · 2 comments

### Creating unnecessary logs/ directory

Every time I start a session in Roo Code, it creates the `logs/` directory.
This should not happen.

`git-mcp-server` is creating this directory at the root of the project...

├── logs │   ├── combined.log │   ├── error.log │   └── interactions.log


$ cat logs/combined.log {"level":30,"time":1761644032758,"env":"development","version":"2.5.6","pid":372662,"requestId":"7OI99-TG78K","timestamp":"2025-10-28T09:33:52.757Z","operation":"loggerInit","msg":"Logger initialized. MCP level:

Read the thread · 2025-10-28 · closed · external user · 1 comment

The remaining reports are on the project's issue tracker.