$ sf plugins install @provartesting/provardx-cli

$ sf plugins update

$ sf plugins uninstall @provartesting/provardx-cli

{
  "mcpServers": {
    "provar": {
      "command": "npx",
      "args": ["-y", "@provartesting/provardx-cli", "mcp", "start", "--allowed-paths", "/path/to/your/provar/project"]
    }
  }
}

claude mcp add provar -s user -- npx -y @provartesting/provardx-cli mcp start --allowed-paths /path/to/your/provar/project

# 1. Install the plugin
sf plugins install @provartesting/provardx-cli

# 2. (Optional) Authenticate for full 170+ rule validation
sf provar auth login

{
  "mcpServers": {
    "provar": {
      "command": "sf",
      "args": ["provar", "mcp", "start", "--allowed-paths", "/path/to/your/provar/project"]
    }
  }
}

claude mcp add provar -s user -- sf provar mcp start --allowed-paths /path/to/your/provar/project

USAGE
  $ sf provar auth login [--url <value>]

FLAGS
  --url=<value>  Override the Quality Hub API base URL (for non-production environments).

DESCRIPTION
  Opens a browser to the Provar login page. After you authenticate, your API key is
  stored at ~/.provar/credentials.json and used automatically by the Provar MCP tools
  and CI/CD integrations. The key is valid for approximately 90 days.

  For CI/CD pipelines (GitHub Actions, Jenkins, etc.) where a browser cannot open:
  run sf provar auth login once on your local machine, copy the api_key value from
  ~/.provar/credentials.json, and store it as the PROVAR_API_KEY environment variable
  or secret in your pipeline. Rotate the secret every ~90 days when the key expires.

  Don't have an account? Request access at:
  https://aqqlrlhga7.execute-api.us-east-1.amazonaws.com/dev/auth/request-access

EXAMPLES
  Log in interactively:

    $ sf provar auth login

  Log in against a staging environment:

    $ sf provar auth login --url https://dev.api.example.com

USAGE
  $ sf provar auth rotate

DESCRIPTION
  Exchanges your current pv_k_ key for a new one atomically. The old key is
  invalidated immediately. The new key is written to ~/.provar/credentials.json.

  Use this to rotate your key on a regular schedule (~every 90 days) without
  going through the browser login flow. If your current key is already expired,
  run sf provar auth login instead.

EXAMPLES
  Rotate the stored API key:

    $ sf provar auth rotate

USAGE
  $ sf provar auth status

DESCRIPTION
  Reports whether an API key is configured, where it came from (environment variable
  or credentials file), and performs a live check against the Quality Hub API to
  confirm the key is still valid.

EXAMPLES
  Check auth status:

    $ sf provar auth status

USAGE
  $ sf provar auth clear

DESCRIPTION
  Deletes ~/.provar/credentials.json and revokes the key server-side. After clearing,
  the MCP tools fall back to local validation mode. Has no effect if no key is stored.

EXAMPLES
  Remove the stored key:

    $ sf provar auth clear

USAGE
  $ sf provar mcp start [-a <value>...]

FLAGS
  -a, --allowed-paths=<value>...  Allowed base directory paths for file operations.
                                  Defaults to the current working directory.
                                  Repeat the flag to allow multiple paths.

DESCRIPTION
  Launches a stateless MCP (Model Context Protocol) server that exposes Provar tools
  to AI assistants (Claude Desktop, Claude Code, Cursor) via stdio transport. All MCP
  JSON-RPC communication happens over stdout; all internal logging goes to stderr.

  Note: --json is not available on this command — stdout is reserved for MCP traffic.

TOOLS EXPOSED
  43 tools across: project inspection & org describe, Page Object and test-case
  authoring/validation, test-suite/plan validation, properties files, Quality Hub
  (test runs, defects, corpus examples), Provar Automation, ANT build, and NitroX
  components. See docs/mcp.md for the full catalogue with schemas and examples.

EXAMPLES
  Start MCP server (accepts stdio connections from Claude Desktop / Cursor):

    $ sf provar mcp start