ai-sdk-5-migration

This MCP server assists in migrating from AI SDK 4.x to 5.0 by providing three focused tools that help you plan and execute the migration. The create-checklist tool returns a curl command to download a comprehensive AI_SDK_5_MIGRATION.md checklist, which you can review and follow step-by-step. The search-guide tool scans the official AI SDK 5 migration guide for code-related changes—such as API updates, imports, streaming changes, and tool usage—with examples drawn from the guide. The search-data-guide tool looks into the data migration guide for database and persistence considerations, including converting stored messages, dual-write patterns, and schema changes. Together, these tools streamline the transition and ensure you cover both code and data migrations. To use them, run the prompt through Cursor with the ai-sdk-5-migration server enabled, and let the MCP server return targeted guidance and ready-to-execute snippets.

Once configured in Cursor, you can initiate a migration session by prompting the agent with a request like: "Please migrate this project to AI SDK 5 using the ai-sdk-5-migration mcp server. Start by creating a checklist." The server will first provide a checklist via the create-checklist tool, then refine changes by consulting the migration guide and data guide as needed. This workflow helps you systematically address API changes, import updates, and persistence adjustments while keeping a single, auditable migration path.

Prerequisites:

• Node.js (recommended LTS) installed on your machine
• Basic familiarity with npm/yarn/pnpm depending on your setup

1. Install dependencies (example using pnpm as per Local Development): pnpm install

2. Run the MCP server locally: pnpm run dev

3. If you need to switch to a hosted version, configure your MCP client (e.g., Cursor) to point to http://localhost:3000/api/mcp during development, or to the deployed URL in production as instructed by the hosting environment.

4. Verify server startup by checking the console output for a listening message (e.g., listening on port 3000) and by performing a basic request to the MCP endpoint to ensure responses are returned.

Note: If your project uses a different package manager, adapt the commands accordingly (for npm: npm install and npm run dev; for yarn: yarn install and yarn dev).

Tips and considerations:

• Ensure Cursor is configured to include the ai-sdk-5-migration MCP server in .cursor/mcp.json as shown in the Quick Start example.
• The three tools (create-checklist, search-guide, search-data-guide) are designed to be used in sequence during a migration session; use them to gather both high-level guidance and code-level changes.
• If you encounter API or import changes during migration, use search-guide to locate the exact sections in the official migration guide with examples.
• For data migrations, consult the data guide with search-data-guide to understand schema changes and persistence patterns before applying updates to your database.
• When running locally, you can toggle the server off/on in Cursor to test changes without affecting your production setup.
• Ensure environment variables (if any) required by your migration workflow are properly set in your hosting environment and in your local dev environment.