MCP.Market

Plyo MCP server

by plyo-dev·io.github.plyo-dev/plyo-mcp·v0.4.3
No reviews yet

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

B75/100grade B
Write a reviewInstall
What users say
No reviews yet
Be the first
Safety scan
B75/100

full report

Adoption
New

0 stars30 downloads/wk

Reviews

Write one

Nobody has reviewed Plyo yet.

If you have run it, two minutes of your experience saves the next person an afternoon.

Plyo tools (10, 2 write)

write = sends, deletes, buys or posts

Read from the package source without running it. The installed server may list more.

  • backup_data

    Take a snapshot of the project's database (and storage files) before risky data changes — schema migrations, bulk updates, deletions. The user can restore or download it from Settings → Backups.

  • create_projectwrite action

    Create a new Plyo project and link the current folder to it. Existing files stay untouched; use save_checkpoint afterwards to store them.

  • get_build_error

    Get the most recent build's status, and if it failed, the plain-English error and the fix guidance.

  • get_timeline

    Show the project's recent checkpoints (the timeline) with what changed in each.

  • link_project

    Link the current folder to an existing Plyo project by slug.

  • list_projects

    List the user's Plyo projects (name, slug, live URL).

  • publishwrite action

    Publish the project's latest checkpoint to its live URL. Waits for the result; on failure, returns a plain-English cause plus a fix you can act on.

  • restore

    Restore the project to an earlier checkpoint. Never destructive: a new checkpoint is created and everything stays on the timeline.

  • save_checkpoint

    Save the current state of the project as a checkpoint on the user's Plyo timeline. Call this after completing a piece of work.

  • start_draft

    Start a Draft — a safe copy of the project to try changes without touching the live version. Switches this folder to the draft. If the user already started a draft in Plyo, pass its exact name and this folder joins it instead of creating a new one.

Public scan report

scanner v0.1.10 · 2026-10-30 · same rubric, same numbers if you re-run it

no findings
  • Code scan2 source files scanned25/25
  • –Live reliabilityno gateway calls yet and no remote to proben/a
  • –Tool poisoningtools not inspected (local package is not executed); not countedn/a
  • Auth qualitystatic API keys via environment variables6/15
  • Maintenancelast push 59 days ago12/15
  • Maintainer identityregistry namespace matches repository owner6/10
Overall 75/100. Components that don't apply are left out of the denominator. Any critical finding is an F.RubricAppeal a findingJSON

How Plyo compares

Against every graded MCP server, from our own scans and uptime checks. Updated after each scan run.

Safety score
75/100
higher than 45% of 48,243 servers
Tools
10
the typical server has 7
Tools that change things
20%
typical: 0%. Fewer write tools means less an agent can break
Downloads a week
30
more than 18% of 12,306 servers with a package

What its tools let an agent do: 6 read · 2 create · 1 send or post · 1 run or deploy

Install Plyo in Claude Code, Cursor or VS Code

Runs npx -y plyo-mcp on your machine. Read the scan report first; the gateway never runs local packages.

claude mcp add plyo-mcp -- npx -y plyo-mcp
Add to Cursor

What the publisher says

From the Plyo repository's README, as published. We do not edit it. Read it on GitHub

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

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

Nothing above is checked by us. What we check is on the safety report.

Plyo: common questions

Is Plyo MCP server safe?
Mostly: it is graded B (75/100). Read the Plyo safety report
How do I install Plyo?
It runs on your machine. Copy the Claude Code, Cursor, VS Code or Claude Desktop config from the install section.
Does Plyo need an API key?
Yes. The registry entry asks for PLYO_TOKEN.
Is Plyo maintained?
The last commit was 65 days ago (2026-09-01). The latest release is v0.4.3.
How does Plyo compare with other MCP servers?
safety score 75/100 (higher than 45% of 48,243 servers); tools 10 (the typical server has 7); tools that change things 20% (typical: 0%. Fewer write tools means less an agent can break). Full comparison.