> ## Documentation Index
> Fetch the complete documentation index at: https://docs.assert.dev/llms.txt
> Use this file to discover all available pages before exploring further.

# MCP

> Connect your coding assistant to Assert's clusters and review progress

Assert's **Model Context Protocol (MCP)** server gives coding assistants access to a
pull request's clusters and your review progress.

Server URL:

```text theme={null}
https://mcp.assert.dev/mcp
```

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

<Tabs>
  <Tab title="Claude Code">
    Add Assert as an HTTP server:

    ```sh theme={null}
    claude mcp add --transport http assert https://mcp.assert.dev/mcp
    ```

    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](https://code.claude.com/docs/en/mcp) for configuration
    scopes and client troubleshooting.
  </Tab>

  <Tab title="Codex">
    Add the server and sign in:

    ```sh theme={null}
    codex mcp add assert --url https://mcp.assert.dev/mcp
    codex mcp login assert
    ```

    Complete the browser sign-in and consent flow. Run `codex mcp list` to check
    the configuration, or use **`/mcp`** in Codex to see connected servers.

    See [Codex's MCP guide](https://developers.openai.com/codex/mcp) for shared CLI
    and IDE configuration and authentication options.
  </Tab>

  <Tab title="Other clients">
    Add a remote **Streamable HTTP** MCP server named **Assert** using the URL
    above. Choose the client's OAuth sign-in action and authorize your Assert
    account. Your client must support remote HTTP MCP and OAuth.

    After connecting, refresh its tools list and look for Assert's cluster tools.
  </Tab>
</Tabs>

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

| Tool | Description |
| :- | :- |
| `list_pull_request_clusters` | Lists a pull request's clusters, with links and your saved review progress. |
| `get_pull_request_cluster` | Returns one cluster, its files, and the smaller clusters within it. |
| `get_pull_request_cluster_diff` | Returns the code changes in a cluster. |

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](/integrations/github).


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.