rapibase

CLI

One command and your agent has a backend

Run it in your app's folder. It logs you in (or creates your account) in the browser, creates or picks a project, links the folder, writes your .env and connects your coding agent with skills and MCP. From then on, you ask your agent for the app.

npx rapibase@latest init

1 project free forever · no card · Pro $20/project/month

What init does

  1. Logs you in, in the browser. The terminal shows a code; you check that the browser shows the same one and approve. No account yet? You create it right there.
  2. Creates your project or lets you pick one. The free plan includes one project, no card.
  3. Links the folder in .rapibase/project.json. It holds no secrets, so it goes in the repo. In a monorepo, each app can have its own.
  4. Writes your .env with the project's keys. It never prints them.
  5. Connects your agent: it installs the Rapibase skills and the MCP for Claude Code, Cursor, OpenCode, Codex and Hermes, or for any agent that reads AGENTS.md.

Every step can be skipped (--no-env, --no-skill, --no-mcp) and running it again is safe.

Then, from the same terminal

rapibase deploy ./distPublishes your frontend on the project's domain. rapibase deploys activate rolls back.
rapibase statusWhat is running and where.
rapibase env pullWrites the keys to .env again, without printing them.
rapibase sql 'select …'Runs SQL on the project's Postgres.
rapibase tablesYour tables: rows, columns, types and keys.
rapibase api get … --anonChecks what a visitor sees (or a user, with --jwt): RLS applies.
rapibase functions deployUploads your TypeScript functions (endpoints, cron jobs and workers) and reloads them instantly.
rapibase logs --followThe project's logs, live.
rapibase skill updateBrings your agent's skills up to date. skill uninstall and mcp remove take them out.

rapibase <command> --help shows the options and examples of each one, in English, Spanish or Portuguese. To drop the npx, install it with npm i -g rapibase.

Made for agents

  • --json prints exactly one object: the data, or an error with a code and an exit status your agent can act on. Progress goes to stderr.
  • Without a terminal nothing waits for input: a missing choice fails and lists the options.
  • Inside an agent, login prints the link and the code and exits. Your agent runs it again after you approve.
  • Your agent never handles keys: sql, api, functions and rls go through Rapibase, and the project's secret key never leaves the server.
  • The Rapibase skills tell your agent to publish only when you ask for it.
  • If your agent already had an older Rapibase MCP for that project, init replaces it (it asks first), so it doesn't see the same tools twice.

Several projects

There is no global "current project": each command acts on the project linked to the nearest folder and names it before changing anything. --project <slug> or RAPIBASE_PROJECT override it.

In CI

Create a deploy token in the console (it publishes the site and the services, nothing else) and add this step to your workflow:

- run: npx rapibase@latest deploy ./dist
  env:
    RAPIBASE_DEPLOY_TOKEN: ${{ secrets.RAPIBASE_DEPLOY_TOKEN }}
    RAPIBASE_PROJECT: ${{ vars.RAPIBASE_PROJECT }}   # the numeric project id

For other steps (functions deploy, sql…) use a server token in RAPIBASE_TOKEN. rapibase --help lists every variable the CLI reads.

Open source

The CLI is MIT licensed and runs on Windows, macOS and Linux (x64 and arm64). Its npm packages are published from GitHub Actions with provenance. Code and the full reference: github.com/rapibase/cli.

Put your app online today

Create a free project, connect your agent and ask it for the app. It sets up the database, the login and the hosting. No card.