<!-- git-log-mcp - FastMCP server exposing a git_log tool

Written in 2026 by Amir Yalon <amir@seekingalpha.com>

To the extent possible under law, the author(s) have dedicated all copyright and related and neighboring rights to this software to the public domain worldwide. This software is distributed without any warranty.

You should have received a copy of the CC0 Public Domain Dedication along with this software. If not, see <http://creativecommons.org/publicdomain/zero/1.0/>. -->

git-log-mcp

FastMCP server exposing a single typed tool, git_log. Use this tool to investigate when a code/configuration change happened and infer why it happened from commit history. Choose it when you need commit timelines, authorship context, or intent signals from commit messages and diffs for a specific module or identifier. It is not for repository file content reads or branch manipulation; it is for history analysis and change attribution.

Installation

From the project root, run:

uv sync

Then configure your MCP client to use the full path to .venv/bin/git-log-mcp.

Example Roo Code MCP configuration:

{
  "mcpServers": {
    "git-log": {
      "command": "/full/path/to/.venv/bin/git-log-mcp"
    }
  }
}

Development

Run tests:

pytest -q