Plyo Mcp

io.github.plyo-devPublished by GitHub account plyo-devv0.4.3Updated Oct 24, 2026

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

The publisher's own server: Plyo

VerifiedSTDIODesktop onlyCloud & InfrastructureFiles & StorageDeveloper Tools

Overview

AI-generated overview

Local MCP server that lets an AI assistant create, checkpoint, publish, restore and back up AI-built projects hosted on Plyo.

What you can do
Create or link Plyo projects to the current folder and list the user's projects with slugs and live URLs. Save checkpoints to a project timeline with a one-sentence intent, and view recent checkpoints and what changed. Publish the latest checkpoint to the live URL, read build status and translated error guidance, and start a draft copy for safe experiments. Restore earlier checkpoints without destroying history, and snapshot the project database and storage files before risky changes.
When to use it
For people building projects with AI who want the assistant to handle versioning, publishing and backups on Plyo without manual git or deployment work. Useful when a project needs a safe draft, a rollback point, or a data backup before migrations or deletions.
Requirements
Runs locally via npx (Node.js) over stdio. Requires a Plyo account and a Plyo AI key supplied in the PLYO_TOKEN environment variable, created in the Plyo dashboard under Settings > AI keys. Network access to Plyo is needed.
Before you install
The PLYO_TOKEN key grants access to the user's Plyo projects and is also usable as a git password, so keep it private. Publishing pushes changes to a live public URL, and restore, backup and checkpoint actions change project state; a failed publish reportedly does not take a live site down. Project data is sent to Plyo's servers.

Installation

In SourceWeft

  1. Open Plyo Mcp in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

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:

bash
claude mcp add plyo -e PLYO_TOKEN=plyo_xxx -- npx plyo-mcp

Any other MCP client:

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

ToolWhat it does
create_projectCreate a Plyo project and link the current folder to it
link_projectLink the current folder to an existing project by slug
save_checkpointSave the current state to the project's timeline (pass intent: one sentence on what the user asked for; it powers timeline search)
publishPublish the latest checkpoint to the live URL; on failure returns a plain-English cause and a fix you can act on
get_build_errorLatest build status; if it failed, the translated error and fix guidance
start_draftSafe copy of the project to try changes without touching the live version
restoreReturn to an earlier checkpoint; never destructive, history is kept
get_timelineRecent checkpoints with what changed in each
backup_dataSnapshot the project's database and storage files before risky data changes
list_projectsThe 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.

MIT · plyo.dev · [email protected]

mcp-name: io.github.plyo-dev/plyo-mcp

Source: README.md at commit ff90978

Tools

0
SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

1
  1. v0.4.3LatestSep 16, 2026

Score

50% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 days25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts

Other Plyo integrations

Plyo

dev.plyoOfficial publisher

Plyo lets an assistant manage AI-built projects: view visitors, restore versions, publish with a safety check, and back up data.

Streamable HTTPWeb executableAuth
Productivity & WorkflowCredential requiredOct 24, 2026