Skip to main content
Assert’s Model Context Protocol (MCP) server gives coding assistants access to a pull request’s clusters and your review progress. Server URL:
Sign in with the same Assert account you use for reviews. The server uses that account’s repository access and review progress.

​
Connect your assistant

Add Assert as an HTTP server:
In Claude Code, run /mcp, select assert, and choose Authenticate. Complete the Assert sign-in and consent flow in your browser, then return to Claude Code. Use /mcp again to check the connection.See Claude Code’s MCP guide for configuration scopes and client troubleshooting.

​
Example: explore a pull request

Give your assistant a GitHub pull request URL and ask for an overview:
Use Assert to explain the main changes in this PR. Which clusters should I read first, and why? Give me links so I can follow along.
Then ask about a specific cluster:
Read the error-handling cluster. What happens when a request times out, and which tests cover that path?

​
Example: check your review progress

The server can read your saved review progress, so you can ask:
Which clusters have I not finished reviewing? Suggest an order and link each one.
Progress updates as you mark code reviewed in Assert. The MCP tools only read progress; they don’t mark code reviewed or submit feedback to GitHub.

​
Cluster tools

Cluster results include your review progress once you’ve marked code reviewed on that PR in Assert. For a large change, ask the assistant to work through smaller clusters. If Assert is still processing the pull request, the tools tell the assistant when to retry.

​
Troubleshooting

If authentication expires, repeat your client’s sign-in action. If a PR is inaccessible, confirm you can open it with the same Assert account and check its GitHub connection.