Prisma MCP connector for AI agents

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

CALL ANY TOOL

19 tools for Prisma Postgres: list and create databases, introspect schemas, run SQL and schema updates, manage connection strings, backups, and recovery, and manage object-store buckets.

prismamcp_create_object_store_bucket

Create object store bucket

Create a new object-store bucket in the given project. On success, use the returned bucket id to generate access credentials.

Parameters

Name

Type

Required

Description

projectId

string

Required

The project ID to create the bucket in (e.g. proj_xxx).

branchId

string

Optional

Branch ID (e.g. br_xxx) to scope the bucket to. Defaults to the project default branch.

name

string

Optional

A display name for the bucket. Generated if omitted.

prismamcp_create_object_store_bucket_key

Create object store bucket key

prismamcp_create_prisma_postgres_backup

Create prisma postgres backup

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_object_store_bucket

Delete object store bucket

prismamcp_delete_object_store_bucket_key

Delete object store bucket key

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_object_store_buckets

List object store buckets

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

prismamcp_search_prisma_documentation

Search prisma documentation

Build your Agent

Same auth pattern across LangChain, OpenAI, Anthropic, and Google ADK.

import { ScalekitClient } from "@scalekit-sdk/node";
import { createReactAgent } from "@langchain/langgraph/prebuilt";

const sk = new ScalekitClient(env.SCALEKIT_ENV_URL, env.SCALEKIT_CLIENT_ID, env.SCALEKIT_CLIENT_SECRET);

// Prisma MCP tools scoped to this user
const { tools } = await sk.tools.listScopedTools("user_123", {
  filter: { connectionNames: ["prismamcp"], toolNames: [
    "prismamcp_list_prisma_postgres_databases",
    "prismamcp_introspect_database_schema",
    "prismamcp_execute_sql_query"] },
  pageSize: 100,
});

const agent = createReactAgent({ llm, tools });
await agent.invoke({ messages: [{ role: "user", content: "Show me the schema of my staging database" }] });

import OpenAI from "openai";
import { ScalekitClient } from "@scalekit-sdk/node";

const sk = new ScalekitClient(env.SCALEKIT_ENV_URL, env.SCALEKIT_CLIENT_ID, env.SCALEKIT_CLIENT_SECRET);
const openai = new OpenAI();

const { tools } = await sk.tools.listScopedTools("user_123", {
  filter: { connectionNames: ["prismamcp"] }, pageSize: 100,
});

const res = await openai.chat.completions.create({
  model: "gpt-5",
  messages: [{ role: "user", content: "Show me the schema of my staging database" }],
  tools,
});

// Execute the tool call with the user's vaulted Prisma token
await sk.tools.executeTool(res.choices[0].message.tool_calls[0], "user_123");

import Anthropic from "@anthropic-ai/sdk";
import { ScalekitClient } from "@scalekit-sdk/node";

const sk = new ScalekitClient(env.SCALEKIT_ENV_URL, env.SCALEKIT_CLIENT_ID, env.SCALEKIT_CLIENT_SECRET);
const anthropic = new Anthropic();

const { tools } = await sk.tools.listScopedTools("user_123", {
  filter: { connectionNames: ["prismamcp"] }, pageSize: 100,
});

const msg = await anthropic.messages.create({
  model: "claude-sonnet-5",
  max_tokens: 1024,
  messages: [{ role: "user", content: "Show me the schema of my staging database" }],
  tools,
});

// Tool call runs with the user's vaulted Prisma token
await sk.tools.executeTool(msg.content, "user_123");

import { Agent } from "@google/adk/agents";
import { ScalekitClient } from "@scalekit-sdk/node";

const sk = new ScalekitClient(env.SCALEKIT_ENV_URL, env.SCALEKIT_CLIENT_ID, env.SCALEKIT_CLIENT_SECRET);

const { tools } = await sk.tools.listScopedTools("user_123", {
  filter: { connectionNames: ["prismamcp"] }, pageSize: 100,
});

