Skip to content
Start building

Build from your AI tools

Connect Claude, ChatGPT, Cursor, Claude Code, VS Code or Codex. Your assistant can create a project, keep building it, read the diff and publish it.

Connect your assistantRead the docs

Works on every plan. Sign in with OAuth, no API key.

The Vibely MCP server lets Claude, ChatGPT, Cursor, Claude Code, VS Code and Codex build, edit, review and publish your Vibely apps. You sign in with OAuth and choose its permissions. It has 52 tools, and only three of them (creating a project, sending a message and approving a plan) use credits.

Connect from

  • Claude
  • ChatGPT
  • Claude Code
  • Cursor
  • VS Code
  • Codex

Get started

New to MCP? Read what the Model Context Protocol is.

  • Connect in a chat app

    In Claude or ChatGPT, open Settings → Connectors, add a custom connector and paste https://api.vibely.sh/mcp. Sign in to Vibely and untick any permission you don’t want to give.
    Open Connected AI apps

  • Connect in your editor or terminal

    One command in Claude Code or Codex, or a few lines of JSON in Cursor and VS Code. Then sign in to Vibely in your browser.
    claude mcp add --transport http vibely https://api.vibely.sh/mcp

Latest MCP updates

What your assistant can do in Vibely

claude mcp add --transport http vibely https://api.vibely.sh/mcp

Create and iterate

create_project starts an app from a prompt, send_message keeps building it, and answer_question and approve_plan answer the agent when it asks.

Review the code

get_diff, list_edits, list_files and read_file let your assistant read exactly what changed before you ship it.

Publish and ship

deploy_project publishes the web app and returns the live URL. Mobile builds and store submission work the same way.

Works where you already ask

  • Chat apps

    Add a custom connector, sign in, and untick anything you don’t want to allow.

  • Editors

    Cursor and VS Code read the server from mcp.json. Reload, then sign in once in the browser.

  • Terminals

    One command adds Vibely to Claude Code or Codex. Sign in from the terminal’s browser prompt.

See every call it makes

Settings → Connected AI apps lists each app, its permissions, when it was last used and its recent tool calls. Disconnect revokes every token it holds, immediately.

Open Connected AI apps

Vibely speaks MCP three ways

Frequently asked questions

No. Connectors let Vibely use your tools while it builds. The Vibely MCP server works the other way round: it lets your AI assistant use Vibely.

The Vibely MCP server works on every plan, including Free.

Only three tools do: create_project, send_message and approve_plan, the ones that run the Vibely agent. They spend workspace credits exactly as the editor does. Every other tool is free.

Only what you can see, within the permissions you grant on the consent screen. Workspace owners and admins can switch AI apps off, allow approved apps only, or block SQL and publishing for AI apps.

No. When a build needs an API key, Vibely asks you for it in the editor, not in the assistant chat.

240 tool calls a minute per connection, and 30 a minute for the tools that use credits.

Technical rundown

Connect your assistant

claude mcp add --transport http vibely https://api.vibely.sh/mcp