Skip to main content
Glama
modelcontextprotocol

git MCP server

Official

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault

No arguments

Instructions

Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.

This server publishes no instructions, or was last inspected before Glama recorded them.

Capabilities

Features and capabilities supported by this server

Protocol revision2025-11-25

CapabilityDetails
tools
{
  "listChanged": false
}
prompts
{
  "listChanged": false
}
resources
{
  "subscribe": false,
  "listChanged": false
}

Tools

Functions exposed to the LLM to take actions

NameDescription
git_statusB

Shows the working tree status

git_diff_unstagedB

Shows changes in the working directory that are not yet staged

git_diff_stagedB

Shows changes that are staged for commit

git_diffC

Shows differences between branches or commits

git_commitD

Records changes to the repository

git_addC

Adds file contents to the staging area

git_resetB

Unstages all staged changes

git_logC

Shows the commit logs

git_create_branchC

Creates a new branch from an optional base branch

git_checkoutC

Switches branches

git_showB

Shows the contents of a commit, or of a file or directory given as :

git_branchC

List Git branches

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

B3/5.0

Scored across 12 tools

Disambiguation4/5

The three diff tools (git_diff_unstaged, git_diff_staged, git_diff) are distinguished by scope, but an agent must read descriptions carefully to choose correctly. Other tools target unique actions/resources, with only minor overlap between git_show and git_log.

Naming Consistency5/5

All tools consistently use a git_ prefix and snake_case, matching familiar Git subcommands. No mixed conventions or ambiguous naming styles are present.

Tool Count5/5

12 tools is well-scoped for a Git server covering core local operations. Each tool earns its place without excessive bloat or thin coverage.

Completeness3/5

The set covers staging, committing, diffing, branching, checkout, log, and show, but omits notable Git lifecycle operations such as branch deletion, merge, rebase, remote push/pull, and stash. Core local workflows work, but the surface is not complete for general Git use.

Maintenance

ActivityActive
ResponsivenessWithin a week