Quickstart: Your First Vibe

Build it with the AI you already use. We host it and hand every AI you connect the keys.

Last updated: September 2026

Ten minutes, start to finish. You describe what you want to the coding agent you already use; it writes a small app; we run it on its own subdomain with storage, auth, and an MCP server your AI can call.

What you need

Step 1: Install the skill

One command. It puts the skill in ~/.claude/skills/vibe-coded-ai/ and links the vibe command into ~/.local/bin/:

curl -fsSL https://vibe-coded.ai/install.sh | sh
vibe help

Claude Code, Claude Desktop and Cursor find the skill there on their own. Codex CLI and Gemini CLI need a symlink into their own skills folder — the CLI guide has the two lines.

Step 2: Log in

vibe login your@email.com

Your password is read from the terminal and never enters the conversation. The token lasts 90 days.

Step 3: Start from a template

Three runnable templates ship with the skill: tracker (things with a status), log (dated entries), and journal (longer notes). Pick the closest one:

mkdir my-tracker && cd my-tracker
vibe init --template tracker my-tracker --storage kv --visibility private

That registers the vibe, writes .vibe-coded.json, and drops in a worker with its MCP tools already annotated. --storage kv is included on every plan; --storage sql needs BYOV or Pro.

Step 4: Make it yours

Now talk to your agent. It has the skill loaded, so it knows the platform's storage APIs, the @mcp-expose annotation, and the rules. Say what you want the app to track:

Turn this into a bread diary. Recipes with hydration and
timing, and bakes logged against a recipe with a rating
and notes. Expose list, get, log and update as MCP tools.

Run it locally while you iterate — the whole vibe, worker and storage included, on the real runtime with hot reload:

vibe dev

Keep reads free of schema setup. If your worker creates its tables on first use, do that from the write tools only. People you share the vibe with run its tools in read-only mode.

Step 5: Preview, then publish

vibe preview

Uploads your source, builds it in about a minute, and gives you a preview URL to check. When it looks right:

vibe publish

Your vibe is live at:

https://your-username--my-tracker.vibe-coded.ai

Step 6: Connect an AI client

Every published vibe is an MCP server. Point any client at it:

https://your-username--my-tracker.vibe-coded.ai/mcp

In claude.ai and Claude Desktop, add it as a custom connector under Settings → Connectors. In Claude Code: claude mcp add --transport http my-tracker <that URL>. You'll be asked to sign in once; after that the AI reads and writes your real records. See Connecting AI to Your Vibe for each client.

Prefer a hosted builder?

Pro includes the Vibe Builder: describe the app in the browser and a team of agents writes it for you, with credits to iterate. It's the same platform underneath — same storage, same MCP server. Open it from your account page once you're on Pro.

Next steps

← What is a Vibe? Anatomy of a Vibe →