Prisma MCP connector for AI agents

CALL ANY TOOL

Each tool maps to a Prisma operation your agent can call against any connected Prisma Postgres instance.

prismamcp_create_prisma_postgres_backup

Create Prisma Postgres Backup

Create an automated backup for a Prisma Postgres database. Note: on-demand backup creation is not currently supported; backups are created automatically by the system.

Parameters

Name

Type

Required

Description

databaseId

string

Required

The unique identifier of the Prisma Postgres database. Get it from List Databases.

projectId

string

Required

The unique identifier of the Prisma project. Get it from List Databases.

prismamcp_create_prisma_postgres_connection_string

Create Prisma Postgres Connection String

prismamcp_create_prisma_postgres_database

Create Prisma Postgres Database

prismamcp_create_prisma_postgres_recovery

Create Prisma Postgres Recovery

prismamcp_delete_prisma_postgres_connection_string

Delete Prisma Postgres Connection String

prismamcp_delete_prisma_postgres_database

Delete Prisma Postgres Database

prismamcp_execute_prisma_postgres_schema_update

Update execute prisma postgres schema

prismamcp_execute_sql_query

Query execute sql

prismamcp_fetch_workspace_details

Fetch Workspace Details

prismamcp_introspect_database_schema

Introspect Database Schema

prismamcp_list_prisma_postgres_backups

List Prisma Postgres Backups

prismamcp_list_prisma_postgres_connection_strings

List Prisma Postgres Connection Strings

prismamcp_list_prisma_postgres_databases

List Prisma Postgres Databases

Build your Agent

Same per-user vault and scope enforcement regardless of which AI framework your agent runs on.

Try these prompts

Paste any prompt into your agent to start querying Prisma Postgres on behalf of the authenticated user.

Schema exploration

Copy the prompt

Copied

Show me the full schema for my production database.

Copy the prompt

Copied

List all tables and their row counts in my Prisma Postgres instance.

Copy the prompt

Copied

Which tables have foreign key relations to the users table?

Copy the prompt

Copied

What indexes exist on the orders table?

Data queries

Copy the prompt

Copied

Find all records in the events table from the past 7 days.

Copy the prompt

Copied

Show me the top 10 users by query count this month.

Copy the prompt

Copied

Count the number of rows in each table and sort by largest.

Migrations and maintenance

Copy the prompt

Copied

What migrations are pending on my staging database?

Copy the prompt

Copied

Apply all pending migrations to my dev database.

Copy the prompt

Copied

Show me the migration history for the past 30 days.

SEE HOW AUTH WORKS

The developer authorizes once. Every subsequent agent call resolves their vaulted API key with scope enforcement before touching the database.

1

Authorize

Your user connects

Prisma MCP

once. We tie it to their identity and the meetings they approved — no shared bot account, no org-wide access

Who:

user ‘A’

when:

Once per user

access:

Limited to user

2

Store

Their

Prisma MCP

token lives in a vault scoped to them. User A's meetings are never reachable by an agent acting for user B, even on the same connection

vault:

encrypted

scope:

per-user

tokens:

auto-refreshed

3

Resolve

When your agent calls a

Prisma MCP

tool, we fetch the right token server-side. It never touches your agent, never appears in the LLM context, never shows up in your logs

speed:

~40ms

check:

before every call

seen by:

nobody

4

Audit

Every

Prisma MCP

tool call is logged — who triggered it, which meeting was fetched, what came back. 90 days of history, tied to the user who authorized it

history:

90 days

export:

SIEM-ready

logged:

every call

Test other agents

See the same per-user auth pattern enforced across every other developer tools connector.

ENGINEERING

DevOps assistant agent

Triage GitHub incidents, open Linear tickets, and notify the on-call channel in Slack with context already attached.

ENGINEERING

Auto-release notes agent

Group merged GitHub PRs by feature, fix, or chore and publish release notes per tag. No manual changelog grooming.

GitHub

View agent

Why Scalekit

Secure your agent's access. Connectors ship in minutes

Most database agent setups wire a shared connection string into the agent and call it done.

01.

Shared tokens break per-user analytics

A shared database URL works in a demo. In production every query looks like a service account. Scalekit resolves the real developer credential so your audit log reflects who actually ran each query.

// shared DATABASE_URL
audit → service_account

// scalekit
audit → alice@acme.com ✓

02.

Authentication is not authorization

03.

Multi-tenancy is architectural

04.

Prisma MCP today. Others tomorrow.

“Our agents act across Salesforce, Gong, Google Drive, and more, on behalf of every customer. Scalekit behind the scenes meant we can keep adding tools without ever rebuilding how credentials or tool calling work.”

Venu Madhav Kattagoni

Head of Engineering / Von

FAQs

Frequently Asked Questions

Does every user need their own Prisma API key, or can we share one?

Every user needs their own credential. Scalekit vaults a key per user and resolves it at call time, so queries are attributed to the right developer and your audit log stays accurate. A shared key collapses all activity into one identity, which breaks both attribution and fine-grained access control.

How does Scalekit store Prisma API keys?

Keys are encrypted at rest with AES-256 and decrypted only at the moment a tool call is authorized. The plaintext credential is never written to logs, never passed through agent context, and is inaccessible outside the vault resolution path.

Can I limit which Prisma MCP tools a specific user or role can call?

Yes. Scalekit's listScopedTools API returns only the tools a given user is permitted to invoke. You pass that list to your agent at session start, so the agent cannot even attempt a tool outside the permitted scope for that user.

What happens if a user revokes their Prisma API key or I delete their vault entry?

Any subsequent tool call that tries to resolve that credential will fail with an authorization error before it reaches Prisma. The agent receives an explicit rejection rather than a stale or empty response, so your error handling can prompt the user to re-authorize.

Does Scalekit support Prisma Postgres connection strings as well as API keys?

Yes. Scalekit vaults both Prisma API keys and direct Prisma Postgres connection strings. Each is stored and resolved the same way, giving you consistent per-user isolation and audit coverage whether your agent connects through the Prisma Data Platform or a direct database URL.

Prisma MCP

Tools your database agent reaches for on Prisma MCP, scoped per user.