doable.do

Doable for Claude Code

Deploy from Claude Code with /deploy

Doable adds /deploy to Claude Code via MCP. The same chat that wrote your app ships it, no dashboard, no copy-pasting commands into a separate terminal. The model bundles your repo, builds it on our worker, and hands back the live URL inline.

Setup in two steps

1. Install (one-time, in your project directory)

npx -y doable-cli setup

2. Deploy (in Claude Code)

Type /deploy or use natural language:

  • "deploy this"
  • "ship the changes"
  • "put this live"
  • "push to prod"

Doable's MCP tool descriptions lead with these trigger phrases so Claude Code routes intent to /deploy without command-style invocation.

Why Doable + Claude Code

Native MCP, no shell-out

Doable is a first-class MCP tool, not a CLI Claude Code shells out to. The model knows the deploy state, can read logs, can apply Doctor fixes, all inside the conversation.

Chained intent, deploy → logs → fix → redeploy

A failed build flows through doable.deploy → doable.logs → doable.doctor_analyze → doable.doctor_apply → doable.deploy again, all in one Claude Code turn. No human in the middle for the common-case fix.

No browser switch

Live URL appears in the chat as soon as the deploy is healthy. Click to open, share, or paste anywhere, without ever leaving the editor.

Works alongside everything else

Doable's MCP server doesn't replace anything in Claude Code, it sits next to the filesystem, bash, and other tools. No conflicts, no opinions about how you write code.

FAQ

Do I need a Doable account before installing?

No. After running the setup command, type /deploy on a fresh project, Claude Code will ask whether you want a permanent project (free signup, 30 seconds in your browser) or a 8-hour preview (no signup). Both paths work the same after that.

Why not just use Claude Code's bash tool to run `vercel deploy`?

You can, but the MCP path is tighter. Doable's tools return structured data the model can reason about (deployment ID, status, log events), so chained flows like 'deploy → see error → propose fix → reapply' work in one turn. Bash output is just a string the model has to parse.

What does the Doable MCP server have access to?

Only the directory you run /deploy in (for bundling), plus the Doable API. It can't read other files on your machine, can't access other MCP tools' state, and never sees your Claude Code credentials.

How do I uninstall?

Remove the `doable` entry from `.mcp.json` in any project where you ran setup. The `npx` command leaves nothing on your machine, there's no globally-installed binary.

Create a free account

No credit card. Or try with any GitHub URL without signing up.

Use a different editor? Doable for Cursor · Doable for Codex