GitDesktop MCP
A Git client with a built-in MCP server for Windows, macOS and Linux: an agent reads repos, PRs, issues and CI logs, read-only
- 248 ★ on the repository
- Last commit
- Apache-2.0
Broad access
Why this level
- With write flags the agent creates and merges PRs, force-pushes and deletes branches in your name
- Forge access goes through your `gh`, `glab` or Bitbucket token
- The server reads code, history and CI logs of every repository you connect
Install
- Works in
Manual install
Install GitDesktop, open Settings, MCP servers and press install for Claude Code, or write the snippet to the repository's `.mcp.json`. Leave all write flags off. Do not enable `--allow-remote-write` or `--allow-destructive` without the user's explicit consent.
Access and checks
How we reviewBroad accessThe tool can change data, run commands or handle secrets.
- With write flags the agent creates and merges PRs, force-pushes and deletes branches in your name
- Forge access goes through your `gh`, `glab` or Bitbucket token
- The server reads code, history and CI logs of every repository you connect
This is third-party code. Review the repository files before installing.
What it does
GitDesktop is a desktop Git client built on Tauri and React with pull requests and review, issues and a GitHub Actions view for GitHub, GitLab and Bitbucket. For agents it has a built-in stdio MCP server: the app gives an external client (Claude Desktop, Cursor, Claude Code) tools for status, log, diff, blame, branches, file reads and history, plus pull requests, issues, CI logs and project boards. Forge requests go through `gh`, `glab` or a Bitbucket token by the repository's remote. Writes are enabled by a ladder of separate flags, all off. `--allow-write` gives the app's local PRs and issues, `--allow-remote-write` real forge writes (create, merge, assign reviewers, rerun CI, cut a release), `--allow-git-write` recoverable git operations and `--allow-destructive` the irreversible ones: reset, force push and deleting branches. In the app settings one click writes a snippet into the repository's `.mcp.json` or installs it globally for Claude Code and Copilot.
Who it is for. Developers who want an agent to read a repository, PRs and CI through already configured `gh` and `glab` without handing it tokens.
Good fit when
- An agent needs to understand a repository: status, file history, blame and branches, changing nothing
- You must read the logs of a failed Actions run and work out the cause with an agent
- A pull request review runs in the agent and it should take description and labels from GitHub or GitLab issues
- You want to open writing to the agent step by step: local PRs first, then git, then forges
Not a fit when
- You want the server without the app: the MCP is launched by the GitDesktop client itself and there is no separate package
- The agent must edit agent session branches: branch-mutating tools refuse them, as do push and force push
- You need Bitbucket issues: it covers pull requests and pipelines but not issues
Example request
Read the logs of the failed CI run in this repository through GitDesktop and explain which step broke, without changing anythingMCP
- Transport
- stdio
- Authentication
- not required
Limitations
The MCP server is part of the app, so GitDesktop must be installed. GitHub access goes only through `gh` with no OAuth app, and the app stores no tokens; GitLab needs `glab` and Bitbucket a token. On Windows the MCP runs through the `gitdesktop-mcp` copy and on macOS and Linux through the app's own binary. Each write tier has its own flag, and the dangerous tiers `--allow-remote-write` and `--allow-destructive` give the agent your identity's rights on forges. The project changes actively, with the latest changes from November 2026.
How to disable. In the app settings open MCP servers and press Remove for the client, or delete the entry from `.mcp.json`. The app itself uninstalls like any other program.
FAQ
How do I connect the GitDesktop MCP server?
Settings, MCP servers has a ready snippet, a write to the repository's `.mcp.json` (with a portable-paths option) and a global install for Claude Code or Copilot. Claude Desktop and Cursor clients are supported too.
What can the agent do by default?
Only read: status, log, diff, blame, branches, files and history, PRs, issues, CI logs and GitHub project boards.
Which flags enable writing?
`--allow-write` for local PRs and issues, `--allow-remote-write` for forge writes, `--allow-git-write` for recoverable git operations and `--allow-destructive` for irreversible ones. Each flag is independent and off by default.
Do I need tokens?
Not for GitHub: access goes through `gh`. GitLab needs `glab` and Bitbucket a token, and model keys are kept in the OS keychain.
Does it work with GitHub Enterprise?
Yes, `gh` detects the host from the repository remote, and after `gh auth login --hostname <host>` Enterprise works like github.com.
Discussion
No questions or reviews yet.
Related
MCP serversA GitLab MCP with 86 tools: issues, merge requests, pipelines, wikis and files, a read-only mode and a launch both locally and remotely with OAuth
Diffinery plugins connect Claude Code and Codex to self-hosted Git, pull requests and CI on Cloudflare through an MCP server
GitHub's official MCP server: code, issues, pull requests, Actions and security alerts straight from the agent
gitai is an open source-control server for hundreds of agents: landing by compare-and-swap, server-side history and the graft CLI.
A server-side web job runner with an MCP endpoint: Claude Code runs jobs and workflows, reads their results and answers notes
A GitHub Action that runs Claude Code in pull requests and issues: answers mentions, reviews and makes changes
README in short
The description opens with the client: the full PR cycle, three forges, a My work inbox, a GitHub Actions cockpit, agent sessions, AI review and MCP in both directions. The MCP section covers connecting your own servers to sessions and GitDesktop itself as a server with a ladder of write flags.