Local clone or hosted repo?

Both are covered. git_log reads from a checkout on disk, which suits an agent already working in a local clone. GitHub and Gitea list commits through their APIs, which is what you want when the code lives on the host and the agent has no local copy.

What can an agent do with a commit list?

Plenty: write a changelog, find when a line changed, summarize recent work, or pick the commit to revert. The list gives messages, authors, and timestamps; from there an agent reads a specific file or diff for the detail.

MCP servers that can list commits

3 verified servers expose a tool that can list commits in a repository

When an agent needs to understand what changed and when, it reads the commit log. Listing commits is how it sees the history of a branch: who touched what, in what order, leading up to now.

These verified servers let an agent list commits in a repository.

Top pick

GitHub

Official

GitHub's official remote MCP server for repos, issues, pull requests, Actions, and code search.

version-control30,334

Tool:

list_commits

list_commits returns commits on a branch of a GitHub repository, the hosted-repo read an agent uses to summarize changes or trace a regression.

Pick 2

Git

Anthropic (Model Context Protocol)

Official

Reference MCP server for local Git: status, diffs, commits, branches, and history on a repo path.

version-control86,565

Tool:

git_log

git_log reads the commit log straight from a local checkout, with optional date filtering, the plain-git path for an agent working on disk.

Pick 3

Gitea

Official

Gitea's official MCP server for repos, branches, issues, pull request reviews, releases, Actions, and wikis on any Gitea instance.

version-control73

Tool:

list_repo_commits

list_repo_commits lists commits in a self-hosted Gitea repository, the same history read on a forge you run yourself.

What to know

The commit log is context an agent uses constantly: to write a release note, to find when a bug was introduced, to summarize a week's work. The three servers here cover local and hosted git. Plain git reads the log from a checkout on disk, with date filtering. GitHub and Gitea list commits on a branch through their APIs, which is what an agent uses when the repo lives on a host rather than a local clone. All return the same shape: commits with messages, authors, and timestamps.

History does not change, which makes it worth reading once and remembering. An agent re-listing the same commits every session to rebuild a picture of recent work is spending tokens on a fact that was already settled.

Questions

Local clone or hosted repo?: Both are covered. git_log reads from a checkout on disk, which suits an agent already working in a local clone. GitHub and Gitea list commits through their APIs, which is what you want when the code lives on the host and the agent has no local copy.
What can an agent do with a commit list?: Plenty: write a changelog, find when a line changed, summarize recent work, or pick the commit to revert. The list gives messages, authors, and timestamps; from there an agent reads a specific file or diff for the detail.