# Read and act on issues, pull requests and CI on a code host

> Read and act on issues, pull requests and CI on a code host: 0 companies fully do it, 4 with a limit, 13 carry the tag. Every listing in Code & developer platforms with the reason and a source.

- Canonical: https://www.anchorterminal.com/niches/code.host-ops/
- Markdown: https://www.anchorterminal.com/niches/code.host-ops/index.md (~1,500 tokens)
- Slim: https://www.anchorterminal.com/niches/code.host-ops/index.min.md (~280 tokens, same facts, less prose, for token-sensitive contexts)
- JSON: https://www.anchorterminal.com/niches/code.host-ops/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

No company's docs show a full fit yet. The listings below do the job with a limit, or not at all.

| Companies, full fit | With a limit | Carry the tag | Share of the category's work | First-hand accounts |
| --- | --- | --- | --- | --- |
| 0 | 4 | 13 | 19 | 21 |

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

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

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)**: 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.
- **Entire (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.
- **GitHub MCP Server (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.
- **GitLab MCP Server (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.

- not this job: amCharts 5 MCP Server (amCharts): Documentation server for amCharts 5 only; no issue, pull request or CI tools.
- not this job: Context7 (Upstash): Documentation server; no issue, pull request or CI tools.
- not this job: Git (MCP reference server) (Model Context Protocol, a Series of LF Projects, LLC): Local git only; no host, issue or CI tools.
- not this job: GitMCP (Ido Salomon (GitMCP open-source project)): Documentation and code search for public repositories; no issue, pull request or CI tools.
- not this job: graft (Vishisht Choudhary (individual)): Self-hosted source control with change requests; no issues, CI or hosted instance, and no MCP server.
- not this job: Graphify (Graphify Labs): list_prs and get_pr_impact read pull requests into the graph, but there are no issue, CI or write tools.
- not this job: Jam MCP (Jam): Bug recordings; no issue, pull request or CI tools.
- not this job: Microsoft Learn MCP Server (Microsoft Corporation): Documentation server; no issue, pull request or CI tools.
- not this job: ModusToolbox AI Assistant (Infineon Technologies AG): Embedded development assistant; no host tools.
- not this job: Momentic MCP server (Momentic): Bug-bash sessions; no issue, pull request or CI tools.
- not this job: REA (morluto): Reverse-engineering tools for binaries and apps; no host tools.
- not this job: Ref (Ref Software, Inc): Documentation search; no host tools.
- not this job: Salesforce DX MCP Server (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.
- not this job: Sourcegraph MCP Server (Sourcegraph, Inc.): Code search and navigation; no issue, pull request or CI tools.
- not this job: Superpowers (Prime Radiant (no legal form or registration found on its pages); the MIT LICENSE names Jesse Vincent): A skills library; no host tools.
- not this job: TokenEconomizer (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.
- not this job: Void (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

As data: https://www.anchorterminal.com/api/v1/use-cases/code.host-ops.json, or the MCP tool get_use_case with id code.host-ops. 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
