Skip to main content
Most builds start by typing into the Vibely app. Some do not — an idea lands in a group chat, a teammate should be the one to build it, or a script needs to kick off a project with no human at the keyboard. Four things are real today. Start with what you actually need.
There is no Slack app, Telegram bot, or ChatGPT integration. If you have seen one advertised, it was not ours. Everything on this page is what ships.
Start a build from outside Vibely
vibely.sh/tools/link-generator turns an idea into a post you can paste into a thread, a channel, or a DM.
1

Write the prompt

Up to 2,000 characters. It is a prompt, not a spec document — name the job, the sections and the feel, and let the build ask about the rest.
2

Pick the target

Web app for something that lands on a live URL. Native mobile app for a real Expo app the builder can open on their own phone while it is still being written.
3

Copy the post

You get the prompt and the matching link, formatted and ready to paste.
The result looks like this:
The prompt travels as text next to the link, not inside it. Whoever opens the link lands on Vibely with the prompt sitting right there in the post to paste. That is the whole trick, and it is why the post is worth copying rather than just the URL. No account is needed to share one. The person who opens it needs one to build.

​
The build stream API

POST /api/v1/vibe/stream is the same endpoint the Vibely app itself calls. Anything the app can start, an external caller can start.
It returns Server-Sent Events as the build runs. Omit project_id to create a project; pass it to continue one, which is how an agent carries a build across several turns. Auth is a Supabase-issued JWT, short-lived (1 hour) — so a long-running caller has to handle 401 by re-authenticating rather than holding a token forever. The AI gateway your generated app calls is a different surface with a different key; see Authentication for both. Full request schema, every event type, and the error shapes are in Build Stream.

​
MCP works in both directions

Vibely as an MCP server. AI tools such as Claude, ChatGPT, Cursor, Claude Code and Codex can connect to Vibely and create, edit, inspect and publish your apps with your account’s access. See the Vibely MCP server page for the server URL and per-client setup, or open Settings → MCP server in the app. Vibely as an MCP client. The other direction is just as useful: connect your own MCP servers, and the build agent gains mcp_list and mcp_call. It can then query your database, hit your internal API, or read your issue tracker while it is building — so the app it writes matches your real schema instead of an invented one.