Prisma ORM 6.6.0: ESM Support, D1 Migrations & MCP Server

Prisma ORM v6.6.0 is out

Since publishing our ORM manifesto, we've been shipping meaningful improvements to Prisma ORM at a steady pace. In v6.6.0, we are bringing long-awaited features like ESM support and an initial version of pushing schemas changes to D1 and Turso databases to life.

ESM support with more flexible prisma-client generator (Early Access)

We are excited to introduce a new prisma-client generator that's more flexible, comes with ESM support and removes any magic behaviours that can cause friction with the current prisma-client-js generator.

Here are the main differences:

• Requires an output path; no “magic” generation into node_modules any more
• Supports ESM and CommonJS via the moduleFormat field
• Outputs plain TypeScript that's bundled just like the rest of your application code; this gives you more control and flexibility about your application bundling

If you've had problems with Prisma ORM in your project setup before (e.g. monorepos, Next.js, Vite, ...), we think that this new generator will greatly improve your workflow — try it out and let us know what you think!

Here's how you can use the new prisma-client generator in your Prisma schema:

The generator also has more fields like runtime, generatedFileExtension and importFileExtension that help you adapt the generated Prisma Client code to your specific project needs.

In your application, you can then import the PrismaClient constructor (and anything else) from the generated folder:

As of now, we recommend keeping the generated './generated/prisma' folder out of version control by adding it to .gitignore because the compiled query engine binary may cause compatibility issues when running the app on another machine (with a different OS):

We see the prisma-client generator as the more modern version compared to prisma-client-js and will make it the default generator with the next major version increment in Prisma 7. Here are some more exciting features we're planning to add:

• splitting the generated generated Prisma Client file to avoid slowing down code editors due to long generated files
• no more need for the Accelerate extension when using Prisma Postgres

MCP server to manage Prisma Postgres via LLMs (Preview)

Prisma Postgres is the first serverless database without cold starts. Designed for optimal efficiency and high performance, it's the perfect database to be used alongside AI tools like Cursor, Windsurf, Lovable or co.dev. In this release, we're adding a command to start a Prisma MCP server that you can integrate in your favorite AI development environment.

Thanks to that MCP server, you can now:

• tell your AI agent to create new DB instances
• design your data model
• chat through a database migration

… and much more.

To get started, add this snippet to the MCP configuration of your favorite AI tool:

Cloudflare D1 & Turso/LibSQL migrations (Early Access)

Cloudflare D1 and Turso are popular database providers that are both based on SQLite. While you can query them with Prisma ORM using the respective driver adapter, previous versions of Prisma ORM weren't able to make schema changes against these databases.

With today's release, we're sharing the first Early Access version of native migration support for D1 and Turso and these commands:

• prisma db push: Updates the schema of the remote database based on your Prisma schema
• prisma db pull: Introspects the schema of the remote database and updates your local Prisma schema
• prisma migrate diff: Outputs the difference between the schema of the remote database and your local Prisma schema

Note: Support for prisma migrate dev and prisma migrate deploy is underway and will come very soon!

To use these commands, you need to connect the Prisma CLI to your D1 or Turso instance by using the driver adapter in your prisma.config.ts file. Here is an example for D1:

With that setup, you can now execute schema changes against your D1 instance by running:

You can learn more details in the docs:

• Cloudflare D1
• Turso / LibSQL

New --prompt option on prisma init

You can now pass a --prompt option to the prisma init command to have it scaffold a Prisma schema for you and deploy it to a fresh Prisma Postgres instance:

For everyone, following social media trends, we also created an alias called --vibe for you 😎

The future of Prisma ORM is exciting

This is just the beginning, we have a lot more exciting things coming to Prisma ORM in the next weeks and months — check out our 3-months roadmap to get a glimpse of what's next or catch up on the most recent developments in our changelog (such as the performance improvements gained from our move from Rust to TypeScript).

Let us know on X and our Discord what you think of this release — and follow us to stay in the loop with all the exciting things coming your way!