const agent = new Agent({
  name: "database_agent",
  model: "gemini-2.5-pro",
  instruction: "Prisma MCP tools scoped to this user",
  tools,
});

await agent.run("Show me the schema of my staging database");

Try these prompts

Copy any prompt into your agent. Each maps directly to a Prisma MCP tool. Click to copy, paste into your agent, done.

Schema and data

Copy the prompt

Copied

Show me the schema of my production database.

Copy the prompt

Copied

Count the rows in the orders table created in the last 7 days.

Copy the prompt

Copied

Add an index on orders.user_id in my dev database.

Databases and connections

Copy the prompt

Copied

List all Prisma Postgres databases in my workspace.

Copy the prompt

Copied

Create a new Prisma Postgres database in us-east-1.

Copy the prompt

Copied

Create a connection string for my staging database.

Backups and storage

Copy the prompt

Copied

List the available backups for my production database.

Copy the prompt

Copied

Restore last night's backup into a new database.

Copy the prompt

Copied

Create an object-store bucket for user uploads in this project.

SEE HOW AUTH WORKS

Each user signs in to Prisma once; Scalekit stores and refreshes their tokens. Credentials stay vaulted, every call is scope checked, and every action is logged.

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

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

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

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 across other database and developer tool connectors.

Engineering Teams

DevOps assistant agent

Polls GitHub for failing checks and stale PRs, opens Linear issues for the ones that need work, and posts a daily digest to Slack. It acts as the engineer, not a shared service account.

Engineering Teams

Engineering standup agent

Pulls commits from GitHub and GitLab, tracks issue movement in Jira, and posts a per-engineer standup brief to Slack. Each engineer's activity is read on their own delegated OAuth.

Engineering Teams

Auto release notes agent

Reads merged GitHub PRs, groups them into structured release notes, publishes the page to Notion, and announces the release in Slack. Every call runs on the engineer's own delegated OAuth.

GTM and RevOps Teams

Revenue forecast commentary

Pulls open pipeline from Salesforce and HubSpot, calculates coverage against quota, flags at-risk stages, posts commentary to Slack, and logs every snapshot to Google Sheets.

Why Scalekit

Secure your agent's access. Connectors ship in minutes

01.

Shared tokens break per-user analytics

A shared Prisma token looks fine in a demo. In production every query and schema change looks like one service account, and you cannot tell which user triggered it. Scalekit resolves the credential of the actual user who triggered the agent, never a shared bot.

// shared token
audit → bot_service_account

// scalekit
audit → user_abc ✓

02.

Authentication is not authorization

03.

Multi-tenancy is architectural

04.

Prisma today. Ten connectors 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 the agent access Prisma as the user or through a shared service account?

As the user. Each user signs in to Prisma once, and Scalekit stores and refreshes their tokens. Audit logs attribute every action to that user, not a shared service account.

Where is the Prisma OAuth token stored?

In Scalekit's managed AES-256 token vault, namespaced per tenant. Refresh is automatic. Revocation is a single dashboard action. Credentials never appear in prompts, logs, or LLM context.

Can I limit what the agent does in Prisma?

Yes. Filter by tool name in listScopedTools to expose only what you want, for example the 7 read-only tools without SQL execution or deletes. Scalekit also enforces scope checks before every API call.

What happens when a user revokes Prisma access?

The connection is invalidated on the next tool call. Subsequent requests for that user fail closed with a clear error. Other users in the tenant remain unaffected. The event is logged for audit.

Can the agent run SQL against my Prisma Postgres databases?

Yes, if you expose it. prismamcp_execute_sql_query runs SQL reads and writes, and prismamcp_execute_prisma_postgres_schema_update runs DDL schema changes. Both are marked destructive, along with the four delete tools. 7 of the 19 tools are read-only; leave the destructive ones out of toolNames to keep the agent read-only.