Mcp Git
Let your coding agent inspect local repo history, diffs, and blame without running fragile shell one-liners.
Overview
io.github.infoinlet-marketplace/mcp-git is a MCP server for the Build phase that gives AI agents read-only local Git inspection (log, show, diff, status, blame, grep) with no write operations.
What is this MCP server?
- Six read-only Git operations: log, show, diff, status, blame, and grep
- No write paths—safer for autonomous agents than full git CLI
- Stdio MCP transport via npm package @infoinlet/mcp-git v0.1.1
- Works against the agent’s current working tree for quick context pulls
- Fits code review prep and “what changed?” debugging without pushing commits
- 6 read-only git inspection operations documented
- Package version 0.1.1 on npm as @infoinlet/mcp-git
What problem does it solve?
Agents that only see open files miss commit context, and handing them full git write access is risky when you ship alone.
Who is it for?
Solo builders who want safer, structured git context during implementation and review in a local clone.
Skip if: Teams that need the agent to create branches, commit, merge, or open PRs without a separate GitHub write integration.
What do I get? / Deliverables
After you register the server, your agent can quote accurate history and diffs from the repo while you keep write operations under your control.
- Structured git log, show, diff, status, blame, and grep responses inside agent chats
- Read-only repo intelligence without automated commits or pushes
Recommended MCP Servers
Journey fit
Git read tools sit on the Build shelf because they support day-to-day implementation and integration work in cloned repos. Integrations is the canonical facet for MCP bridges that expose developer tooling to agents alongside other dev APIs.
How it compares
Local read-only git MCP tools, not a hosted GitHub API bridge or a planning skill.
Common Questions / FAQ
Who is io.github.infoinlet-marketplace/mcp-git for?
Indie developers and small teams using AI coding agents who need trustworthy read-only git context in the repo they already have open.
When should I use io.github.infoinlet-marketplace/mcp-git?
Use it during Build or Ship prep when you need log, diff, status, blame, or grep answers without letting the agent mutate git state.
How do I add io.github.infoinlet-marketplace/mcp-git to my agent?
Install @infoinlet/mcp-git from npm, add the stdio MCP server entry in Claude Code or Cursor per your host’s MCP config, and point it at your project directory.