Git Official

Read repository history, diffs and branches as tools an agent can call.

LLM Mart 27 views 2.6k listing impressions

Exposes a local git repository: status, diffs, log, branches, and the contents of a file at a given revision.

What it changes about an agent's answers

Without it, an agent reasons about your code as it is right now and has no idea why any of it looks that way. With history in reach, "why is this check here" is answerable — it can find the commit that added the line and read the message. In practice that is the difference between an agent that rewrites a workaround and one that notices it was deliberate.

Where it fits

Review and archaeology rather than authoring: summarising a branch before a pull request, explaining a regression window, working out what a release actually changed.

Worth knowing

  • It reads; it is not a way to let an agent commit and push on your behalf, and you should be glad about that.
  • A repository with a very large history will produce very large tool results. Ask for a range rather than the whole log.

Related servers

PostgreSQL Official

Let an agent inspect a Postgres schema and run read-only queries.

stdio
@modelcontextprotocol/server-postgres 38 views
Fetch Official

Fetch a web page and hand the agent readable text instead of raw HTML.

stdio
mcp-server-fetch 33 views
Filesystem Official

Give an agent scoped read and write access to directories you choose.

stdio
@modelcontextprotocol/server-filesystem 29 views

Read-only MCP server for the OrchestKit docs: full-text search + Markdown fetch. No auth.

24 views