Back to inline
Review before the pull request exists
inline is an MCP server. Point your agent at it with a personal key and it can review your working tree, or post a plan for a human to sign off before it writes anything. Same engine, same guidelines, same repo memory as the bot on the pull request.
One connection,
two jobs
Ask for a review and the agent sends the uncommitted diff with the context inline needs; nothing is pushed. Ask for a plan review and it publishes wireframes, steps, contracts and open questions to a link your team can pin comments on.
$ claude mcp add inline --transport http \
https://inline.dev/api/mcp
Added MCP server “inline”.
> review my working tree before I open the PR
⏺ inline · review_changes
reading 14 changed files, 812 added lines
repo memory: acme/payments-api
2 high · 1 medium · 3 suppressed
charges.ts:118 idempotency key written after
the charge; concurrent retries double charge.
2 open questions4 steps7 files
Request
Key store
Stripe
insert key → charge → return
- Does the replay cache need the tenant id in the key?
- Should a lost race return 409 or the original charge?
- Unique index on (tenant_id, key), agreed
Included
Named keysper person and per machine, revocable, cost tracked
Layered contextthe agent sends what the review needs, in one call
Feedback queueopen to consumed, so a decision is acted on exactly once
Plan approvalsan agent waits for a human before it starts implementing
Put it on one repository
Connect GitHub, enable a repo, and the next pull request opened gets a review.