Back to Browse

Plyo MCP Server

Developer ToolsModerate5.2MCP RegistryLocal
Free

Server data from the Official MCP Registry

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

About

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

Security Report

5.2
Moderate5.2Moderate Risk

This is a well-structured MCP server for Plyo project management with proper authentication and reasonable security practices. The server requires API token authentication, uses environment variables for credential storage, and implements appropriate error handling. Minor issues include broad exception handling in file operations and lack of input sanitization in git branch names, but these do not represent significant vulnerabilities given the server's controlled purpose and design patterns. Supply chain analysis found 3 known vulnerabilities in dependencies (0 critical, 3 high severity). Package verification found 1 issue.

3 files analyzed · 8 issues found

Security scores are indicators to help you make informed decisions, not guarantees. Always review permissions before connecting any MCP server.

Permissions Required

This plugin requests these system permissions. Most are normal for its category.

env_vars

Check that this permission is expected for this type of plugin.

HTTP Network Access

Connects to external APIs or services over the internet.

File System Read

Reads files on your machine. Normal for tools that analyze or process local data.

File System Write

Writes or modifies files on your machine. Check that this is expected for the tool.

process_spawn

Check that this permission is expected for this type of plugin.

What You'll Need

Set these up before or after installing:

Plyo AI key (create in the dashboard: Settings > AI keys)Required

Environment variable: PLYO_TOKEN

How to Install

Add this to your MCP configuration file:

{
  "mcpServers": {
    "io-github-plyo-dev-plyo-mcp": {
      "env": {
        "PLYO_TOKEN": "your-plyo-token-here"
      },
      "args": [
        "-y",
        "plyo-mcp"
      ],
      "command": "npx"
    }
  }
}

Documentation

View on GitHub

From the project's GitHub 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:

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

Any 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.

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 · hello@plyo.dev

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

Reviews

No reviews yet

Be the first to review this server!