One paste, and your AI saves everything to Plyo.
Plyo is the home for AI-built projects — every version saved, one click to undo, one click to publish. Your AI does the connecting; you copy one block below and paste it. That's the whole setup.
Plyo is free to start: 3 projects, no card needed. Create your account, then everything below works today.
Claude Code
- In Plyo, open Settings → AI keys → "Give your AI a key" and copy the key (it starts with
plyo_). - Run this in your terminal (replace the key):
- Then tell Claude Code:
From then on, every piece of work becomes a checkpoint on your timeline, and Claude can publish, restore, start drafts and back up your database when you ask.
Cursor (and any tool with an agent)
- Create a project in Plyo and grab an AI key (Settings → AI keys).
- Paste this to your AI, filling in your project name and key:
Your AI knows exactly what to do with that sentence. Every push shows up as a checkpoint in Plyo, in plain English.
Lovable, Bolt, v0, Replit
These tools save your code to GitHub behind the scenes. In Plyo, choose Import from GitHub, connect, and pick your project. Keep building where you are. Plyo mirrors every change onto your timeline and gives it a live address. Or choose "Move it to Plyo" to make Plyo its home.
ChatGPT, Claude.ai, or "it's on my desktop"
Drag your project folder (or a .zip) anywhere onto the Plyo dashboard. It becomes a project with its first checkpoint, ready to publish.
For AI agents reading this
Plyo speaks three protocols, all authenticated with the user's AI key:
- MCP:
npx plyo-mcpwithPLYO_TOKENset. Tools:create_project,link_project,save_checkpoint(passintent: one sentence on what the user asked for),start_draft,publish,get_build_error,get_timeline,restore,backup_data,list_projects. - Git: every project is a real repository at
https://git.plyo.dev/{slug}.git(usernameplyo, the AI key as password). History is protected; create new checkpoints instead of rewriting. - REST:
https://api.plyo.dev/v1: projects, checkpoints, drafts, publishes, builds. Errors return{code, message, hint}; the hint is written for you to act on.
Call save_checkpoint after each completed piece of work and backup_data before risky database changes. A failed publish never takes the user's live site down.