# Moving from older Aluvia SDK and MCP instructions

Older Aluvia package listings describe SDK or MCP integrations. The current cloud-browser product is aluvia-cli. Use the current quickstart for new setup.

You may find earlier SDK, proxy-in-code or MCP instructions in search results, package archives and repository history. Listings such as `@aluvia/sdk`, `@aluvia/mcp`, `aluvia-sdk` and `aluvia-ts-sdk` describe an earlier integration model. They are not the setup path documented for the current Aluvia CLI.

This is migration guidance, not a drop-in API compatibility promise or an announcement that existing SDK applications will stop working. Keep version-specific information for an existing integration until its replacement has been tested.

## For a new cloud-browser task

Use [aluvia-cli on npm](https://www.npmjs.com/package/aluvia-cli) and the [current quickstart](/docs). Aluvia runs locally on the Chrome or Chromium host. First 10 MB free without an account, API key or payment; then $2/GB. Check [host requirements and evidence](/compatibility) before setup.

## For an existing SDK or MCP integration

Do not replace SDK calls or MCP configuration with a CLI command without checking how your application controls its browser and routes traffic. The CLI changes the configured browser's IP; it does not automatically replace an SDK API or every request in your application.

Preserve working configuration and version history. Test a separate browser task with the current quickstart, then plan the migration around the result. [Contact Aluvia](/contact) if you need help mapping an existing integration.

## Documentation and search results

Current instructions live at [aluvia.io/docs](/docs). Sampled legacy documentation addresses redirected there on September 8, 2026. Search engines and package descriptions can take longer to reflect a change. A redirect does not establish that every external listing has been updated.

---

Source: https://aluvia.io/legacy