github-mcp-server get_commit adds include_patch parameter
Introduced 2026-06-08 · score 0.95
HOW TO USE IT
When reviewing a repository change and you need the patch, call `get_commit` with the repository owner, name, commit SHA, and `detail: "full_patch"`.
get_commit(owner: "<owner>", repo: "<repo>", sha: "<commit-sha>", detail: "full_patch")WHY THIS HELPS
Retrieve commit details while reviewing a repository change where the patch is needed.
REQUIREMENTS AND LIMITATIONS
- Version: v1.2.0
- owner (required): Repository owner.
- repo (required): Repository name.
- sha (required): Commit SHA, branch name, or tag name.
- detail: Use `full_patch` to include unified diff content for each changed file; it can be very large. Default is `stats`.
- Prerequisite: The tool requires the `repo` OAuth scope.
- Docs conflict: The v1.2.0 README documents optional `detail` (`none`, `stats`, `full_patch`) and does not document `include_patch`; this differs from the release note's named parameter. Use the documented `detail: "full_patch"` form for v1.2.0.
FIRST-PARTY EVIDENCE
- https://github.com/github/github-mcp-server/releases/tag/v1.2.0
- https://github.com/github/github-mcp-server/blob/v1.2.0/README.md
Check the installed version and the source before using it. Entry JSON