The backend your AI agent sets up for you
Empty folder in, live app out. Claude Code, Codex, or Cursor creates the Postgres database, login, and storage on Scribase by itself, then the keys land in your Vercel project automatically.
$9 per project per month. Unlimited projects. Or $299 per month for everything.
Connect your agent once
Sign up, create a token in the console, and add the Scribase MCP server. Nothing to install. Cursor, Codex, and Windsurf use the same URL.
Ask for the app
In an empty folder, tell the agent what to build. It creates the backend, the tables, and the login itself. No template, no starter repo, no dashboard.
Live on Vercel, keys already set
When the folder is linked to Vercel, one command puts the URL and keys into development, preview, and production. The deploy just works.
One line in your terminal
Create a token in the console under Account, Tokens, export it as SCRIBASE_ACCESS_TOKEN, then add the server. The token stays in your shell, never in the chat.
claude mcp add --transport http scribase https://api.scribase.com/mcp \
--header "Authorization: Bearer $SCRIBASE_ACCESS_TOKEN"Cursor, Codex, and Windsurf take the same URL and token in their MCP config. Setup for every editor.
Every tool declares the access it needs, and anything destructive waits for your confirmation. All MCP tools.
Say what you want. The agent does the backend.
No boilerplate to clone. The agent writes the app from zero and calls Scribase for everything behind it.
Build me a habit tracker with email login.
Use Scribase for the backend and deploy it to Vercel.| projects.create | creates Postgres, Auth, Storage, Realtime and Functions and waits until it is live |
| migrations.apply | creates the tables and row level security for your data |
| types.generate | writes TypeScript types from the live schema |
| keys.get | returns the project URL and public key for createClient() |
Env vars on Vercel, set for you
Scribase reads the folder's .vercel/project.json and writes every variable in one request, using VERCEL_TOKEN or the vercel CLI you are already signed in to. Rerun it after a key rotation and the values update in place.
vercel link --yes
scribase vercel env push <org> <project> production
Vercel: 9 environment variables set on prj_... for development,
preview and production (via the signed-in vercel CLI); the next
deploy uses them| NEXT_PUBLIC_SUPABASE_URL | project URL | all |
| NEXT_PUBLIC_SUPABASE_ANON_KEY | public key, row level security applies | all |
| NEXT_PUBLIC_SCRIBASE_URL / _ANON_KEY | the same, Scribase names | all |
| SCRIBASE_ORG / _PROJECT / _ENV | which backend this is | all |
| SUPABASE_SERVICE_ROLE_KEY | server-only, stored as sensitive | production, preview |
The service role key never gets a NEXT_PUBLIC_ name, so it cannot reach the browser.
Ten ideas, ten backends, no project limit
$9 per project per month, as many projects as you want. Or $299 per month for Unlimited. Sign-up takes one click and a $1 card check that is credited to your balance.