PrismaSAFE
MCP server for managing Prisma Postgres.
Overview
From the repository's own README, as read at the audited commit. Badges and raw HTML are left out.
Overview
The Model-Context-Protocol (MCP) gives LLMs a way to call APIs and thus access external systems in a well-defined manner.
Prisma's provides two MCP servers: a local and a remote one. See below for specific information on each.
If you're a developer working on a local machine and want your AI agent to help with your database workflows, use the local MCP server.
If you're building an "AI platform" and want to give the ability to manage database to your users, use the remote MCP server.
Remote MCP server
You can start the remote MCP server as follows:
npx -y mcp-remote https://mcp.prisma.io/mcp
Tools
Tools represent the capabilities of an MCP server. Here's the list of tools exposed by the remote MCP server:
CreateBackupTool: Create a new managed Prisma Postgres Backup.CreateConnectionStringTool: Create a new Connection String for a Prisma Postgres database with the given id.CreateRecoveryTool: Restore a Prisma Postgres Database to a new database with the given Backup id.DeleteConnectionStringTool: Delete a Connection String with the given connection string id.DeleteDatabaseTool: Delete a Prisma Postgres database with the given id.ListBackupsTool: Fetch a list of available Prisma Postgres Backups for the given database id and environment id.ListConnectionStringsTool: Fetch a list of available Prisma Postgres Database Connection Strings for the given database id and environment id.ListDatabasesTool: Fetch a list of available Prisma Postgres Databases for user's workspace.ExecuteSqlQueryTool: Execute a SQL query on a Prisma Postgres database with the given id.IntrospectSchemaTool: Introspect the schema of a Prisma Postgres database with the given id.
Once you're connected to the remote MCP server, you can also always prompt your AI agent to "List the Prisma tools" to ge
6a7cd98647a8OBSERVED · 2026-10-08Connect
Built from this server's own package name, version and transport as found in its source — not copied from anyone's documentation, so it cannot drift against a page we do not control.
claude mcp add prisma-mcp-dxt -- npx -y [email protected]
{
"mcpServers": {
"prisma-mcp-dxt": {
"command": "npx",
"args": [
"-y",
"[email protected]"
]
}
}
}Trust audit
SAFEgrade B · trust 87/100 Nothing in the source contradicts what it says it does. Grade A is reserved for packages that have also passed the behavioural sandbox.
| Layer | What it checks | Result |
|---|---|---|
| L0 | Provenance & inventory | PASS |
| L1 | Static analysis of the code | PASS |
| L2 | Instruction surface (what it tells the agent) | PASS |
| L3 | Class-specific surface | WARN |
| L4 | Behavioural (sandbox) | SKIPPED |
What the source does
- Filesystem
- none-observed
- Network
- none-observed
- Shell
- none-observed
- Dependencies
- pinned
- Secrets in source
- none-found
Findings (2)
sse,streamable-http
Gates applied: no_behavioural_pass.
6a7cd98647a8full audit observations/trust-audit/mcp-server/prisma__prisma.json · Report an issue / request a re-scanAudit history
Every audit this server has had. A grade with a past is a grade somebody is still checking.
| Date | Source | Verdict | Grade | Score | Change |
|---|---|---|---|---|---|
| 2026-10-08 | 6a7cd98647a8 | SAFE | B | 87 | first audit |
Questions
What is the Prisma MCP server?
MCP server for managing Prisma Postgres.
Is Prisma safe to connect to an agent?
The audit found nothing in the source that contradicts what it says it does, and graded it B (87/100). Grade A is held back for packages that have also passed a sandboxed behavioural run, which is why a clean server reads B.
What credentials does Prisma need?
No credential environment variables were found in its source, so it appears to need none.
How does Prisma run?
It speaks sse and streamable-http, so it runs as a service you connect to over the network. It is published on npm as prisma-mcp-dxt at 0.1.0.
How current is this page?
The grade is for one exact copy of the source (6a7cd98647a8), read on 2026-10-08. The repository is watched and re-audited when it changes.