Prisma MCP

What prisma/mcp MCP server does

The prisma/mcp MCP server gives an AI agent access to Prisma Postgres database workflows. It is available in two forms: a local MCP server intended for development on a local machine, and a remote MCP server intended for platforms that need to offer database management to their users.

The remote mode covers managed Prisma Postgres resources. An agent can list databases, create or delete databases, inspect schemas, execute SQL, create and remove connection strings, list backups, create backups, and restore a database into a new database from a backup.

The local mode focuses on Prisma CLI workflows in a developer project. It can check migration status, create and run a development migration, reset a database, authenticate with Prisma Console, create a Prisma Postgres database, open Prisma Studio, and report Prisma Console account status.

How it works

The prisma/mcp MCP server communicates with an MCP-compatible client using the standard server configuration format. The local process is started with the Prisma CLI command npx -y prisma mcp. The remote configuration starts an MCP remote client pointed at https://mcp.prisma.io/mcp.

For the remote service, authentication takes place through Prisma Console. The README describes connecting to the hosted endpoint and then authenticating in a Prisma Console popup. The local server exposes separate tools for checking authentication and logging in through Prisma Console.

The agent supplies arguments such as a database ID, environment ID, backup ID, SQL statement, migration name, database name, or region when the selected operation requires them. For example, a migration tool receives the migration name, while database creation receives a name and region.

Setup and configuration

Install and run the local server with:

npx -y prisma mcp

A local MCP client configuration uses npx as the command and -y, prisma, and mcp as its arguments. This configuration is shown for VS Code and Cursor in the project documentation. Cursor can make the server available globally or only within a project.

The remote service is configured with the hosted endpoint through an MCP remote client:

npx -y mcp-remote https://mcp.prisma.io/mcp

The remote endpoint can also be added to supported MCP clients using an HTTP-style server configuration. The README specifically documents setup guidance for VS Code and Cursor, as well as testing the endpoint in Cloudflare’s AI Playground.

Tools and capabilities

The prisma/mcp MCP server provides these remote database-management capabilities:

• List Prisma Postgres databases, backups, and connection strings.
• Create or delete databases and connection strings.
• Create backups and restore a new database from a backup.
• Execute SQL against a specified database.
• Introspect a database schema.

The local server provides these development capabilities:

• Check migration status.
• Create and apply a development migration.
• Reset a database with force enabled.
• Log in to Prisma Console and check account status.
• Create a Prisma Postgres database with a name and region.
• Open Prisma Studio.

Limitations and notes

The documented tool sets differ between local and remote modes, so selecting one depends on the workflow. The remote tools manage Prisma Postgres resources through the hosted Prisma service, while the local tools invoke Prisma CLI operations from the development environment.

Database deletion, resets, SQL execution, migrations, and recovery can change data or infrastructure. The README includes prompts for creating a backup before seeding data, but the server does not automatically make that decision for every operation.

The provided material does not specify a software license, environment variables, service pricing, or support for Claude Desktop, Windsurf, or Cline.