Model Context Protocol Git MCP Server

The MCP reference server's Git MCP server provides AI agents with local version control tools to inspect commit logs, stage modified files, create feature branches, and generate unified diffs. It empowers autonomous coding agents to navigate version trees, track codebase changes, and perform source control operations.

Start for free

Benefits with Ory + Model Context Protocol Git MCP Server

The Git MCP reference server from the Model Context Protocol project lets your agents work with local Git repositories: checking status and diffs, reading history, staging changes, committing, and managing branches. It has no permission model of its own, so every connected agent gets the same reach into the repository. Ory Agent Security lets reviewers read diffs and history while only the coding agents you approve can commit, and every operation is recorded with the user and agent behind it.

View on GitHub

Use Cases

— 01 use case

Agent IAM

Reviewers inspect diffs at Read, coding agents commit at Write, resets wait for an Admin agent, and everyone else is set to Block for Git.

Explore Agent IAM

Core Functionality

— 04 capabilities

Read, write, admin, or no access
Ory Agent Security classifies every tool on the Git MCP reference server as read, write, or admin, so you can give each user, team, or agent type only the level it needs: read for review agents, write for coding agents that commit for their user, admin for agents you trust with a user's working tree, and no access for agents outside your coding workflow.
Enforced before execution
Ory Agent Security checks each tool call against the user, the agent acting for them, and any sub-agent inside the agent harness, so a denied commit stops before it reaches the repository, with nothing to roll back and no gateway to deploy.
Observe, then enforce
Observe mode shows which agents commit and on whose behalf without blocking anything, so you can apply Ory's pre-built policy for the Git MCP reference server and enforce it on your own schedule.
Complete audit trail
Every allow and deny decision on the Git MCP reference server streams to your SIEM through OpenTelemetry with the user, agent, and action attached, so you can show which agent made a commit and for which user.