Niches · Code & developer platforms
Read and act on issues, pull requests and CI on a code host
No company's docs show a full fit yet. The listings below do the job with a limit, or not at all.
What counts as done
The named issue, PR, run or work item is returned or changed, the response names the object (number and URL), a failed write reports what was and was not changed, and the tool list loaded for the task is under 20 tools.
Measured, for our own tests: the object is returned or changed in at most three tool calls. No docs we read state these figures, so they don't count against a listing here.
How agents ask for it: list the open issues on this repo
, what did CI say about this PR
, comment on issue 42
, which PRs need my review
, get my sprint work items
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 | X-MCP-Toolsets and X-MCP-Readonly cut the list to one domain, and wit_work_item, repo_pull_request and pipelines_build cover the asks; but a saved query over 20,000 items returns an empty success (#1737), wiki paging drops its token (#1694), and Claude Code needs an Entra app registration. source |
| Entire BB Entire Inc | entire trail list, show and update take --json and return trail URLs, replacing issues and pull requests; but there is no CI read beyond gates, the MCP server exposes only agent_help and entire_status, and a login token lasts 8 hours. source |
| GitHub MCP Server BB GitHub, Inc. | Toolset URLs and X-MCP-Toolsets load one domain, /readonly drops writes, fields and perPage trim reads and get_job_logs takes failed_only and tail_lines; but create_pull_request returns an error after the PR exists (#3756), unknown toolset names are ignored, and the default set costs 20,000 to 50,000 tokens. source |
| GitLab MCP Server B GitLab Inc. | X-Gitlab-Enabled-Mcp-Server-Toolsets selects core, merge_requests, work_items, repository or ci and an unknown name returns 400; get_merge_request, get_pipeline and get_job cover the asks; but there is no read-only mode, about 47 tools load by default and an administrator must allow MCP for the group first. source |
Doesn't do this job 17
Listings in the category that do something else, with the reason.
| Listing | Why |
|---|---|
| amCharts 5 MCP Server B amCharts | Documentation server for amCharts 5 only; no issue, pull request or CI tools. |
| Context7 BB Upstash | Documentation server; no issue, pull request or CI tools. |
| Git (MCP reference server) C Model Context Protocol, a Series of LF Projects, LLC | Local git only; no host, issue or CI tools. |
| GitMCP E Ido Salomon (GitMCP open-source project) | Documentation and code search for public repositories; no issue, pull request or CI tools. |
| graft C Vishisht Choudhary (individual) | Self-hosted source control with change requests; no issues, CI or hosted instance, and no MCP server. |
| Graphify BB Graphify Labs | list_prs and get_pr_impact read pull requests into the graph, but there are no issue, CI or write tools. |
| Jam MCP C Jam | Bug recordings; no issue, pull request or CI tools. |
| Microsoft Learn MCP Server D Microsoft Corporation | Documentation server; no issue, pull request or CI tools. |
| ModusToolbox AI Assistant D Infineon Technologies AG | Embedded development assistant; no host tools. |
| Momentic MCP server D Momentic | Bug-bash sessions; no issue, pull request or CI tools. |
| REA BB morluto | Reverse-engineering tools for binaries and apps; no host tools. |
| Ref D Ref Software, Inc | Documentation search; no host tools. |
| Salesforce DX MCP Server C Salesforce, Inc. | DevOps Center work item tools exist, but there are no code-host issue, pull request or CI read tools; see ticket-to-pr. |
| Sourcegraph MCP Server B Sourcegraph, Inc. | Code search and navigation; no issue, pull request or CI tools. |
| Superpowers B Prime Radiant (no legal form or registration found on its pages); the MIT LICENSE names Jesse Vincent | A skills library; no host tools. |
| TokenEconomizer B Microsoft Corporation (repository in the microsoft GitHub organisation with Microsoft's SECURITY.md); co-authors at UC Berkeley | A cost-control plugin; no host tools. |
| Void B Cloudflare, Inc. (VoidZero) | A deploy CLI; no host tools. |
What stops agents finishing
- full tool list of 45 to 92 tools loaded before the first call, 20,000 to 50,000 tokens
- OAuth browser flow with no token route in a headless client
- admin must enable MCP access for the group or tenant before the first connection
- write returns an error after the object was created, so the agent retries and duplicates
Around it
Before: work-trackers.read-ticket. After: code.ticket-to-pr, code.review-pr.
Where this comes from
Weight 19 of 100 in Code & developer platforms: 21 of 65 accounts describe reading or changing issues, PRs, CI runs or work items through GitHub, GitLab or Azure DevOps tools; the most common job in the GitHub MCP issue tracker and the HN MCP-in-production thread
The same as data: /api/v1/use-cases/code.host-ops.json, or the MCP tool get_use_case with id code.host-ops. 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.