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.
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"
}
}
}
Run tests:
pytest -q