Install

Agent integrations

Upgrade

Refresh Pax skills, MCP tools, and protocol adapters after pulling a new version.

1 min readUpdated

Upgrade Pax integrations when you pull a new release or switch branches in your Pax clone.

What you will learn

  • Rebuild the CLI before reconnecting MCP
  • Regenerate protocol adapters when the canonical hash changes
  • Doctor detects version drift between CLI and project manifest
  • No automatic telemetry or cloud sync

Upgrade workflow

  1. Update the Pax clone and rebuild

    git pull
pnpm install
pnpm build

  2. Refresh project metadata

    paxfx update project
paxfx update config
paxfx doctor

  3. Regenerate agent adapters

    paxfx protocol parity
paxfx protocol install
paxfx integrations status

Expected result

Doctor reports no version drift. MCP tools/list returns the expected tool count (23 at launch). Skills under skills/ match the release tag.

MCP after upgrade

Restart your editor so it respawns the MCP server with the rebuilt CLI. If tools fail, verify cwd in MCP config still points at your Pax clone and that pnpm build succeeded.

Compatibility matrix

ComponentUpgrade path
CLI (paxfx)Rebuild from source or npm update @pax-sh/cli when published
MCP toolsAutomatic on server restart after CLI rebuild
Protocol adapterspaxfx protocol generate && paxfx protocol install
Scene documentspaxfx migrate scene <file> when schema version bumps
Blocks registryNo action; install commands stay stable per asset id
Release notesWhat changed in each release.TroubleshootingMCP and doctor fixes.MigrationMove between editors or machines.

Was this page helpful?

Edit this page

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