MCP servers that can open a pull request

4 verified servers expose a tool that can open a pull request

A coding agent that writes a change should be able to propose it the way a person does: push a branch, open a pull request, and let CI and a reviewer take it from there. The servers for the major code hosts expose that as a single call.

These verified servers let an agent open a pull request, with the exact tool each host uses.

Top pick

GitHub

GitHub

Official

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

version-control30,334
Tool:
  • create_pull_request

Opens a PR with create_pull_request, the issue, review, and comment tools sitting right alongside. The default for agents working in GitHub repos.

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
Tools:
  • createPullRequest
  • createDraftPullRequest
  • createPullRequestTask

Separates draft from ready PRs (createDraftPullRequest) and attaches review tasks (createPullRequestTask), the checklist items that fit a structured Bitbucket review process.

Pick 3

Gitea

Gitea

Official

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

version-control73
Tools:
  • create_pull_request
  • create_pull_request_reviewer
  • create_pull_request_review

Opens the PR and assigns reviewers in the same server, a good fit for self-hosted Gitea where you want the agent to route review without leaving the forge.

Pick 4

Salesforce

Salesforce

Official

Salesforce's official DX MCP server: query org data with SOQL, deploy and retrieve metadata, manage orgs, run tests, and build LWC from your agent.

crm412
Tool:
  • create_devops_center_pull_request

create_devops_center_pull_request commits local changes onto a DevOps Center work item's feature branch, the PR step only when your release process runs through the Salesforce platform rather than a code host.

What to know

What the agent can attach to the PR varies. A title, body, and a head-and-base branch pair is the baseline. Gitea can assign reviewers on the PR through create_pull_request_reviewer; Bitbucket instead adds review tasks with createPullRequestTask, the checklist items a reviewer ticks before merge, and supports draft PRs. GitHub keeps the create call lean and leaves reviewers and labels to its broader tool set.

A PR is a handoff: the agent knows why each line changed, the reviewer sees only the diff, and the description is the one place that reasoning survives. An agent that recalls the decisions behind a change writes a far better PR body than one reconstructing intent from the diff alone.

Questions

Can the agent open a draft pull request?
On Bitbucket, yes, through createDraftPullRequest. Other servers expose a single create call and leave draft state to a follow-up edit or a flag on the request. Drafts are useful when you want the agent to stage a change for human review without triggering CI or notifications immediately.
Does opening a PR also push the branch?
No. A pull request references an existing branch, so the agent needs to have committed and pushed the work first (through the same server's file or commit tools, or the local git workflow). The create_pull_request call links two branches; it does not create the code.