Veable
Settings
Account, billing, usage, and build connections Veable uses for clone jobs.
Account
Profile information from your sign-in provider.
Name
Email
Account id
Billing
Bring your own builder. Veable bills for app access, runner coordination, usage checks, and support around the clone workflow.
Current plan: Basic. No surprise bills; high usage gets a warning before anything changes.
Basic
$0 free
Try the clone workflow before upgrading.
- •Free clone allowance
- •Runner pairing and usage checks
- •Local project output through Veable Runner
- •Landing-page mode only
Active
Pro
$4.99 per month
Clone and edit landing pages with your own builder.
- •Bring your own local builder through Veable Runner
- •Landing-page clone and natural edit flow
- •Local project output through Veable Runner
- •MCP access for Codex, Claude, Cursor, GLM, Kimi and other AI editors
- •Fair-use build queue
Usage
Clone allowance is live. Publish and traffic controls appear here only when hosted publishing is enabled for your account.
Clone access
Used
Reserved
Remaining
Publishing
Connections
Build engines connected to this account.
Local runners
No local runner connected yet.
Use Veable in your AI editor
Optional MCP workflow for Codex, Claude Desktop, Claude Code, Cursor, DeepSeek, GLM, Kimi, and other MCP-capable tools.
Keep using the web app for account, preview, chat, and local folder controls. MCP is for local work: your AI editor calls Veable, the project is written to your machine, and Veable checks subscription and usage.
npm --prefix tools/lovable-clone run mcp
Output
Storage
Billing