
This profile is part of our MCP server directory, within The MCP Guide. Profiles are checked against each vendor's own documentation. Need a server built? See MCP development.
The Prisma MCP server lets an AI app manage Prisma Postgres databases and existing Prisma Compute apps. It can create databases, run SQL, apply schema updates, restore backups and manage deployments. Prisma hosts it at https://mcp.prisma.io/mcp, and you sign in with your Prisma account.
Checked against: Prisma MCP tools reference on 28 October 2026. eSEOspace did not install or test this server.
Key Takeaways
- Prisma's tool reference lists 31 tools: 12 read-only and 19 that write or can destroy data.
execute_sql_querycan read, change or delete data, but it does not change the schema.- Prisma warns that tools that change or delete resources "can cause data loss or interrupt live traffic."
- The Prisma CLI's destructive-command guardrails do not apply to MCP tool calls.
- The old local server (
npx prisma mcp) was in Prisma ORM 6.6 to 7.x and is not in Prisma 8.
At a glance
| Item | Detail |
|---|---|
| Publisher | Prisma |
| Official? | Yes |
| Hosting | Remote URL (https://mcp.prisma.io/mcp) |
| Transport | Streamable HTTP |
| Sign-in | Prisma account sign-in; you select a workspace and approve access |
| Read or write | Read, write and destructive tools; no global read-only mode documented |
| Price | No separate MCP price listed |
| Source code | Closed; the old prisma/mcp repo is archived |
| Status | Not stated |
What it can do
Prisma's reference tags each tool R (read-only), W (write) or D (destructive). A summary:
Prisma Postgres databases
- Read:
fetch_workspace_details,list_prisma_postgres_databases,list_prisma_postgres_connection_strings,list_prisma_postgres_backups,introspect_database_schema. - Write:
create_prisma_postgres_database,create_prisma_postgres_connection_string,create_prisma_postgres_recovery,execute_prisma_postgres_schema_update. - Write or destructive:
execute_sql_query. - Destructive:
delete_prisma_postgres_database,delete_prisma_postgres_connection_string.
Object storage
list_object_store_buckets(read),create_object_store_bucketandcreate_object_store_bucket_key(write),delete_object_store_bucketanddelete_object_store_bucket_key(destructive).
Prisma Compute apps
- Read:
list_prisma_compute_apps,list_prisma_compute_builds,list_prisma_compute_deployments,get_prisma_compute_deployment_logs. - Write:
promote_prisma_compute_deployment,rollback_prisma_compute_app,start_prisma_compute_deployment,set_prisma_compute_env_var. - Destructive:
stop_prisma_compute_deployment(write or destructive),delete_prisma_compute_deployment,delete_prisma_compute_app,delete_prisma_compute_env_var.
Other
search_prisma_documentationanswers questions with cited links to Prisma's docs.get_prisma_composer_topologyshows saved connections between Composer services.
Prisma notes the server "does not build or upload code." The Compute tools only manage apps and deployments that already exist.
How to connect it
Prisma's MCP setup guide covers many clients. For Claude Code:
claude mcp add --transport http prisma https://mcp.prisma.io/mcp
For Gemini CLI:
gemini mcp add --transport http Prisma https://mcp.prisma.io/mcp --scope user
For clients that use an mcpServers block, such as Cursor and Claude Desktop:
{
"mcpServers": {
"Prisma": {
"url": "https://mcp.prisma.io/mcp"
}
}
}
VS Code uses a servers key instead of mcpServers. Codex installs it as a plugin with codex plugin marketplace add prisma/codex-plugin. The guide also covers Windsurf (now Devin Desktop), Warp, fx and ChatGPT. After you connect, sign in, pick a workspace and approve access. Prisma suggests testing with "List my Prisma databases."
Security notes
Prisma's main warning is plain: "Tools that change or delete resources can cause data loss or interrupt live traffic." It says to check the target workspace and resources before you approve any operation.
Three things stand out:
- No server-side read-only mode. The reference does not describe one. Your client's approval prompts are the main control. Keep them on for every W and D tool. Read MCP approval fatigue for why careful review matters.
- CLI guardrails do not apply. Prisma says its CLI's destructive-command guardrails cover CLI commands, "not MCP tool calls."
- Some clients auto-approve. Prisma notes that fx may allow some MCP calls without prompting, based on saved rules or automatic review. Check your client's settings.
Pick the workspace carefully at sign-in. If you can, connect the AI to a workspace without production databases. See excessive permissions and the MCP security hub.
Alternatives
- Neon MCP Server: hosted Postgres with read-only mode and a pinned Postgres role.
- Supabase MCP Server: Postgres with
read_onlyand project scoping. - PlanetScale MCP Server: separate read and write query tools.
More profiles are in the MCP server directory.
Next step
Because Prisma documents no read-only mode, decide who may approve write and destructive calls before connecting. Our MCP readiness audit can help you set that rule for your team.
Frequently asked questions
Is there still a local Prisma MCP server?
No, not in current Prisma. The archived repo says the local server (npx prisma mcp) was part of the Prisma ORM CLI from 6.6 to 7.x and is not in Prisma 8.
Can the Prisma MCP server delete data?
Yes. Prisma marks several tools as destructive, including delete_prisma_postgres_database and delete_prisma_compute_app. execute_sql_query can also delete data.
Can it deploy my app to Prisma Compute?
No. Prisma says the server does not build or upload code. It can start, promote, roll back, stop and delete existing deployments.
Does the Prisma MCP server have a read-only mode?
Prisma's tool reference does not describe a global read-only mode. The list and get tools are read-only, so rely on your client's approval prompts for the rest.











