Doable for Cursor
Cursor's chat panel becomes a deploy console. Install Doable as an MCP tool, ask Cursor to deploy your project, and it bundles, builds, and ships, returning the live URL directly in chat. Same flow whether you use Cursor's Composer, Chat, or Agent mode.
1. Install (one-time, in your project directory)
npx -y doable-cli setup --cursor
2. Deploy (in Cursor)
Type /deploy or use natural language:
Doable's MCP tool descriptions lead with these trigger phrases so Cursor routes intent to /deploy without command-style invocation.
Chat, Composer, and Agent mode all see the Doable MCP tools. Pick whichever workflow you prefer; the deploy verb is consistent.
Doable lives in `.cursor/mcp.json` inside each project that opts in. No always-on background process; no global state to debug.
When a deploy fails, Cursor runs doable.doctor_analyze automatically, proposes a fix in chat, and applies it on your approval. The full retry loop happens without leaving the editor.
Doable produces a real Docker image. If you outgrow our Cloud, the same image runs on any Linux host via `doable server add`. Switching costs are zero.
Yes, Composer reads the same MCP tool registry as Chat. Type /deploy in either, or describe what you want in natural language; Cursor routes to doable.deploy automatically.
The `.cursor/mcp.json` file is checked into your repo, so any machine that opens the project gets Doable. The first deploy from each machine prompts for sign-in (one browser tap).
Cursor has integrations with specific platforms (Vercel, Netlify) for some templates. Doable runs on top of MCP, so it works for any project, your own apps, GitHub clones, AI-generated code, without needing a per-platform integration.
Yes. Sign in to Doable once and use the authenticated `doable.deploy` flow. For public repos you can also use the no-signup preview at doable.do/try.
No credit card. Or try with any GitHub URL without signing up.