A
license-
qualityB
maintenanceEnforces team knowledge and workflow policies for AI coding agents by providing context, decisions, and gates before code changes are made.
1
Apache 2.0
mcp-merge-guard
by paolino
This server provides MCP tools to manage pull request merging with guardrails:
check-merge-ready: Validates merge readiness for a PR without performing any action. Checks CI status (all checks must pass, none pending/failed), required approvals (approved or no review required), no merge conflicts, and optionally that the branch is up-to-date with the base branch.
guard-merge: Atomically validates the same conditions and, if all pass, merges the PR using the specified method:
merge,squash, orrebase. Rebase is refused unlessallowSignatureStrippingis explicitly set, to protect signed commits. Optionally enforces branch freshness (requireUpToDate) and, iflocalRepoPathis provided, updates the local base branch via GitHub HTTPS fast-forward after a successful merge.
Both tools require the repository owner, name, and PR number.
Provides tools to validate and perform pull request merges on GitHub, checking CI status, approvals, merge conflicts, and branch freshness, with support for merge methods such as merge, squash, and rebase.
Click on "Install Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@mcp-merge-guardCheck if PR #42 in owner/repo is ready to merge"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
mcp-merge-guard
MCP server that guards PR merge decisions by validating CI, approvals, conflicts, and branch freshness.
Features
check-merge-ready - Query-only status check that validates all guards
guard-merge - Atomic validate-then-merge that refuses if guards fail
Default merge method is
merge(preserves signed branch commits)Rebase is refused unless
allowSignatureStripping: trueis passedOptional
localRepoPathsupport updates the local base branch after merge without relying on the clone's remote protocol
Related MCP server: mcp-pr-reviewer
Guards
Guard | Description |
ci-status | All CI checks passed, none pending or failed |
approval | PR is approved (or no review required) |
conflicts | No merge conflicts |
up-to-date | Branch is current with base (optional, off by default) |
merge-method-policy | Rebase refused unless allowSignatureStripping is set |
Installation
Requires gh CLI installed and authenticated.
With Nix (recommended)
Add to your Claude Code settings (~/.claude/settings.json):
{
"mcpServers": {
"merge-guard": {
"command": "nix",
"args": ["run", "github:paolino/mcp-merge-guard"]
}
}
}Or use /settings in Claude Code to add the MCP server through the UI.
From source
git clone https://github.com/paolino/mcp-merge-guard
cd mcp-merge-guard
npm install && npm run buildAdd to ~/.claude/settings.json (use absolute path):
{
"mcpServers": {
"merge-guard": {
"command": "node",
"args": ["/absolute/path/to/mcp-merge-guard/dist/index.js"]
}
}
}Restart Claude Code after adding the configuration.
Usage
Once configured, use the tools in Claude Code:
Check if PR #42 in owner/repo is ready to mergeMerge PR #42 in owner/repo if all guards passDocumentation
Full documentation at paolino.github.io/mcp-merge-guard
Development
just install # Install dependencies
just build # Build TypeScript
just test # Run tests
just CI # Full CI pipelineLicense
MIT
Maintenance
–Maintainers
–Response time
0dRelease cycle
3Releases (12mo)
Commit activity
Issues opened vs closed
Resources
Unclaimed servers have limited discoverability.
Looking for Admin?
If you are the server author, to access and configure the admin panel.
Tools
Related MCP Servers
- Alicense-qualityDmaintenanceAnalyzes GitHub Pull Requests using AI via MCP, providing detailed feedback and approve/reject decisions.71MIT
- FlicenseAqualityDmaintenanceEnables safe GitHub automation by queuing write operations for admin approval before execution.6
- FlicenseAqualityCmaintenanceStreamlines GitHub PR workflows, monitors CI/CD, and sends Slack notifications. Provides tools for PR analysis, CI monitoring, and follow-up tasks.7
Related MCP Connectors
Git-native policy layer for AI agents: check_action verdicts against rules approved via PR.
Screens public GitHub repos and PRs to generate risk maps, findings, and merge-readiness signals.
A Model Context Protocol (MCP) application for automated GitHub PR analysis and issue management.…
Latest Blog Posts
- Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)By Om-Shree-0709 on .mcpAgent IdentityOAuth 2.1
- Your AI Chatbot Just Exposed Your CEO's Salary to an InternBy Om-Shree-0709 on .Agent IdentityMCP SecurityOAuth Delegation
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/paolino/mcp-merge-guard'
If you have feedback or need assistance with the MCP directory API, please join our Discord server