1. Conduid
  2. Developer Tools
  3. Git Blame
MCP server · Developer Tools

Git Blame

by · github.com/KhanhPham2411/mcp-git-blame

MCP server: Git Blame

Unclaimed last commit 9 months ago devtools
InstallView source
39Low

Scored 3 months ago · breakdown

About Git Blame

Git Blame is an MCP server published by KhanhPham2411 in the Developer Tools category: mCP server: Git Blame. It has been installed 0 times through Conduid.

The repository has 1 stars and 0 forks, with the last commit 9 months ago. Six months or more without a commit doesn't mean the server is broken, but check the open issues (0) before depending on it in production.

Install

Install
npx mcp-git-blame

This server has no ConduID identity, so agent calls to it are not receipted. Pin the version you install and review the source before granting it credentials.

Ask AI

✦

Ask AI about Git Blame

Powered by Claude · Grounded in docs

I know everything about Git Blame. Ask me about installation, configuration, usage, or troubleshooting.

Security checks

  • ·README presentNot checked yet.
  • ·License declaredNot checked yet.
  • ·Tests presentNot checked yet.
  • ·Dependencies pinnedNot checked yet.
  • ·No dynamic code executionNot checked yet.
  • !Scoped permissionsDoesn't declare a permission scope. Assume it can do anything its process can.

README

MCP Git Local Blame Server

An MCP (Model Context Protocol) server that provides git local blame information for files and specific line ranges.

Features

  • Get git blame information for entire files
  • Get git blame information for specific line ranges
  • Detailed commit information including author, committer, timestamps, and commit messages
  • Works with any git repository

Screenshot

Sample Output

Installation

  1. Install dependencies:
npm install
  1. Build the project:
npm run build

Usage

Running the Server

npm start

Or for development:

npm run dev

Available Tools

git_blame

Retrieves git blame information for a file or specific lines.

Parameters:

  • filePath (string, required): Full path to the file to get blame information for
  • lineFrom (number, optional): Starting line number (1-based)
  • lineTo (number, optional): Ending line number (1-based)

Example Usage:

Get blame for entire file:

{
  "name": "git_blame",
  "arguments": {
    "filePath": "/path/to/your/file.js"
  }
}

Get blame for specific lines (10-20):

{
  "name": "git_blame",
  "arguments": {
    "filePath": "/path/to/your/file.js",
    "lineFrom": 10,
    "lineTo": 20
  }
}

Response Format:

The server returns detailed blame information including:

  • File path and line range information
  • For each line:
    • Line number
    • Commit hash
    • Author name and email
    • Author timestamp and timezone
    • Committer name and email
    • Committer timestamp and timezone
    • Commit summary/message
    • Previous commit hash and filename
    • Line content

Development

The server is built with TypeScript and uses:

  • @modelcontextprotocol/sdk for MCP protocol implementation
  • simple-git for git operations

Cursor Integration

To add this server to Cursor, add the following to your Cursor MCP configuration:

{
  "mcpServers": {
    "command": "node",
    "args": ["{your-folder}/mcp-git-blame/dist/index.js"],
    "env": {}
  }
}

License

MIT

README mirrored from the source repository 3 months ago. The original is authoritative.

Questions

About Git Blame

How do I install Git Blame?

Run npx mcp-git-blame, then add the server to your MCP client's configuration. Conduid has recorded 0 installs, so the command is known to work with current clients.

Is Git Blame safe to use with an AI agent?

Its trust score is 39 out of 100 (low). It passes 0 of 1 static security checks; the failures are listed above. It has no ConduID identity yet, so agent calls to it are not receipted.

Is Git Blame still maintained?

The last commit was 9 months ago, with 0 open issues. That's long enough that you should check whether the maintainer is responding to issues before depending on it.