Niches · Code & developer platforms
Review a pull or merge request
One company's docs show a full fit.
What counts as done
A review that names files and lines, posted or returned in one run, and inline comments landing on the right diff positions when posted.
Measured, for our own tests: no finding on code that is unchanged, and the run takes under five minutes and under one US dollar of model spend. No docs we read state these figures, so they don't count against a listing here.
How agents ask for it: review MR 118
, what does this PR change and does it break anything
, read the review comments and address them
, summarise the CI failure on this PR
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. | get_merge_request include diffs with detail full_patch, save_merge_request_review create_diff_note with old_path, new_path and lines, get_job include log with byte_limit; a reviewer reports a four-minute run under one dollar. 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_pull_request get_changes returns line diffs, thread tools post comments and pipelines_build_log reads CI; but the remote server omits thread properties (#1748) and no diff size cap is documented. source |
| Entire BB Entire Inc | Trails carry approvals, findings and review-agent scores, and trail show --json lists each change with its URL; whether a comment can land on a file and line of the diff is not in the CLI reference read. source |
| GitHub MCP Server BB GitHub, Inc. | pull_request_read returns diff, files, review threads and check runs, add_comment_to_pending_review takes path and line, and /readonly limits the set; but diffs have no size cap, directory listings carry tokenised URLs (#3748), and review retrieval fails for bots under lockdown mode. source |
| graft C Vishisht Choudhary (individual) | Change requests take comments, approvals and a queue through /v1/cr/comment, /v1/reviews/approve and /v1/cr/queue; whether a comment carries a file and line was not found, and the project has one developer and no users. 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 pull request or diff tools. |
| Context7 BB Upstash | No pull request tools. |
| Git (MCP reference server) C Model Context Protocol, a Series of LF Projects, LLC | git_diff compares local revisions; no pull request or review tools. |
| GitMCP E Ido Salomon (GitMCP open-source project) | No pull request tools. |
| Graphify BB Graphify Labs | get_pr_impact maps a PR's blast radius; no diff reading or comment posting. |
| Jam MCP C Jam | No pull request tools. |
| Microsoft Learn MCP Server D Microsoft Corporation | No pull request tools. |
| ModusToolbox AI Assistant D Infineon Technologies AG | No pull request tools. |
| Momentic MCP server D Momentic | Mo tests a PR's deployed preview and reports behavioural findings; it does not read the diff or name files and lines. |
| REA BB morluto | No pull request tools. |
| Ref D Ref Software, Inc | No pull request tools. |
| Salesforce DX MCP Server C Salesforce, Inc. | No diff or review tools. |
| Sourcegraph MCP Server B Sourcegraph, Inc. | diff_search and compare_revisions read history; no pull request or review tools. |
| Superpowers B Prime Radiant (no legal form or registration found on its pages); the MIT LICENSE names Jesse Vincent | requesting-code-review and receiving-code-review review a subagent's branch inside the session, not a merge request on a host. |
| TokenEconomizer B Microsoft Corporation (repository in the microsoft GitHub organisation with Microsoft's SECURITY.md); co-authors at UC Berkeley | No pull request tools. |
| Void B Cloudflare, Inc. (VoidZero) | No pull request tools. |
What stops agents finishing
- PR review retrieval fails permission checks for bot accounts in lockdown mode
- diffs with very long lines blow past the review package size
- review thread properties missing on the remote server (Azure DevOps #1748)
Around it
Before: code.ticket-to-pr, code.host-ops. After: code.host-ops, work-trackers.update-ticket.
Where this comes from
Weight 10 of 100 in Code & developer platforms: 5 of 65 accounts (GitLab MR review, CodeRabbit first pass, CI logs via GitHub MCP, Fable reviewing Sol's work, ADO code review example); Microsoft's and GitLab's docs both lead with it
The same as data: /api/v1/use-cases/code.review-pr.json, or the MCP tool get_use_case with id code.review-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.