Git for your agent, with the guard rails on.
MCP Git lets your agent work with Git in one project folder without an open shell. It can look at the state, the history and the changes, make changes by creating branches and recording commits, and share work by fetching, publishing and rebasing. Every answer comes back as clear facts, and a request that does not fit what a tool accepts is refused.
It also says no for you. It will not publish to the shared branches main, master or develop, it cannot force-push, and it checks that each commit message follows the conventional format. The only merge it makes is a local fast-forward of a feature branch into develop; publishing develop stays with you.
What you gain over handing the agent a shell.
An agent with a free shell reads text meant for people, and nothing stops it from publishing to a shared branch or committing whatever happened to be staged. A narrow set of tools refuses specific risky requests; it does not replace review or remove other access the agent already has.
Clear answers
The agent reads facts instead of guessing at columns
- Typical alternative
- The agent parses text written for people
- Here
- The agent gets the branch, how far ahead or behind it is, and which files changed, as clear fields
An incomplete diff is visible
Large diffs stay small, and the agent knows when it saw only part
- Typical alternative
- A whole diff pasted into the conversation
- Here
- Large changes are cut to a sensible size by default, and the agent is told when it saw only part of them
A mistaken push is refused
These named shared branches cannot be pushed through this tool
- Typical alternative
- The agent publishes whatever it is asked
- Here
- Publishing to main, master or develop is refused, and force-pushing is not possible at all
Tidy history
Message form is consistent; already-staged changes still need review
- Typical alternative
- Commit messages that follow no rule
- Here
- The agent adds the paths you name to staging and commits the whole staged snapshot, with a conventional message
A rebase with explicit recovery
A conflict is a result to act on, not a stalled editor
- Typical alternative
- An interactive editor the agent cannot drive
- Here
- The agent rebases a complete ordered plan onto fetched origin/develop, and a conflict comes back as a result to act on
Learns the tools on the spot
The agent can retrieve guidance before its first change
- Typical alternative
- The agent relies on what it remembers about Git
- Here
- A built-in manual tells your agent the tools, the standard workflows and the rules
Ready in the image, one entry to add.
MCP Git comes in the MAIT image and updates with it (mait-image). Runs on Linux (amd64, arm64). On macOS and Windows, MCP Git runs in the managed Linux environment that AIDC Launch provides. Your agent client starts it from the folder of the repository you want it to work on: there is no separate repository setting, so the folder it starts in is the checkout it works on.
A developer can look at the same checkout from the command line too. You can also connect it through MCP Registry, so a single entry reaches all your tool servers. Get started shows how.
Where it sits in the MAIT toolkit.
Where to read on.
- Get started, Use cases and Tools