GitHub — how agent-ready is it?
The reference standard for agent-readiness: canonical MCP server, fine-grained self-serve tokens, and an API that covers essentially everything a human can do.
API surface — 9.5/10
REST + GraphQL cover repos, issues, PRs, Actions, code search — near-total parity with the UI.
MCP / agent protocol — 10/10
The official GitHub MCP Server replaced the community reference in late 2025 and is the canonical access path for Claude Code, Cursor and agent frameworks.
Docs quality — 9.5/10
docs.github.com/rest is versioned, exhaustive, with per-endpoint auth and rate-limit notes.
Auth friction — 9/10
Self-serve PATs with fine-grained repo/permission scoping; OAuth and GitHub Apps for multi-user agents.
Rate limits & pricing fairness — 8.5/10
5,000 req/h authenticated on the free tier — generous for agent workloads; secondary limits documented.
ToS stance on agents — 9/10
Automation is a first-class citizen (Actions, bots, Apps); GitHub builds agent products on its own API.
Machine-readable output — 9/10
JSON everywhere, webhooks, raw file access, Atom feeds on activity.
Stability — 9/10
Long deprecation windows, versioned REST API (X-GitHub-Api-Version) — breakage is rare and announced.
Sources
Point-in-time assessment — platforms change their API terms often (that volatility is itself scored under Stability).
- docs.github.com/rest — REST API reference — coverage, auth, rate limits (accessed 2026-07-12)
- github.com/github/github-mcp-server — Official GitHub MCP server (accessed 2026-07-12)
- github.com/modelcontextprotocol/servers — MCP servers directory — official vendor servers (accessed 2026-07-12)
- docs.github.com/en/rest/using-the-rest-api/rate-lim… — Rate limit documentation (accessed 2026-07-12)