The backup and restore pair is what lifts it above a query tool: an agent can take a backup before a migration and restore into a fresh database when it goes wrong, without anyone opening a console.
Prisma's MCP offering, in two shapes: a local server for a developer working on their own machine, and a remote server for platforms that want to hand database management to their own users. The tools below are the remote server's, covering Prisma Postgres databases, connection strings, backups and queries.
- Prisma Postgres databases in your workspace listed, and one deleted by id
- A connection string created for a database, listed, or deleted
- A managed backup created, and the available backups listed
- A database restored from a backup into a new database
- SQL executed against a Prisma Postgres database
- A database's schema introspected
The remote server runs through mcp-remote against Prisma's hosted endpoint, and follows the standard JSON MCP client configuration. Choose the local server instead if you are working against a database on your own machine.
One command — npx -y mcp-remote https://mcp.prisma.io/mcp