Install

Agent integrations

Cursor

Install Pax into Cursor with skills, rules, MCP server configuration, and troubleshooting.

1 min readUpdated

Install Pax into Cursor so the agent can init projects, install blocks, run recipes, and validate output locally.

What you will learn

  • Skills merge into Cursor rules with Pax markers
  • MCP server runs over stdio from your Pax clone
  • Rebuild CLI after every Pax pull
  • Uninstall removes only Pax-owned blocks

Install

  1. Run the installer

    pnpm paxfx install cursor
pnpm paxfx protocol install
pnpm paxfx integrations status

    From the Pax monorepo root. For external projects, use the same commands with PAXFX pointing at the built CLI.

  2. Configure MCP

    Add Pax to Cursor MCP settings (.cursor/mcp.json or Settings → MCP):

    {
  "mcpServers": {
    "pax": {
      "command": "node",
      "args": ["/absolute/path/to/pax/packages/cli/dist/bin.js", "mcp", "serve"],
      "cwd": "/absolute/path/to/your/project"
    }
  }
}

    Use your project directory as cwd, not the Pax clone, when the agent works inside your app.

  3. Rebuild and restart

    cd /absolute/path/to/pax && pnpm build

    Restart Cursor so it respawns the MCP server with the fresh CLI binary.

Verify

Ask Cursor to list MCP tools or run paxfx mcp tools from the terminal. You should see 23 tools including initialize_project, create_scene, and validate_document.

Troubleshooting

MCP shows disconnected

Confirm the CLI path exists after pnpm build. Check Cursor MCP logs for spawn errors. See Troubleshooting.

Tools list is empty

Update Cursor and ensure the MCP config JSON is valid. Restart the editor after config changes.

Agent ignores Pax skills

Run paxfx protocol parity and paxfx protocol install to refresh adapters. Confirm skills appear in integrations status.

MCPFull tool reference.UpgradeAfter pulling a new Pax version.UninstallRemove Cursor integration cleanly.

Was this page helpful?

Edit this page

Answers are not recorded or transmitted. Pax has no telemetry.