Integration

Prisma Postgres Management API integration

The Prisma Postgres Management API (the Prisma REST API) manages a Prisma Data Platform workspace. Create, list, rename and delete projects and their Prisma Postgres databases, list database backups and restore one into a database, read a database's operations and storage usage, create, rotate and delete connection strings, manage Prisma Storage buckets (S3-compatible object storage) and their access keys, and read workspaces, their subscription, the available regions and the identity of the current token. Routes the vendor marks Experimental or deprecated (apps, services, deployments, branches, builds, environment variables, source repositories, Alchemy state), project transfer, service-token and OAuth-integration management and agent approvals are not exposed. Authentication is a workspace service token, created in Prisma Console under Settings then Service Tokens, sent as a Bearer token in the Authorization header.

Connect Prisma Postgres Management API How integrations work

Ask it in chat

Say what should happen.
The workflow builds itself.

When this happens, do that in Prisma Postgres Management API.Built from the 36 Prisma Postgres Management API tools below, on the connection you add once.

What you can do with Prisma Postgres Management API

Each of these is one operation on one endpoint, available both as a workflow step and as a tool an AI agent can call on its own. Nothing bundles several operations into one action, so what a run did stays readable afterwards.

Most endpoints run on the free plan. A few, mainly the ones that publish on your behalf, need a paid plan.

Database, 8 operations

create_databaseCreate databasePOSTCreates a new database in the given project: empty, restored from a backup, or cloned from another database (source). logicalId cannot be combined with branchGitName; pass branchId instead.
create_project_databaseCreate project databasePOSTCreates a new database in the given project: empty, restored from a backup, or cloned from another database (source). Returns the database with its connections, connection strings included.
delete_databaseDelete databaseDELETEDeletes the database with the given ID.
get_databaseGet databaseGETReturns the database with the given ID.
list_databasesList databasesGETReturns all databases the token has access to. Optionally filter by project ID.
list_project_databasesList project databasesGETReturns databases for the given project.
restore_database_backupRestore database backupPOSTDestructive: immediately and irreversibly replaces all data in the target database with the contents of a backup; data written since that backup is lost. Connections and credentials are kept.
update_databaseUpdate databasePATCHRenames a database, moves it to another branch, or sets or clears its logicalId. logicalId cannot be combined with branchId or branchGitName in one request: move the database first, then set its logicalId.

Connection, 7 operations

create_connectionCreate connectionPOSTCreates a new named connection for the given database. The response carries its connection strings, credentials included, and is the only time they are returned.
create_database_connectionCreate database connectionPOSTCreates a new named connection for the given database. The response carries its connection strings, credentials included, and is the only time they are returned.
delete_connectionDelete connectionDELETEDeletes the connection with the given ID.
get_connectionGet connectionGETReturns the connection with the given ID, with its hosts and ports (no connection string).
list_connectionsList connectionsGETReturns all connections the token can access, optionally only those of one database, with their hosts and ports (no connection strings).
list_database_connectionsList database connectionsGETReturns the connections of the given database with their hosts and ports. Connection strings are not included: they are only returned when a connection is created or rotated.
rotate_connection_credentialsRotate connection credentialsPOSTGenerates new credentials for the connection with the given ID and returns its new connection strings. Revocation of the previous credentials is best-effort.

Bucket, 5 operations

create_bucketCreate bucketPOSTCreates a new object-store bucket in the specified project.
delete_bucketDelete bucketDELETEPermanently deletes the bucket with the given ID, all objects stored in it, and all its access keys. This action cannot be undone.
get_bucketGet bucketGETReturns the bucket with the given ID.
list_bucketsList bucketsGETReturns all object-store buckets the token has access to. Optionally filter by project ID.
update_bucketUpdate bucketPATCHUpdates the display name, logical id, or branch of the bucket with the given ID. The display name is a label only: the provider bucket name, the objects, and the access keys do not change.

Project, 5 operations

create_projectCreate projectPOSTCreates a project in the workspace and, unless createDatabase is false, a Prisma Postgres database with its connections, whose connection strings (credentials included) are returned only in this response.
delete_projectDelete projectDELETEDeletes the project with the given ID.
get_projectGet projectGETReturns the project with the given ID.
list_projectsList projectsGETReturns the list of projects the token has access to.
update_projectUpdate projectPATCHRenames the project with the given ID.

Bucket key, 3 operations

create_bucket_keyCreate bucket keyPOSTCreates an access key for the given bucket and returns its accessKeyId, its secretAccessKey (returned exactly once, never stored), the S3 endpoint and the bucket name.
delete_bucket_keyDelete bucket keyDELETERevokes and deletes the bucket access key with the given ID.
list_bucket_keysList bucket keysGETReturns the access keys of the given bucket: name, role and a hint of the key value. Secrets are never returned here.

Region, 2 operations

list_postgres_regionsList postgres regionsGETReturns the regions a Prisma Postgres database can be created in, with their availability.
list_regionsList regionsGETReturns every region across Prisma products with its product and availability; filter with product.

Workspace, 2 operations

get_workspaceGet workspaceGETReturns the workspace with the given ID.
list_workspacesList workspacesGETReturns the list of workspaces the current token can access.

Backup, 1 operation

list_database_backupsList database backupsGETReturns the backups of the given database (full, incremental or differential) with their status and size, plus the backup retention period in days. A backup ID feeds restore_database_backup.

Database usage, 1 operation

get_database_usageGet database usageGETReturns a database's usage for a period: operations and storage used, each with its unit. The period defaults to the current month to date.

Principal, 1 operation

get_current_principalGet current principalGETReturns who the current token acts for: the user (when any), the workspace, and the credential's type (service_token, oauth and so on), id and name.

Subscription, 1 operation

get_workspace_subscriptionGet workspace subscriptionGETReturns the workspace's subscription: plan name, whether usage is blocked, and the URL to upgrade the plan.

Use Prisma Postgres Management API from Claude Code, Cursor or Codex

Connect Prisma Postgres Management API in LiveContext, create an API key in Settings, then add the LiveContext MCP server to your client. Its Prisma Postgres Management API operations become tools the client can call, next to every other integration you connected.

Claude Code

claude mcp add --transport http livecontext https://livecontext.ai/mcp --header "X-API-Key: YOUR_API_KEY"

Codex (~/.codex/config.toml)

[mcp_servers.livecontext]
url = "https://livecontext.ai/mcp"

[mcp_servers.livecontext.http_headers]
"X-API-Key" = "YOUR_API_KEY"

Cursor, Claude Desktop and other JSON configs

{
  "mcpServers": {
    "livecontext": {
      "type": "http",
      "url": "https://livecontext.ai/mcp",
      "headers": {
        "X-API-Key": "YOUR_API_KEY"
      }
    }
  }
}

Set up the MCP server step by step

How to connect Prisma Postgres Management API

Create your workspace
Sign up free. Nothing to install.
Connect Prisma Postgres Management API once
Add your Prisma Postgres Management API connection in Settings. Every tool from this integration reuses it, and secrets are encrypted at rest and visible only to you.
Describe the job in chat
The workflow builds itself in front of you and picks the endpoints it needs. Drag the steps yourself on the canvas whenever you would rather be explicit.