rapibase

2026-11-12 · 4 min read

From zero to published with your coding agent

npx rapibase@latest init

Run in your app's folder, that command gets everything ready to work with your coding agent: it logs you in or creates your account, creates a free project, writes .env and installs the Rapibase skills and MCP in Claude Code, Cursor, OpenCode, Codex, Hermes or any agent that reads AGENTS.md. Then you ask the agent for the app and publish it when you decide.

What you need

  • Node.js, to run npx.
  • Your coding agent.
  • A folder for the app: empty, or with the code you already have.

You don't need an account beforehand: you create it in the first step. The free plan includes one project and asks for no card.

1. Log in from the browser

Open a terminal in the app's folder and run the command. Your browser opens and the terminal shows a code. Check that the browser shows the same code, log in or sign up, and approve. You never type an email or a password in the terminal. If the browser doesn't open, the terminal gives you the link.

2. Create the project

init asks which project to use. The first option is a new one on the free plan: pick a name and that name becomes your address, my-app.rapibase.com. The project comes with its own Postgres database, user login, file storage, TypeScript functions and hosting. If you already used your free project, init offers the ones you have.

3. What ends up in your folder

init detects your agent (or asks which one you use) and leaves this:

  • .rapibase/project.json, which links the folder to the project. It has no secrets: you can commit it.
  • .env, with the project's URL and keys. init adds it to .gitignore and never prints the values.
  • The Rapibase skills, where your agent reads them. They teach it the database, login, functions, deploys and logs.
  • The Rapibase MCP, registered in your agent without any key: the agent logs in with OAuth the first time it uses it.

If the MCP is new, restart the agent so it loads it; init tells you how for yours. In Claude Code, claude --continue picks the conversation back up.

If you'd rather have your agent run it

You can also ask the agent to do it, in your own words:

Connect this folder to Rapibase with
npx rapibase@latest init --name my-app
and give me the link to approve.

From an agent, the CLI doesn't sit waiting: it prints the link and the code and exits with login_pending. You open the link, check the code, approve and tell the agent, which runs the same command again and carries on where it stopped. --name is the name of the free project it will create; to use one you already have, swap it for --project and that project's name. When it finishes, do what the CLI says to load the MCP (usually, restart the agent).

4. Ask for the app

With the folder ready, ask for what you want to build. For example:

Build a to-do app with Rapibase:
sign-up and login with email,
each user only sees their own tasks.
Test it locally. Do not publish anything yet.

The agent already knows how to use Rapibase: it creates the tables, turns on row level security so the database itself decides who sees what, and writes the code against the API. If the app needs server-side logic (sending an email, receiving a payment notification, calling another API), ask for a TypeScript function: it runs inside the same project. When the agent queries the database or the API through the CLI, the secret key never leaves the server.

Test it with two accounts: what one saves, the other must not see.

5. Publish when you decide

When you are happy, ask the agent "build it and publish it on Rapibase", or do it yourself:

npx rapibase@latest deploy ./dist

./dist is Vite's build folder; if you don't pass one, the CLI looks for your framework's. The app goes live at my-app.rapibase.com, on the same domain as the API, so there is no CORS. If you'll use the CLI often, install it with npm i -g rapibase and type just rapibase, as in the rest of this guide.

Each deploy is a release: rapibase deploys lists them and rapibase deploys activate goes back to an earlier one. The agent only publishes when you ask, because the skills tell it so; if it ever does it on its own, tell it not to.

Day to day

  • rapibase status: the project's URLs, plan and usage.
  • rapibase logs --follow: the app's logs, live.
  • rapibase sql "select count(*) from tasks": SQL straight against your Postgres.
  • rapibase env pull: writes .env again. On another computer, after cloning the repo, run rapibase login and then this.
  • rapibase open: opens the project's console.

The commands, the agent mode and CI usage are summed up on the CLI page. rapibase --help lists every command, and each one has its own --help with examples. The CLI is open source, at github.com/rapibase/cli.

Try it with your agent

Create a free project, connect your agent (Claude Code, Cursor, OpenCode or Claude.ai) and ask it for your app. No card.

Start free