Database Provisioning
Overview
Section titled “Overview”Provision a managed PostgreSQL database instantly — no infrastructure setup required. Each provisioned database is an isolated schema on AutoDB’s shared RDS instance, with a dedicated role and credentials.
Provisioned databases are automatically registered as connections and can be used with all AutoDB tools (introspection, migration analysis, text-to-SQL, agents, etc.).
Limits: 3 provisioned databases per user.
Provision a Database
Section titled “Provision a Database”curl -X POST https://api.autodb.app/api/v1/provision \ -H "Content-Type: application/json" \ -H "Authorization: Bearer YOUR_JWT" \ -d '{"name": "staging"}'| Field | Type | Description |
|---|---|---|
name | string | Display name (1-200 chars). |
Response (201)
Section titled “Response (201)”{ "success": true, "data": { "id": "d4e5f6a7-b8c9-0123-d456-e7f8a9b0c1d2", "connection_id": "a1b2c3d4-e5f6-7890-abcd-ef1234567890", "name": "staging", "schema_name": "tenant_a1b2c3d4e5f6_7890abcd", "status": "active", "created_at": "2026-04-11T..." }}The connection_id is immediately usable with all other endpoints — introspect, query, analyze migrations, etc.
List Provisioned Databases
Section titled “List Provisioned Databases”curl https://api.autodb.app/api/v1/provision \ -H "Authorization: Bearer YOUR_JWT"{ "success": true, "data": { "databases": [...], "count": 2, "limit": 3 }}Delete a Provisioned Database
Section titled “Delete a Provisioned Database”curl -X DELETE https://api.autodb.app/api/v1/provision/PROVISION_ID \ -H "Authorization: Bearer YOUR_JWT"This permanently drops the schema, all tables, all data, and the database role. The associated connection is deactivated. This cannot be undone.
MCP Tools
Section titled “MCP Tools”The MCP server exposes three provisioning tools:
provision_database(name)— create a new managed databaselist_provisioned_databases()— see your managed databases and remaining quotadelete_provisioned_database(provision_id)— drop a managed database
Architecture
Section titled “Architecture”Provisioned databases use schema-per-tenant isolation on a shared PostgreSQL instance:
- Each database gets a dedicated PostgreSQL schema and login role
- The role’s
search_pathis set to its schema — queries default to the tenant’s tables - Schemas are fully isolated — one tenant cannot access another’s schema
- The shared RDS instance is managed by AutoDB with automated backups
Limits
Section titled “Limits”| Limit | Value |
|---|---|
| Max provisioned databases per user | 3 |
| Storage | Shared (RDS auto-scaling 20-50 GB) |
| Connections | Standard PostgreSQL connection pooling |