# Take a ticket through to a pull or merge request

> Take a ticket through to a pull or merge request: 1 companies fully do it, 4 with a limit, 17 carry the tag. Every listing in Code & developer platforms with the reason and a source.

- Canonical: https://www.anchorterminal.com/niches/code.ticket-to-pr/
- Markdown: https://www.anchorterminal.com/niches/code.ticket-to-pr/index.md (~1,450 tokens)
- Slim: https://www.anchorterminal.com/niches/code.ticket-to-pr/index.min.md (~280 tokens, same facts, less prose, for token-sensitive contexts)
- JSON: https://www.anchorterminal.com/niches/code.ticket-to-pr/index.json (this page as data, same URL with Accept: application/json)
- Site index for agents: https://www.anchorterminal.com/llms.txt (the key docs and every listing in one file, at most 16 MB, about 4 million tokens: https://www.anchorterminal.com/llms-full.txt)
- API: https://www.anchorterminal.com/api/v1/index.json
- MCP: https://www.anchorterminal.com/mcp (the whole catalogue as tools, no key)
- DNS: dig +short TXT <slug>.grade.anchorterminal.com (the grade as a DNS TXT record, for a sandbox with no HTTP where names still resolve; also top., best.<category>. and <a>.vs.<b>. under the zone, and the same under grade.letme.dev)
- Licence: CC BY 4.0, credit Anchor Terminal and link this page (https://www.anchorterminal.com/terms/#data)
- Updated: 2026-11-15

One company's docs show a full fit.

| Companies, full fit | With a limit | Carry the tag | Share of the category's work | First-hand accounts |
| --- | --- | --- | --- | --- |
| 1 | 4 | 17 | 12 | 9 |

## 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

The docs show it meets the test above, and nothing we read says otherwise.

- **GitLab MCP Server (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.

## Does the job, with a limit

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.

- **Azure DevOps MCP Server (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.
- **Entire (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.
- **GitHub MCP Server (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.
- **Salesforce DX MCP Server (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.

- not this job: amCharts 5 MCP Server (amCharts): No repository, git or ticket tools.
- not this job: Context7 (Upstash): No repository or git tools.
- not this job: Git (MCP reference server) (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.
- not this job: GitMCP (Ido Salomon (GitMCP open-source project)): Read-only; no write or git tools.
- not this job: graft (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.
- not this job: Graphify (Graphify Labs): Read-only graph; no git or host writes.
- not this job: Jam MCP (Jam): No repository or git tools.
- not this job: Microsoft Learn MCP Server (Microsoft Corporation): No repository or git tools.
- not this job: ModusToolbox AI Assistant (Infineon Technologies AG): No repository or git tools.
- not this job: Momentic MCP server (Momentic): No repository or git tools.
- not this job: REA (morluto): No repository or git tools.
- not this job: Ref (Ref Software, Inc): No repository or git tools.
- not this job: Sourcegraph MCP Server (Sourcegraph, Inc.): Read-only; no git or host writes.
- not this job: Superpowers (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.
- not this job: TokenEconomizer (Microsoft Corporation (repository in the microsoft GitHub organisation with Microsoft's SECURITY.md); co-authors at UC Berkeley): No repository or git tools.
- not this job: Void (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

As data: https://www.anchorterminal.com/api/v1/use-cases/code.ticket-to-pr.json, or the MCP tool get_use_case with id code.ticket-to-pr. Draft, read 2026-11-12 from public docs and first-hand accounts, not yet reviewed by a person.

---

Query this catalogue directly over MCP: https://www.anchorterminal.com/mcp (Streamable HTTP, no key). How: https://www.anchorterminal.com/agents/#mcp
