Purr GitHub MCP

Why it exists

Repository automation becomes easier to review when read operations, file mutations, commits, and pull request actions are exposed as explicit tools instead of a general shell.

The project focuses on clear boundaries around what an agent can inspect and what it can change.

Current scope

The server supports repository metadata and file reads, batched text changes, branch workflows, pull requests, comments, and merge operations.

• Repository and file inspection
• Batch text commits and unified diff application
• Feature branch and pull request workflows
• Verification result comments
• Secret scanning before supported mutations

How it is used

The usual flow is inspect, prepare one coherent batch, commit to a feature branch, verify the branch with Purr Verify MCP, and merge through a pull request.

Status

The project is active. Current improvements focus on larger safe batches, clearer evidence around mutations, and dependable pull request workflows.