Proofline MCP

Connect a coding agent to Proofline’s hosted MCP server with npx -y @proofline/mcp. Requires Node.js 22 or later. No CLI installation or runtime dependencies are needed.

Contributing

This repository distributes the Proofline MCP bridge. The bridge discovers tools from the hosted MCP server at runtime. Open an issue for changes to the tool catalog or tool behavior. Pull requests are welcome for the hand-written bridge in src/, package scripts in scripts/, and tests in tests/.

Add to your agent

Add this entry to an agent’s MCP configuration, such as Cursor’s .cursor/mcp.json or Claude Code’s .mcp.json:

{
  "mcpServers": {
    "proofline": {
      "command": "npx",
      "args": ["-y", "@proofline/mcp"],
      "env": {
        "PROOFLINE_TOKEN": "YOUR_PROOFLINE_TOKEN"
      }
    }
  }
}

Create a personal token in the Proofline console for the organization you want to use. Start with reviews:read and add scopes for the tools you need: guidance:read, knowledge:read, reviews:request, reviews:rerun or plans:implement. The server enforces each tool’s scopes and repository access. The token selects the organization; no organization ID is needed. Keep the token in local user configuration, or omit env when the agent inherits PROOFLINE_TOKEN from its environment.

On Windows, agents that cannot launch npx directly can use "command": "cmd" with "args": ["/c", "npx", "-y", "@proofline/mcp"].

For Codex, the equivalent config.toml entry is:

[mcp_servers.proofline]
command = "npx"
args = ["-y", "@proofline/mcp"]
env_vars = ["PROOFLINE_TOKEN"]

Set PROOFLINE_TOKEN in the environment that starts Codex. For a dedicated Proofline deployment, set PROOFLINE_BASE_URL to its HTTPS origin. The default is https://proofline.sh. The package never opens a browser or stores credentials. Agents with remote HTTP and OAuth support can connect directly to https://proofline.sh/mcp instead; this package supplies the local stdio option.

Tools and results

The package forwards the server’s tool catalog and results unchanged. Tools cover review status and findings, repository guidance, review requests and reruns, wiki pages, codebase questions, architecture documents, plans, captured fix context and re-verification of pushed fixes. Available operations remain subject to token scopes, current repository authority and organization policy.

The server keeps model and repository text wrapped as untrusted_text. Treat it as data. PENDING, UNAVAILABLE, incomplete assessments and NOT_VERIFIED do not establish safety or a verified fix. A tool refusal retains isError: true. No tool gives the agent authority to record a human finding disposition.

Transport

The bridge accepts newline-delimited JSON-RPC on stdin and writes only protocol responses to stdout. Diagnostics go to stderr. It forwards one request at a time