This article first appeared on hyrax.dev.
Hyrax now runs a Model Context Protocol server. The AI coding agents a team already uses, Claude Code, Cursor, and Copilot, can talk to Hyrax directly: query a repository's live findings, check which rules apply to a file before editing it, submit a fix job, and follow the resulting pull request, all without a browser tab.
The reason this matters is timing. Autonomous code review and fixing produces knowledge that changes by the hour: which findings are unresolved, which suggestions are pending, which architectural migrations are in flight. An agent editing code at 2 PM needs the 2 PM answer. Static exports go stale; the MCP server serves the live state (docs).
What an agent can ask
Read tools query the repository's live state and never change anything. An agent typically lists the workspace's repositories first, then addresses everything else by the owner, repo, and branch triple.
| Question | Tool |
|---|---|
| What findings and suggestions exist, filtered by kind, status, or priority? | List / search observations |
| Which conventions and skills apply to this file path? | Applicable rules |
| What are the repo's canonical patterns, served live rather than from a stale file? | Canonical pattern |
| Which unresolved findings touch this file? | Recent issues |
| What is the full body of finding HYRAX-N? | Explain an observation |
| Which architectural suggestions are pending? | Pending migrations |
| What will this workflow likely cost and how long will it run? | Cost forecast |
| Where is my job, and did the fix PR merge? | Job status, List fix PRs |
The canonical-pattern tool is worth a pause. Hyrax publishes each repo's patterns and conventions to the codebase as part of its context bundle, and agents read those files. The MCP version serves the same content live, so an agent never reasons from a pattern file that predates last week's audit.
The cost forecast is readable by any key, so an agent can quote the likely cost and duration band for a workflow before anything runs.
What an agent can do
Write tools run the real workflows without a round trip through the web app. An agent can submit an audit, spawn a fix job for a specific finding by its HYRAX-N ref, retry a failed job, or register a new repository. Cost-bearing writes draw on the workspace's spend controls exactly as the REST API does, so an agent operates inside the same budget the team already set.
Triage moves into the editor too. An agent can dismiss a finding as a false positive with a reason, acknowledge one as seen, mark one complete when it was resolved outside a Hyrax PR, or move a closed finding back to new. The routine, reversible actions that used to mean switching to the app now happen where the code is.
The loop this enables reads like one conversation. An agent about to edit a payment module asks which findings touch it and which conventions apply, makes its change with that context, then submits a fix job for a related finding and checks back on the PR status, all through the same protocol it already speaks.
The guardrails
Every tool, read and write, is gated by the API key's scopes, and a key's scopes are a hard ceiling even for account owners. A key minted for read-only queries cannot submit jobs. A submit-only key can quote a cost forecast but cannot read the repository list beyond its grant. Keys only narrow after mint, so widening access means minting a new key deliberately.
Key restrictions travel across transports. An IP allowlist set on a key applies to MCP calls exactly as it does to REST calls, refusing requests from outside the listed ranges. The endpoint is rate-limited per key at roughly 60 requests per minute, and per-key spending ceilings gate every call.
The most important guardrail is unchanged from every other Hyrax surface: fixes arrive as pull requests, and nothing auto-merges. An agent can submit the fix job, but a human reviews and merges the result. The MCP server changes where the conversation happens, not who holds the merge button.
Connecting
The server is mounted at /mcp/ over streamable HTTP and authenticates with the same hk_live_ API keys as the REST API, passed as a bearer token:
POST /mcp/ HTTP/1.1
Authorization: Bearer hk_live_...
Content-Type: application/json
API access ships on paid plans; a key-authenticated MCP request from a workspace without API access returns a 402. Setup details, the full tool list, and scope reference are in the MCP server docs.
Find. Fix. Ship. Close.
Hyrax reviews all code, not just AI-written code, finds issues across security, correctness, maintainability, performance, architecture, and operations, and submits verified fixes as pull requests a human merges. The MCP server puts that whole loop within reach of the agents already sitting in the editor, working from the same live findings the team sees.
Hyrax makes your code better. Ship clean code.
Top comments (0)