Plyo Mcp

io.github.plyo-dev由 GitHub 账号 plyo-dev 发布v0.4.3更新于 Oct 24, 2026

Save, publish, restore and back up AI-built projects on Plyo, for people who build with AI.

发布方自己的服务：Plyo

已验证STDIO仅桌面云端与基础设施文件与存储开发者工具

服务详情

标识符: io.github.plyo-dev/plyo-mcp
传输: STDIO
运行时: Desktop only
信任: Verified
发布于: Sep 16, 2026

安全提示

MCP 服务会接收对话中的工具调用请求，并可能执行外部操作。启用前请先了解该服务能做什么，并只授予它所需的权限。

注册中心已验证此条目所属的 GitHub 账号 plyo-dev。这并不表明该账号就是产品方。

SourceWeft 的检查只涵盖条目是否完整、端点是否响应；不审查服务器的代码，也不审查其工具的行为。

在 README 中添加徽章

向读者展示该 MCP 服务已收录于 SourceWeft，徽章链接到本页。

[![Listed on SourceWeft](https://sourceweft.com/badge/mcp/io.github.plyo-dev%2Fplyo-mcp.svg)](https://sourceweft.com/mcp/io.github.plyo-dev%2Fplyo-mcp?utm_source=readme&utm_medium=badge)

概览

AI 生成的概览

本地 MCP 服务器，让 AI 助手在 Plyo 上创建、存档、发布、恢复和备份 AI 构建的项目。

可以做什么: 创建 Plyo 项目或将当前文件夹关联到已有项目，并列出用户的全部项目及其标识和线上地址。把当前状态保存为带一句话意图说明的检查点，并查看最近的检查点及变更内容。将最新检查点发布到线上地址，读取构建状态和通俗的错误修复建议，并创建草稿副本以安全试验改动。恢复到较早的检查点且不破坏历史，并在高风险数据改动前备份项目数据库和存储文件。
适用场景: 适合用 AI 构建项目、希望由助手代为完成版本管理、发布和备份而无需手动操作 git 或部署的用户。当项目需要安全草稿、回滚点，或在迁移、删除前需要数据备份时也适用。
运行要求: 通过 npx（Node.js）以 stdio 在本地运行。需要 Plyo 账户，并在 PLYO_TOKEN 环境变量中提供 Plyo AI 密钥，该密钥在 Plyo 控制台的 Settings > AI keys 中创建。需要访问 Plyo 的网络连接。

安装前请注意

PLYO_TOKEN 密钥可访问用户的 Plyo 项目，也可用作 git 密码，应妥善保密。发布会把改动推送到公开的线上地址，恢复、备份和检查点操作会改变项目状态；据说明发布失败不会导致线上站点下线。项目数据会发送到 Plyo 的服务器。

安装

在 SourceWeft 中

打开控制台中的 Plyo Mcp，将其添加到工作区。
为需要使用其工具的对话启用该服务。

Desktop only，通过 STDIO。 STDIO 服务会启动本地进程，因此需要 SourceWeft 桌面宿主。

其他 MCP 客户端

参照仓库中的启动说明。

README

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:

Any other MCP client:

json

{  "mcpServers": {    "plyo": {      "command": "npx",      "args": ["plyo-mcp"],      "env": { "PLYO_TOKEN": "plyo_xxx" }    }  }}

{  "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.

Tools

Tool	What it does
`create_project`	Create a Plyo project and link the current folder to it
`link_project`	Link the current folder to an existing project by slug
`save_checkpoint`	Save the current state to the project's timeline (pass `intent`: one sentence on what the user asked for; it powers timeline search)
`publish`	Publish the latest checkpoint to the live URL; on failure returns a plain-English cause and a fix you can act on
`get_build_error`	Latest build status; if it failed, the translated error and fix guidance
`start_draft`	Safe copy of the project to try changes without touching the live version
`restore`	Return to an earlier checkpoint; never destructive, history is kept
`get_timeline`	Recent checkpoints with what changed in each
`backup_data`	Snapshot the project's database and storage files before risky data changes
`list_projects`	The user's projects with names, slugs and live URLs

Notes for agents

Call save_checkpoint after each completed piece of work, with a one-sentence intent.
Call backup_data before 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 push at https://git.plyo.dev/{slug}.git (username plyo, the AI key as password).
A failed publish never takes a live site down.