How to add Prisma MCP to Claude Desktop

Prisma's official MCP: run migrations, provision Prisma Postgres, execute SQL and manage backups from your agent. Paste the config into ~/Library/Application Support/Claude/claude_desktop_config.json and restart Claude Desktop.

Last updated June 14, 2026 · 43★ · stdio · oauth · official

Claude Desktop config for Prisma MCP

npx -y prisma mcp

{
  "mcpServers": {
    "prisma-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "prisma",
        "mcp"
      ]
    }
  }
}

Setup steps

1Open Claude Desktop → Settings → Developer → Edit Config (this opens ~/Library/Application Support/Claude/claude_desktop_config.json).
2Paste the Prisma MCP config below under the top-level "mcpServers" key.
3Fill in any placeholder secrets (API keys, paths) in the snippet.
4Save the file, then fully quit and reopen Claude Desktop.
5Open a chat and confirm Prisma MCP's tools appear under the 🔌 tools menu.

Before you start

Node.js with npx
A Prisma project (schema + datasource) for the local migrate tools
A Prisma Console account (console.prisma.io) for Prisma Postgres provisioning and all remote tools

What Prisma MCP can do in Claude Desktop

migrate-status

Local: check migration status via prisma migrate status.

migrate-dev

Local: create and run a migration via prisma migrate dev --name <name>.

migrate-reset

Local: reset the database via prisma migrate reset --force (destructive).

Prisma-Postgres-account-status

Local: check Prisma Console authentication status.

Create-Prisma-Postgres-Database

Local: create a new Prisma Postgres database with name and region.

Prisma-Login

Local: authenticate with the Prisma Console.

Prisma-Studio

Local: open Prisma Studio to browse data.

ListDatabasesTool

Remote: list Prisma Postgres databases in your workspace.

Security

migrate-reset runs prisma migrate reset --force, which wipes and recreates the target database — keep the local server pointed at development databases. The remote server acts on your Prisma Console account after OAuth (create/delete databases, run arbitrary SQL via ExecuteSqlQueryTool), so treat those tools as production-grade access.

Prisma MCP + Claude Desktop FAQ

Where is the Claude Desktop config file?

Claude Desktop reads MCP servers from ~/Library/Application Support/Claude/claude_desktop_config.json. Paste the Prisma MCP config there under the "mcpServers" key and restart the client.

Is Prisma MCP safe to use with Claude Desktop?

What is the difference between the local and remote Prisma MCP servers?

The local server (npx -y prisma mcp) wraps the Prisma CLI for the project on your machine: migrations, Studio, dev-database provisioning. The remote server (https://mcp.prisma.io/mcp) is hosted, OAuth-authenticated management of Prisma Postgres: databases, backups, connection strings, SQL execution and schema introspection.

Does it work with databases other than Prisma Postgres?

Partially. The local migrate tools run the Prisma CLI against whatever datasource your schema defines, so any Prisma-supported database works there. Database provisioning and every remote tool are Prisma-Postgres-only.

Is the Prisma MCP free and safe to use?

Both servers are free to use (Prisma Postgres itself is billed separately per Prisma's pricing). Safety-wise, know the two sharp edges: migrate-reset force-wipes the target database, and ExecuteSqlQueryTool runs arbitrary SQL on the database you point it at — keep agents on dev databases and backups enabled.

View repo Full Prisma MCP page