cyanheads/git-mcp-server

A Git MCP server for AI agents. STDIO & Streamable HTTP.

This repository also configures its own agents. See what git-mcp-server tells them →

242Stars on the repository
8Mods indexed here, across every type
21d agoLast push, which is what freshness is scored on
Apache-2.0Licence, which decides whether bodies are shown

maintenance

01

cyanheads/git-mcp-server

Skill Claude CodeCodex

Investigate, adopt, and verify dependency updates. Captures what changed, understands why, cross-references against the codebase, and runs final checks. Supports two entry modes: run the full flow end-to-end, or review updates you already applied.

not rated 242 +1 21d ago A SkillSpector: pass 53 tokens original Apache-2.0

polish-docs-meta

02

cyanheads/git-mcp-server

Skill Claude CodeCodex

Finalize documentation and project metadata for a ship-ready release. Use after implementation is complete, tests pass, and devcheck is clean. Safe to run at any stage — each step checks current state and only acts on what still needs work.

not rated 242 +1 21d ago A SkillSpector: pass 53 tokens original Apache-2.0

release-and-publish

03

cyanheads/git-mcp-server

Skill Claude CodeCodex

Ship a release end-to-end across every registry this project targets (npm, MCP Registry). Runs the final verification gate, pushes commits and tags, then publishes to each applicable destination. Assumes git wrapup (version bumps, changelog, commit, annotated tag) is already complete — this skill is the post-wrapup…

not rated 242 +1 21d ago A SkillSpector: warn 83 tokens original Apache-2.0

report-issue

04

cyanheads/git-mcp-server

Skill Claude CodeCodex

File a bug or feature request against this repository (cyanheads/git-mcp-server) using the gh CLI. Use for tool logic bugs, git provider misbehavior, transport issues, auth/config problems, or new feature proposals.

not rated 242 +1 21d ago A SkillSpector: warn 51 tokens original Apache-2.0

At most 3 mods per repository are shown here, and a mod shipped inside a plugin is left to that plugin's page — the rest are on their repository pages: