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 at you--my-notes.vibe-coded.ai with storage, auth, and an MCP server your AI can call.

What you need

  • A vibe-coded.ai account. Free is enough for this page.
  • A coding agent: Claude Code, Cursor, Codex CLI, or Gemini CLI.
  • jq, curl and unzip in your shell. See the CLI guide if any are missing.
  • Node.js 18 or newer, with npm, for vibe dev (brew install node on a Mac). The first vibe dev installs its local runtime with npm.

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 (or ~/bin, if that's the one on your PATH). If neither is on your PATH, the installer prints one command to paste that adds it to your shell profile and applies it right away. The installer and the skill are open source at github.com/vibe-coded-ai/vibe if you want to read them first.

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

Claude Code and Cursor find the skill there on their own. The installer also links it at ~/.agents/skills/, which Codex CLI, Gemini CLI, Amp and opencode read. Claude Desktop doesn't read skill folders — upload the skill zip under Customize › Skills instead. Details in the CLI guide.

Step 2: Log in

vibe login

It opens your browser. Sign in however you signed up — Google, GitHub, or email and password — check the code on the page matches the one in your terminal, and approve. The token lasts 30 days. If you'd rather use a password, vibe login your@email.com still works; it reads the password from the terminal so it never enters the conversation.

Step 3: Start from a template

For data your AI reads and writes, start from tools, a blank data vibe with notes your AI can add, list and update:

mkdir my-notes && cd my-notes
vibe init --template tools my-notes

That registers the vibe, writes .vibe-coded.json, and drops in a worker with its MCP tools already annotated. The template decides the storage: tools uses key-value storage, included on every plan; tools-sql is the same on SQL and needs Pro or Pro+. Closer starting points ship too: tracker (things with a status), log (timestamped events with tags) and journal (dated entries with notes). For a plain web page with no backend, use site. vibe templates lists them all.

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 worker and its storage, on the real runtime, reloading on save. It serves at http://127.0.0.1:8787:

vibe dev

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

Publishing needs a verified email address. If you signed up with email and password and haven't clicked the link we sent, open your account page and choose “Resend verification email” (Google and GitHub sign-ins are verified already). Your vibe is live at:

https://you--my-notes.vibe-coded.ai

New vibes are private: only you, signed in, and people you grant access can open it. See Sharing & Access to change that. To check a page without a browser, including on a private vibe, run vibe fetch /.

Check the live tools before you connect anything. vibe call runs one MCP tool on the live vibe as you, with no browser. Write one record with your write tool, then read it back with your list tool. On the untouched tools template those are:

vibe call add_note '{"text":"first note"}'
vibe call list_notes

After Step 4, use the names your agent gave the tools.

Step 6: Connect an AI client

A published vibe with @mcp-expose async functions makes those functions available through its MCP server. Static and frontend-only vibes have no tools. Point any client at it:

https://you--my-notes.vibe-coded.ai/mcp

In Claude Code, run this in the vibe's folder. It adds the vibe to Claude Code for all your projects, with no browser step:

vibe connect

The tools load in your next Claude Code session. In claude.ai and Claude Desktop, add the URL as a custom connector under Settings → Connectors and sign in once. Then give your AI a first prompt, like “log a bake of my country loaf: four stars, a little underproofed”, and open the vibe's page to see the record it wrote. See Connecting AI to Your Vibe for each client.

Next steps

← What is a Vibe? Anatomy of a Vibe →