Skip to main content
Glama
601,754 tools. Updated 2026-09-23 05:53

"Tool or method to view git logs and compare code changes across commits" matching MCP tools:

  • View commit logs or compare file changes between revisions. Filter by author, date range, or revision range to analyze project history.
    MIT
  • Inspect Git commit logs, recent changes, diffs, or line blame across repository files to trace history, review edits, and identify code ownership.
    MIT
  • Get files and symbols changed since a git ref as JSON, including uncommitted working-tree changes, to focus review or testing on relevant code.
    MIT
  • Organize code changes into well-structured commits with clear messages. Break large modifications into smaller, logical commits for better history.
    MIT
  • Track dependency graph evolution across git history by sampling commits to reveal file, symbol, and edge count changes over time.
    Business Source 1.1
  • Analyze how changes to a method in a specific class affect downstream code. Identify potential impacts before implementing modifications.
    Mozilla Public 2.0

Matching MCP Servers

Matching MCP Connectors

  • Compare quality changes between git branches or commits. Identify new findings and resolved issues to review pull request impact on code quality.
    MIT
  • Compare branches or commits to identify changes in a Git repository. Specify the target and optional context lines to view detailed diffs.
    MIT
  • Query Git commit history to understand changes, debug regressions, and find commit context. Search by keyword, file, or blame.
    MIT
  • Show differences between the working tree, index, and commits to review changes before staging or committing, or to compare two commits.
    MIT
  • Roll back a local repository by N commits using git reset --hard, discarding uncommitted changes and rolled-back commits. Inspect what would be lost with diff/dry-run, or back up first, before executing.
    MIT
    Destructive
  • Automates Git commits by detecting changes, generating conventional commit messages, staging, committing, and optionally pushing to remote repositories while updating CHANGELOG.
    MIT
  • Reset a Git repository to a target commit (default HEAD) in soft, mixed, or hard mode to undo commits, unstage changes, or discard working tree changes. Preview impact before confirming.
    MIT
    Destructive
  • View unstaged Git changes with numbered lines to selectively stage specific modifications or new files for creating focused commits.
    MIT
  • Stage specific lines or ranges from Git changes for partial commits, enabling multiple logical commits from a single file with intermixed changes, including untracked files.
    MIT
    Destructive
  • Organize multiple Git changes into separate, focused commits using guided sessions with step-by-step instructions and change statistics.
    MIT
  • Check git repository status to view current branch, uncommitted changes, and staged/modified/untracked files before committing.
    Apache 2.0
  • Convert a complex method into a method object class whose __call__ holds the method body, with the original method delegating to it. Preview changes first; set apply=true to write.
    MIT
  • Create a cryptographically signed Git commit envelope with Ed25519 provenance metadata, recording actor and tool for auditability.
    Apache 2.0
  • Collect a git repository's recent commits, branch, and origin URL for use in partial incident analysis pipelines. Returns a read-only snapshot of the last 14 days (up to 200 commits).
    MIT