Will it merge even if checks are failing?

Generally no, if your branch protection says so. These tools merge through the host's normal rules, so required checks and approvals still gate the merge. The tool performs the action; the repository's protections decide whether it is allowed, which is why branch protection matters more than ever once an agent holds a merge tool.

Can the agent choose how to merge?

On the hosts that support it, yes: a merge commit, a squash, or a rebase, the same options a person sees in the UI. Pick the method your repo standardizes on so an agent-merged PR looks like any other.

MCP servers that can merge a pull request

3 verified servers expose a tool that can merge a pull request

Opening a PR is the start; merging it is the commit. When an agent has approval and green checks, a merge tool lands the change into the base branch, the step that turns a proposal into shipped code.

These verified servers let an agent merge a pull request on the major code hosts.

Top pick

GitHub

Official

GitHub's official remote MCP server for repos, issues, pull requests, Actions, and code search.

version-control30,334

Tool:

merge_pull_request

merge_pull_request lands a PR into its base branch with the chosen merge method and the repository's branch-protection rules applied, the default for GitHub-hosted code.

Pick 2

Bitbucket

MatanYemini

Community

A maintained MCP server for Bitbucket Cloud and Server: browse repos, drive pull requests, comments, tasks, and pipelines.

version-control143

Tool:

mergePullRequest

Bitbucket's mergePullRequest lands a PR once its conditions are met, the same final step for teams whose code lives there.

Pick 3

Gitea

Official

Gitea's official MCP server for repos, branches, issues, pull request reviews, releases, Actions, and wikis on any Gitea instance.

version-control73

Tool:

merge_pull_request

On a self-hosted Gitea instance, merge_pull_request closes the loop on a forge you run in-house.

What to know

Merging is the highest-consequence write in a code workflow, so it is the one you most want a human or a gate in front of. Most of these tools let you choose the merge method, a merge commit, a squash, or a rebase, and they refuse when checks are failing or approvals are missing. That is the behavior you want: the agent proposes, branch protection decides. Treat an agent that can merge with the same care as one that can deploy.

A merge is also a point of no return the next session should know about. An agent that merges a PR, then later cannot tell whether it already did, risks acting on a stale view of the branch. Whether a change has landed is exactly the kind of state worth carrying forward rather than re-deriving from the diff.

Questions

Will it merge even if checks are failing?: Generally no, if your branch protection says so. These tools merge through the host's normal rules, so required checks and approvals still gate the merge. The tool performs the action; the repository's protections decide whether it is allowed, which is why branch protection matters more than ever once an agent holds a merge tool.
Can the agent choose how to merge?: On the hosts that support it, yes: a merge commit, a squash, or a rebase, the same options a person sees in the UI. Pick the method your repo standardizes on so an agent-merged PR looks like any other.