Niches · Code & developer platforms
Take a ticket through to a pull or merge request
One company's docs show a full fit.
What counts as done
A branch exists on the host with the change, a PR or MR is open against the right base with a description that links the ticket, the ticket state is updated, and the run ends on its own with the PR URL in its output.
How agents ask for it: pick up the ticket assigned to me and push a fix
, implement issue 17 and open a PR
, watch for new tickets and complete them
, open a merge request for this branch
Does the job 1
The docs show it meets the test above, and nothing we read says otherwise.
| Listing | Why |
|---|---|
| GitLab MCP Server B GitLab Inc. | add_branch, add_commit with file actions, save_merge_request and save_work_item open and update the objects, a fine-grained PAT works with no browser, and one account runs the Jira-to-MR flow on it daily. source |
Does the job, with a limit 4
It does the job, but something in the docs or a user's account will get in an agent's way. The limit is named in each row.
| Listing | Why |
|---|---|
| Azure DevOps MCP Server B Microsoft Corporation | repo_create_branch, repo_pull_request_write create and wit_work_item_link_write link_to_pull_request exist, and the local server takes a PAT or bearer token from an environment variable; but no tool commits or pushes files, so git must do that step. source |
| Entire BB Entire Inc | entire trail create opens a trail with a branch, trail link attaches another branch and trail update changes status; the agent pushes with git-remote-entire over entire:// URLs, and an unattended run needs a service-account secret in ENTIRE_TOKEN. source |
| GitHub MCP Server BB GitHub, Inc. | create_branch, push_files, create_or_update_file, create_pull_request and issue_write cover the flow with GITHUB_PERSONAL_ACCESS_TOKEN or a Bearer header, and release binaries avoid Docker; but a reviewer failure makes create_pull_request report an error after the PR exists (#3756), so a retry duplicates. source |
| Salesforce DX MCP Server C Salesforce, Inc. | The devops toolset checks out a DevOps Center work item's branch, commits to it, opens its pull request and sets its status; but only inside DevOps Center, the ten tools carry no annotations, and the server reached end of life on 2 November 2026. source |
Doesn't do this job 16
Listings in the category that do something else, with the reason.
| Listing | Why |
|---|---|
| amCharts 5 MCP Server B amCharts | No repository, git or ticket tools. |
| Context7 BB Upstash | No repository or git tools. |
| Git (MCP reference server) C Model Context Protocol, a Series of LF Projects, LLC | No remote operations, so it cannot push or open a pull request; the README says to push with another tool. source |
| GitMCP E Ido Salomon (GitMCP open-source project) | Read-only; no write or git tools. |
| graft C Vishisht Choudhary (individual) | No ticket tracker; gft cr create opens a change request on a changeset, but nothing links a ticket or returns a hosted URL. |
| Graphify BB Graphify Labs | Read-only graph; no git or host writes. |
| Jam MCP C Jam | No repository or git tools. |
| Microsoft Learn MCP Server D Microsoft Corporation | No repository or git tools. |
| ModusToolbox AI Assistant D Infineon Technologies AG | No repository or git tools. |
| Momentic MCP server D Momentic | No repository or git tools. |
| REA BB morluto | No repository or git tools. |
| Ref D Ref Software, Inc | No repository or git tools. |
| Sourcegraph MCP Server B Sourcegraph, Inc. | Read-only; no git or host writes. |
| Superpowers B Prime Radiant (no legal form or registration found on its pages); the MIT LICENSE names Jesse Vincent | finishing-a-development-branch hands the PR step to the harness's own gh or MCP; Superpowers adds no host tool. |
| TokenEconomizer B Microsoft Corporation (repository in the microsoft GitHub organisation with Microsoft's SECURITY.md); co-authors at UC Berkeley | No repository or git tools. |
| Void B Cloudflare, Inc. (VoidZero) | No repository or ticket tools. |
What stops agents finishing
- push_files leaves an orphan branch when the push fails
- create_pull_request reports failure after the PR exists
- a sandbox without Docker cannot run the stdio server image
- a login token that expires in 8 hours and is never refreshed (Entire)
Around it
Before: work-trackers.read-ticket, agent-harnesses.scheduled-job. After: code.review-pr, code.commit-from-sandbox.
Where this comes from
Weight 12 of 100 in Code & developer platforms: 8 of 65 accounts describe an agent carrying a ticket to a PR or MR (GitHub via gh or MCP, GitLab MCP with Jira, Azure DevOps); weighted up slightly because it is the end state the host-ops accounts build towards
The same as data: /api/v1/use-cases/code.ticket-to-pr.json, or the MCP tool get_use_case with id code.ticket-to-pr. Other jobs in this category: /api/v1/niches?category=code.
For companies
Do agents find, use and choose your tools?
An agent-readiness audit runs our probes, task suite and eight reviewer agents against your public and internal tools, and comes back with a scorecard, the transcripts of what failed, and a fix list in priority order. From $2,500, re-run included. We never take payment to move a rank. We do help companies earn one.