Git for git workflows
For git workflows, the reference Git server is the top pick of four, because it operates directly on the repository on disk, which is where the workflow actually begins. This Anthropic reference server runs the core operations, status, diff, branch, commit, log, on a local repo, the foundation everything else builds on.
It ranks first because the mechanical heart of any git workflow is local. Before a pull request or CI, there is a working tree to stage, commit, and branch, and that is exactly what this server handles.
How Git fits
git_status shows the working tree, git_diff_unstaged and git_diff_staged show changes before and after staging, and git_diff compares branches or commits. git_add stages, git_commit records with a message, and git_reset unstages. git_create_branch and git_checkout move work onto a branch, git_log and git_show read history, and git_branch lists branches. With that set an agent can do the day-to-day mechanics: branch, stage, commit, and inspect a diff on the repo in front of it.
The siblings add the hosted side this server leaves out. GitHub covers pull requests, issues, code search, reviews, and Actions, so a change can travel from commit to merged PR. GitLab and Bitbucket are the picks when your code and reviews live on those platforms instead. The Git server does not reach any hosted forge; it works on the local checkout. Pair it with whichever hosted server matches where your reviews happen.
Tools you would use
| Tool | What it does |
|---|---|
| git_status | Shows the working tree status. |
| git_diff_unstaged | Shows changes in the working directory not yet staged. |
| git_diff_staged | Shows changes that are staged for commit. |
| git_diff | Shows differences between branches or commits. |
| git_commit | Records staged changes to the repository with a message. |
| git_add | Adds file contents to the staging area. |
| git_reset | Unstages all staged changes. |
| git_log | Shows the commit logs with optional date filtering. |
| git_create_branch | Creates a new branch from an optional base. |
| git_checkout | Switches to the given branch. |
FAQ
- Why is the local Git server the first pick for git workflows?
- Because the workflow starts on disk. git_add, git_commit, git_create_branch, git_diff, and git_log handle the core mechanics on the local repo, the steps that happen before anything reaches a hosted platform. The forge servers build on top of that base.
- Does the Git server open pull requests?
- No. Its tools operate on the local repository, commits, branches, diffs, history, not on a hosted forge. For pull requests and reviews use GitHub, GitLab, or Bitbucket depending on where your code lives. The Git server handles the local half of the workflow.