What an agent can do in Prisma
Manage Prisma Postgres: run SQL, restore backups, manage Object Storage buckets and Compute deployments with their logs and environment variables, and search the Prisma docs.
Jobs on Rush that use Prisma
No published job uses Prisma yet. The use cases show the kinds of work a run does.
Code changes on a Prisma codebase
These change the code of an app built on Prisma. They run on your repository in a Project and need no Prisma connection.
- Add Account Deletion to a Next.js and Prisma App
- Add an Audit Log to a Prisma Project
- Add Connection Pooling Limits to a Prisma App on Serverless
- Add Cursor Pagination to a Prisma API
- Add Database Indexes to a Prisma Schema
- Add Full-Text Search to a Prisma App
- Add a Prisma Migration Drift Check to CI
- Add Optimistic Locking to Prisma Models
- Add Pagination to a Prisma Query
- Add Read Replicas to a Prisma App
- Add a Seed Script to a Prisma Project
- Add Slow Query Logging to a Prisma App
- Add Soft Delete to a Prisma Schema
- Run Prisma Tests Against Their Own Database, Not the Dev One
- Add Transactions to a Prisma App
- Fix updatedAt Columns That Never Update in a Prisma Schema
- Find Slow Postgres Queries in a Prisma App
- Upgrade a Project to Prisma 7
- Review Prisma Migrations in Every Pull Request
How Prisma connects
Prisma is a remote MCP server, published by Prisma, at https://mcp.prisma.io/mcp. Connecting it signs in through the MCP OAuth flow on Prisma's side.
From Prisma: Prisma's MCP documentation.
Connect it once in the console under Settings → Connections, or from your server with POST /me/connections. The sign-in finishes in a browser signed in to the console as the same person, and a link not finished within 10 minutes expires.
After that, a run that names prisma in connections, or runs a saved agent that names it, gets it; your connections reach no run that does not name them.
POST https://api.phoenix.so/me/connections
{
"type": "mcp",
"name": "Prisma",
"url": "https://mcp.prisma.io/mcp"
}Whose Prisma account the agent uses
Your Prisma connection is personal: it belongs to the person who signed in. A run started in the console uses that person's Prisma, and a run started with an API key uses the Prisma of the member who created the key.
To act for your own app's users, make each user an agent from your template and show them, signed in to your app, the sign-in link POST /o/{org}/agents/{agent}/connections returns. They sign in to their own Prisma, and that agent's runs use their account and nothing else: never yours, never another user's.
More Database integrations
Frequently asked questions
How do I connect Prisma to Rush?
Open Settings → Connections in the console and connect Prisma, or send POST /me/connections with {"type":"mcp","name":"Prisma","url":"https://mcp.prisma.io/mcp"} and open the authorize_url it returns while signed in to the console. The connection reads pending until the sign-in finishes, then connected.
Does every run get my Prisma account?
No. A run gets your Prisma connection only when it names it in connections ("connections": ["prisma"]), or runs a saved agent that names it. A saved agent names its connections once, and every run of it gets them.
What can an agent do in Prisma?
Manage Prisma Postgres: run SQL, restore backups, manage Object Storage buckets and Compute deployments with their logs and environment variables, and search the Prisma docs. No published job uses it yet.
Can my app's users connect their own Prisma?
Yes. Make each user an agent from your template, and they sign in to their own Prisma through the link POST /o/{org}/agents/{agent}/connections returns. That agent's runs use their account alone.
Keep reading
- AI agents for engineering teams: every job and app for them
- How connections work: sign in once, then every run that names a connection gets it
- Start your first run from the developer API quickstart
- Pricing: one price per member, hours shared by the team
- How Rush compares with other cloud agents
- Every app and MCP server Rush connects to