Cursor

Connect Paragon to Cursor via MCP

Add Paragon as an MCP server in Cursor to get code review, testing, and analysis tools directly in your editor.

Cursor with Paragon

Prerequisites

Cursor editor installed
Paragon CLI installed

Get your API key

Go to app.paragon.run
Sign in or create an account
Navigate to Settings → API Keys
Copy your API key

Some tools like generate_tests, run_paragon, list_test_suites, and save_to_suite require an API key. Other tools work without one.

Setup

Open Cursor and go to Settings > MCP. Click + Add new MCP server.
Select Type: command and add the following configuration:

{
  "mcpServers": {
    "paragon": {
      "command": "paragon",
      "args": ["mcp-server"],
      "env": {
        "POLARITY_API_KEY": "your-api-key-here"
      }
    }
  }
}

Replace your-api-key-here with your API key from app.paragon.run. Alternatively, create a .cursor/mcp.json file in your project root with the same configuration.

After saving, you should see paragon listed in your MCP servers with a green status indicator.

Available tools

Once connected, Paragon exposes 12 tools to Cursor:

Code review

Tool	Description
`run_paragon`	Run a Paragon prompt — reads/writes files, runs shell commands, and performs complex coding tasks. Requires API key.
`list_reviewed_prs`	List pull requests with Paragon review comments in the current repository. Supports filtering by state (`open`, `closed`, `all`).
`get_review_comments`	Get parsed review findings from a PR, including severity, descriptions, file locations, and suggested fixes. Auto-detects PR from current branch if omitted.
`resolve_review_comment`	Reply to a review comment and optionally resolve the thread.

Testing

Tool	Description
`detect_test_framework`	Scan the repository and detect test frameworks in use. Returns framework details, run commands, file patterns, and confidence level.
`find_tests`	Discover existing test files using framework-aware file patterns. Returns file paths and count.
`run_tests`	Execute unit/integration tests using the detected or specified framework. Returns pass/fail status and full output.
`run_e2e_tests`	Run Playwright E2E tests locally. Installs browsers if needed, optionally starts a dev server, and captures results.
`generate_tests`	Generate unit, integration, or E2E tests using Paragon. Detects patterns, writes tests, verifies compilation, runs them, and fixes failures. Requires API key.

Test suite management

Tool	Description
`list_test_suites`	List your test repositories and suites from the Paragon cloud dashboard. Requires API key.
`save_to_suite`	Save locally generated test files to a Paragon cloud test suite. Requires API key.

Utility

Tool	Description
`check_setup`	Check if the MCP server is properly configured. Reports the status of the API key, Paragon binary, and GitHub CLI.

Usage

After setup, Cursor's agent mode can automatically use Paragon tools when relevant. You can also request them directly in chat:

Review the comments on my current PR and fix the issues

Generate unit tests for src/auth.ts

Run the test suite and show me what's failing

Find all Playwright tests and run them in headed mode

Claude Code FAQ