Build from Claude

What it is

vibe-coded.ai has its own MCP server at https://vibe-coded.ai/mcp. Connect it to Claude and the whole vibe lifecycle becomes tools Claude can call: create a vibe, push its source, build a preview, check it, publish it, and hand you the vibe's own MCP URL. It is the same platform API the CLI wraps, reached from a chat instead of a terminal. Each vibe still gets its own MCP server once it is built; this one manages the vibes on your account.

Who can use it

A signed-in vibe-coded.ai account, on any plan. The CLI path works with the same account if you prefer local files.

Connect

claude.ai and Claude Desktop

1. Open Settings → Connectors and click Add custom connector.
2. Give it a name and paste the URL:

https://vibe-coded.ai/mcp

3. Your browser opens a vibe-coded.ai approval page. Sign in and approve. The grant covers every vibe on your account and appears under Connected AI clients on your account page, where you can revoke it.

Claude Code

Add the server once, for all your projects:

claude mcp add --scope user --transport http vibe-coded https://vibe-coded.ai/mcp

Or declare it in a project's .mcp.json:

{
  "mcpServers": {
    "vibe-coded": {
      "type": "http",
      "url": "https://vibe-coded.ai/mcp"
    }
  }
}

claude mcp list shows it as Needs authentication until you run /mcp inside a Claude Code session and sign in.

The first prompt

Describe the app and ask Claude to start with the server's getting_started tool. That tool explains what a vibe is made of, which template fits, and the order of calls, so Claude does not have to guess:

Make a new vibe on vibe-coded.ai: a bread diary with recipes and
bakes I can log from Claude. Call getting_started first, then
create it, push the source and give me the preview link. Don't
publish until I say so.

Claude creates the vibe, writes a worker with its tools annotated, pushes the files and waits for the preview build. It can then write a record through one of the new tools and read it back to prove the build works, and gives you the preview address. New vibes are private: only you, signed in, can open the preview. When it looks right, say “publish”; publishing is a separate step the server never takes on its own. Afterwards Claude hands you the vibe's own /mcp URL and the connector steps from Connecting AI to Your Vibe.

What the tools let Claude do

Tool	What it does
getting_started	How a vibe is put together, which template to start from, and the order of calls. Claude reads this first.
list_vibes	Every vibe on the account with its URLs, plus the plan.
usage	What the plan allows and what is used, with the billing page when a limit is near.
get_vibe	One vibe's settings, build ids and URLs, and the website page for anything the server cannot do.
create_vibe	A new private vibe, from a template or empty.
push_source	Upload files (merged by path), run the preview build and return its outcome.
build_status	The state of a build or promotion that outran the push's wait.
publish	Promote the latest successful preview to production.
logs	Build log lines, for a build that failed.
list_source, get_source	Read the files already on a vibe before changing it.
call_tool, fetch_page	Run one of the vibe's tools, or fetch one of its pages, as you, to check a build before you look.
get_settings, set_settings	Read a vibe's settings; change its title. Visibility and interaction policy are set on the website.
list_secrets, set_secret, delete_secret, secret_audit	Encrypted secrets the worker reads as env.NAME (Pro or Pro+). Write-only: no tool returns a value.
list_access	Who a vibe is shared with. Granting and revoking happen on the website.
connect_info	The vibe's own MCP URL and the connector steps for each client.

Anything that exposes a vibe to other people — sharing, visibility, interaction policy, deleting — stays on the website. Claude gives you the link when you ask for one of those.

Where things show up

My Vibes lists every vibe Claude creates, with its preview and production links, settings and sharing. The connector itself is listed under Connected AI clients on the same page, with a revoke button. Secrets have their own page under your account.

When to prefer the CLI

The CLI skill is the better fit when the source lives on your machine: a project in git, an existing app you are bringing over, or anything you want to run locally with vibe dev and reload on save. Claude Code can use both at once — the skill for local work, this server for the platform — and the vibes are the same either way.