VibeKit
Enter App
Cursor Hosting
Deploy apps you build in Cursor straight to a live domain at yourapp.vibekit.bot. Every app gets a persistent AI agent, a real GitHub repo you own, and a database — so the app keeps running and improving after you close the editor.
Why use VibeKit with Cursor
- Cursor stays your editor. VibeKit doesn't replace the IDE — it hosts the app and runs a persistent agent next to it.
- Real GitHub repo. Cursor opens your code directly. Commit, branch, PR normally.
- Agent that doesn't forget. The VibeKit agent watches the app 24/7, auto-heals failures, and remembers past decisions.
- BYOK. Bring your own OpenAI or Anthropic key; your AI spend goes straight to the provider.
Two ways to deploy from Cursor
1. Cursor's terminal + CLI
npm install -g vibekit
vibekit login
vibekit deployThat's the same flow as any CLI tool — open Cursor's integrated terminal and run it.
2. MCP server (Cursor as an agent client)
Install the vibekit-mcp Model Context Protocol server and Cursor's agent mode can call VibeKit's hosting, deploy, and monitoring tools directly. Tell Cursor "deploy this to VibeKit" and the MCP server handles the rest.
What lives on VibeKit
The hosted app: runtime, database, domain, logs, agent memory. Your editor (Cursor) stays your editor. The repo lives under your GitHub account — you could walk away from VibeKit and keep working.
FAQ
Why host Cursor apps on VibeKit?
Cursor is your editor; VibeKit is where your app actually runs. VibeKit gives every Cursor-built app a live domain, runtime, database, logs, and a persistent AI agent that keeps working on the app after you close Cursor.
How do I deploy from Cursor to VibeKit?
Either push your Cursor project to GitHub and let VibeKit auto-deploy, or install the vibekit-mcp Model Context Protocol server and tell Cursor's agent to deploy. The MCP server gives Cursor direct tool calls for VibeKit hosting.
Do I still own my code if I use VibeKit with Cursor?
Yes. The canonical copy is a GitHub repo under your account. Cursor edits it, VibeKit deploys it. You could walk away from VibeKit tomorrow and keep working — nothing is locked in.
Does VibeKit use my Cursor AI credits?
No. Cursor AI and VibeKit's agent are independent. Cursor's AI spend is on Cursor; VibeKit uses its own agent (your Anthropic/OpenAI key with BYOK, or VibeKit balance). You can use either, both, or neither for any given change.
What lives on VibeKit vs Cursor?
VibeKit handles the hosted app: runtime, database, domain, logs, agent memory. Cursor stays your editor. The GitHub repo is the shared source of truth both tools read and write.