Mcp Git

io.github.infoinlet-marketplacePublished by GitHub account infoinlet-marketplacev0.1.1Updated Oct 24, 2026

Read-only Git inspection for AI agents — log, show, diff, status, blame, grep. No writes.

VerifiedSTDIODesktop onlyDeveloper Tools

Overview

AI-generated overview

A local MCP server that gives an AI assistant read-only Git inspection: log, show, diff, status, blame and grep, with no write operations.

What you can do
Inspect commit history and individual commits with log and show, including diffs of changes between revisions or the working tree. Check repository state with status and trace line-level authorship with blame. Search tracked content with grep. All operations are read-only, so the assistant cannot commit, push or modify files through this server.
When to use it
Useful when you want an assistant to explain recent changes, review a diff, find when a line was introduced, or locate code by pattern in a local repository without giving it the ability to change anything.
Requirements
Runs as a local process over stdio, installed from the npm package @infoinlet/mcp-git, so Node.js and npm are needed. It must run on a desktop machine with access to the Git repositories to inspect. No authentication, environment variables or headers are declared.
Before you install
The server is described as read-only with no writes, but it still reads repository contents and history, including any secrets committed to the repo, and passes them to the assistant. Review which repositories it can reach before installing.

Installation

In SourceWeft

  1. Open Mcp Git in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

README

This repository has no README.

Tools

0
SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

1
  1. v0.1.1LatestSep 16, 2026

Score

25% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 days25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • License10 pts

    Declare a license in the repository or the registry entry.