io.github.plyo-dev/plyo-mcp
OfficialThis server does not currently have a deployable release on Glama. Follow the repository's setup instructions to install and configure it for your MCP client, including any required credentials and local dependencies.
plyo-mcp
MCP server for Plyo — the home for AI-built projects. Every version saved, one click to undo, one click to publish, plus a security check before going live, visitor stats, health monitoring and database backups. Built for people who build with AI and don't code; this server is how their AI does the technical part.
Setup
Claude Code, one line:
claude mcp add plyo -e PLYO_TOKEN=plyo_xxx -- npx plyo-mcpAny other MCP client:
{
"mcpServers": {
"plyo": {
"command": "npx",
"args": ["plyo-mcp"],
"env": { "PLYO_TOKEN": "plyo_xxx" }
}
}
}PLYO_TOKEN is an AI key from the Plyo dashboard (Settings → AI keys → "Give your AI a key"). New here? Plyo is free to start. plyo.dev has the full picture; setup lives at plyo.dev/connect.html.
After setup, the user says: "I've added Plyo. Save this project there and keep saving as we go." That's the whole integration.
Related MCP server: Agent NextUp
Tools
Tool | What it does |
| Create a Plyo project and link the current folder to it |
| Link the current folder to an existing project by slug |
| Save the current state to the project's timeline (pass |
| Publish the latest checkpoint to the live URL; on failure returns a plain-English cause and a fix you can act on |
| Latest build status; if it failed, the translated error and fix guidance |
| Safe copy of the project to try changes without touching the live version |
| Return to an earlier checkpoint; never destructive, history is kept |
| Recent checkpoints with what changed in each |
| Snapshot the project's database and storage files before risky data changes |
| The user's projects with names, slugs and live URLs |
Notes for agents
Call
save_checkpointafter each completed piece of work, with a one-sentenceintent.Call
backup_databefore schema migrations, bulk updates or deletions.Errors come back plain and actionable: publish and build failures include what went wrong and what to change.
Under the hood every project is a real git repository; Plyo also accepts plain
git pushathttps://git.plyo.dev/{slug}.git(usernameplyo, the AI key as password).A failed publish never takes a live site down.
MIT · plyo.dev · hello@plyo.dev
mcp-name: io.github.plyo-dev/plyo-mcp
This server cannot be deployed
Maintenance
Related MCP Connectors
The home for AI-built projects: visitors, restore, publish with a safety check, data backups.
Deploy and manage Jade Hosting projects from AI clients. Jade account and OAuth required.
Project management shared by people and AI agents, with persistent project state through MCP.
Deploy and manage your apps, databases, storage, and scheduled jobs from your AI agent
Related MCP Servers
AlicenseCqualityCmaintenanceEnables AI agents to create, edit, and publish web apps on Prowpt.ai through project management, code editing, and AI assistant tools.59MIT- AlicenseNot gradedqualityBmaintenanceEnables AI agents to maintain project continuity through a file-based state hub with tasks, phases, and handoff snapshots. Provides MCP tools for reading and updating project state, with gatekeeping enforced via real-state evaluation and per-tool authorization.3MIT
- AlicenseAqualityDmaintenanceEnables AI agents to deploy, manage, and configure web applications on sota.io, including project creation, deployment, environment variables, custom domains, and rollbacks.1376 npmMIT
- AlicenseNot gradedqualityBmaintenanceEnables AI assistants to build, deploy, and inspect apps through a hosted backend service, including reading platform docs, deploying raw source, inspecting logs, verifying live pages in browsers, and managing project tasks.MIT