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.