Prisma MCP

Prisma MCP lets an AI coding agent drive Prisma workflows directly instead of guessing at CLI invocations, and it ships in two forms. The local server runs alongside a project and wraps the commands a developer uses during schema work: checking migration status, creating and applying a migration from the current schema, resetting the database when a branch diverges, and opening Prisma Studio to inspect rows. Since the agent is usually already editing the schema file, this closes the loop between changing a model and having the migration exist. The remote server targets Prisma Postgres, the hosted database, and covers provisioning rather than schema. Through it an agent can list projects and databases, create a database, mint and revoke connection strings, manage backups, trigger a recovery, and delete a database that is no longer needed. That makes per-branch or per-environment database creation something an agent can handle inside a larger task. The intended user is anyone building with Prisma ORM who wants an editor agent to handle the mechanical parts of database work. Two cautions apply. Migration and reset commands are destructive against whatever database the environment points at, so keep the agent aimed at development targets and review a migration before it runs against shared data. Connection strings issued by the remote server are live credentials, so treat creating and deleting them as an audited operation.