Veable
Settings
Checking account
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
  • •Desktop-agent pairing and usage checks
  • •Local project output through an approved desktop connector
  • •Landing-page mode only
Active
Pro
US$4.99 monthly
Clone and edit landing pages with your own builder.
  • •Use an approved local desktop agent
  • •Landing-page clone and natural edit flow
  • •Local project output through the approved desktop agent
  • •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
0 free left
Publishing
Optional hosted publishing not enabled
Connections
Build engines connected to this account.
Desktop agents
No desktop agent approved 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. Run this from the standalone Veable repository root.

npm run mcp
Output
Local project folder
Storage
Not uploaded unless you later choose share or deploy
Billing
Uses your Veable plan and fair-use checks