← Explore all mcp servers

DATABASE DEVELOPMENT / Prisma

Prisma MCP

Manage Prisma Postgres databases, connection strings, recovery and object-store resources from an authenticated client.

“Manage Prisma Postgres databases, Prisma Compute deployments, and Object Storage with the Prisma MCP server.”

01 / THE REASONING

Why this made the selection.

  • Combines database lifecycle, schema inspection, backups and recovery in the Prisma workspace.
  • The tool list distinguishes documentation lookup from SQL, schema and resource mutations.
  • Prisma’s page says the MCP server manages Prisma Postgres, Prisma Compute deployments, and Object Storage after the user signs into a workspace.
  • It warns that tools which change or delete resources can cause data loss or interrupt live traffic, and that the CLI’s destructive-command safeguards do not apply to MCP tool calls.

02 / THE REVIEW RECORD

What we actually inspected.

Source review has boundaries.
A clear record is more useful than a “safe” badge.

Material inspected

  • Current Prisma MCP guide, full tool list, workspace authentication and client setup examples.
  • https://www.prisma.io/docs/ai/tools/mcp-server
  • Round 2 reread of acquired publisher setup and permission evidence; see immutable wave review.

Our findings

  • Authentication selects a Prisma Console workspace.
  • The current tool list includes permanently deleting a bucket and its objects/keys, so read-only documentation access must not be generalized to the whole server.
  • The Prisma MCP server is documented for Prisma Postgres databases, Compute deployments, and Object Storage, after signing in and selecting a workspace.
  • Tools that change or delete resources can cause data loss or interrupt live traffic, and the user is told to review the target before approving the call.
  • The page says built-in safeguards against accidental destructive commands apply to Prisma CLI commands, not to MCP tool calls.
  • The guide includes Composer service discovery and environment-variable changes in addition to database queries and backups.

Not established by this review

  • Server launch, authenticated tool calls, and release-to-source parity were not tested.
  • The resource was not executed and its tools were not called.
  • The server was not called. A source review is not a runtime or security certification.

The review applies to the material and revision named here. A newer upstream release can change its behavior.

03 / PUT IT TO WORK

Connect a server deliberately.

Upstream setup instructions ↗

DOCUMENTED COMMAND

claude mcp add --transport http prisma https://mcp.prisma.io/mcp

Copying does not execute this command. It may retrieve a newer version than the reviewed source.

  1. For Claude Code, register the remote HTTP endpoint with the shown command; the JSON example uses the documented Cursor mcpServers format.
  2. Complete Prisma Console authentication and choose the intended workspace.
  3. Use the client’s approvals to review SQL, schema changes, recovery and deletion operations.

Before you start

  • Prisma Console workspace access.
  • A compatible remote MCP client.

Documented configuration example

Use the client and authentication context described in the setup guidance. Configuration formats vary between hosts.

{
  "mcpServers": {
    "Prisma": {
      "url": "https://mcp.prisma.io/mcp"
    }
  }
}

04 / FOLLOW THE EVIDENCE

The source trail.

Our notes are separate from the original resource.
Check upstream before adopting a new version.

  1. https://www.prisma.io/docs/ai/tools/mcp-server

    Supports: summary, upstreamDescription, whySelected, bestFor, limitations, install, access, compatibility, transports, review

Evidence & Ask