Coding agents

View as Markdown

Connect your coding agent to read Proofline review status through the Model Context Protocol (MCP).

Install the CLI#

Run this command in your terminal to install the latest release on macOS or Linux:

curl -fsSL https://proofline.sh/cli | sh

If the installer asks you to add ~/.local/bin to your PATH, follow its instructions before continuing.

Sign in#

Sign in and choose your organization on the approval page:

proofline login --scope reviews:read

Your account must belong to an active organization. The CLI stores your credential in the operating system keychain. You can revoke it from Personal tokens.

Connect an agent#

Run the command for your agent. The CLI previews the configuration and asks for approval before saving it. It preserves existing Proofline entries and keeps credentials out of the configuration file.

Codex#

proofline agent install codex

Configuration: ~/.codex/config.toml.

Cursor#

proofline agent install cursor

Configuration: ~/.cursor/mcp.json. This is Cursor’s global user file. See Cursor’s MCP documentation to manage its servers.

Gemini CLI#

proofline agent install gemini

Configuration: ~/.gemini/settings.json.

Kiro#

proofline agent install kiro

Configuration: ~/.kiro/settings/mcp.json.

Add --print to preview a configuration without saving it. If you use a custom CODEX_HOME, or the CLI refuses your configuration file, copy the preview into your user configuration manually. Keep agent configuration outside your repository.

The Claude Code plugin is not available.

Read reviews#

Restart your agent or reload its MCP servers. Ask it to read a review’s status with get_review_status and the review ID. Verify that the agent can call the tool after setup.

To read findings for your repository’s current commit, run:

proofline findings

Review local changes#

Sign in with permission to request reviews, then run the review from your repository:

proofline login --scope reviews:read --scope reviews:request
proofline review

An incomplete review retains its evidence gaps. Read the findings and missing evidence before deciding to deploy.

Automatic pull-request reviews require an assigned seat and follow your organization’s review settings. Ask an administrator to assign a seat if you need automatic reviews. Recorded review reads do not require a seat.