Bring Prisma database management and version-aware ORM and Composer guidance into Cursor.
Prisma Cursor Plugin connects Cursor to Prisma’s hosted MCP server for managing Prisma Postgres databases, existing Prisma Compute deployments, and Object Storage in a selected workspace. Its skill entry points direct the agent to official guidance for Prisma ORM and Composer development.
Cursor can select skills when their descriptions match your task; you can also invoke /prisma-orm or /prisma-composer in chat. These entry points instruct the agent to prefer guidance matching your installed package version, using a suitable project copy before looking to the official source.
When a feature needs schema changes, queries, or migrations, use /prisma-orm to direct Cursor to the relevant Prisma 8 guidance. For a new project, complete the Prisma 8 setup guide first: the underlying ORM skill needs an installed package and an emitted contract.
When writing, testing, or deploying a Prisma Composer app, use /prisma-composer to direct the agent to Composer’s core concepts and relevant references. Its instructions check the installed package version before choosing a local skill copy.
Ask Cursor to manage Prisma Postgres databases, existing Compute deployments, or Object Storage buckets and access keys through the hosted MCP server. Sign in with your Prisma account and select the workspace you intend to manage.
Local tool needed
Find version-matched guidance for writing, testing, and deploying Prisma Composer apps.
Find version-matched guidance for Prisma 8 setup, schemas, queries, migrations, and upgrades.
Manage Prisma Postgres, existing Compute deployments, and Object Storage in your selected workspace.
Open Customize in Cursor, find Prisma, and select Install. Choose project or user scope. This installs the whole plugin, including its skills and hosted MCP configuration.
Open Customize and check that Prisma shows one MCP server and two skills.
On first use of the hosted MCP server, sign in with your Prisma account and select a workspace. The connection does not use your project’s DATABASE_URL; CLI commands or your application may still need that variable.
Use this path to test a copy of the plugin repository. Cursor loads it only when local plugin imports are allowed. An installed Marketplace copy of Prisma takes precedence over a local copy with the same name.
On Enterprise, an administrator controls Allow Local Plugin Imports under Dashboard → Settings → Security & Identity → Marketplace and Plugins; it is off by default. See Cursor’s local plugin instructions.
Copy the contents of the Prisma Cursor Plugin repository into ~/.cursor/plugins/local/prisma, with .cursor-plugin/plugin.json inside that folder.
Restart Cursor or run Developer: Reload Window.
Open Customize and check that Prisma shows one MCP server and two skills.
On first use of the hosted MCP server, sign in with your Prisma account and select a workspace. The connection does not use your project’s DATABASE_URL; CLI commands or your application may still need that variable.
