Git (local)
BetaThe reference MCP server for Git. It reads history and diffs and can stage and commit in a local repository.
- Developer Tools
- Local
- Runs
- On the developer's Mac
- Launched with
- uvx, Docker
- Platform
- macOS
- Publisher
- Model Context Protocol
How it works
Every agent request passes through Ferentin policy before it reaches Git (local).
It runs on the developer's Mac and talks to the AI client over stdio, so no network gateway sees it. Developers launch it with uvx mcp-server-git or docker run -i --rm mcp/git.
Ferentin's endpoint agent finds Git (local) in the MCP configuration of AI clients on managed Macs. An administrator adds it once from the local MCP catalog for every managed Mac that launches it this way. Each of its tools starts unvetted until it is approved. Ferentin records every tool call.
- AI agentAsks for something
- Ferentin policies
- Git (local) MCP serverRuns on the developer's Mac
- Governed resultChecked, logged, returned
About Git (local)
The reference MCP server for Git. It reads history and diffs and can stage and commit in a local repository.
Frequently asked about Git (local)
- How do I connect Git (local) to Ferentin?
- Enroll your Macs with the Ferentin endpoint agent, then add Git (local) from the local MCP catalog in the Ferentin admin console. Every managed Mac that launches it the way the catalog names it is covered, and each of its tools starts unvetted until you approve it.
- Is the Git (local) integration generally available?
- The Git (local) integration is currently beta on Ferentin.
Related integrations
3
Fetch (local)
The reference MCP server for fetching a web page and converting it to Markdown. It can reach any address the Mac can, including internal hosts.
Filesystem (local)
The reference MCP server for reading, writing, moving and searching files in the directories named on its command line.
Memory (local)
The reference knowledge-graph memory server. It saves what the agent chooses to remember to a local file.