# plyo-mcp

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

- **Type:** MCP server
- **Trust:** 60/100 (B), scored on the package rubric
- **Verification:** community-indexed — nobody has claimed this listing
- **Version:** 0.4.3
- **Author:** io.github.plyo-dev
- **License:** Unknown
- **npm:** plyo-mcp
- **Source:** https://github.com/plyo-dev/plyo-mcp
- **Compatible clients:** claude-code, cursor, copilot, gemini (basis: transport)

## Trust

60/100 (B), scored on the package rubric
- Publisher verified: no
- Install scripts: nothing suspicious found
- Prompt-injection scan: not run
- Obfuscation scan: not run
- Evidence age: 0 days

## Security scan

- **Status:** clean
- **Scanned:** 2026-09-29T08:24:52.330Z
- **Version scanned:** 0.5.0
- **CVEs:** none found by OSV at scan time

## Tools

11 declared. Statically extracted from the shipped source — a floor on the surface, not a census.
- `list_projects` — List the user's Plyo projects (name, slug, live URL).
- `create_project` — Create a new Plyo project and link the current folder to it. Existing files stay untouched; use save_checkpoint afterwards to store them.
- `link_project` — Link the current folder to an existing Plyo project by slug.
- `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 dr
- `publish` — 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.
- `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.
- `get_pending_tasks` — Fix instructions the user queued for you from Plyo (they pointed at problems on their site). Call once at session start. Returns each task once.
- `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 do
- `restore` — Restore the project to an earlier checkpoint. Never destructive: a new checkpoint is created and everything stays on the timeline.

## Install

**Verdict: review** — Installable, but 1 thing to check first: No publisher has proved control of this listing; it is indexed, not vouched for.
**Cautions** (coverage gaps and advisories — never blocking)
- No publisher has proved control of this listing; it is indexed, not vouched for.
**Config** (claude-code):
```json
"{\n  \"mcpServers\": {\n    \"plyo\": {\n      \"command\": \"npx\",\n      \"args\": [\n        \"-y\",\n        \"plyo-mcp\"\n      ],\n      \"env\": {\n        \"PLYO_TOKEN\": \"<YOUR_PLYO_TOKEN>\"\n      }\n    }\n  }\n}"
```
**Credentials it will ask for** (names only — Forge never holds a value):
- `PLYO_TOKEN` — Plyo Token (required)
Placeholders only. Forge never holds, brokers, or transmits a credential value — replace each <YOUR_NAME> in your own config file. Do not send a value back to Forge; no Forge endpoint accepts one.
- This entry needs 1 credential (1 required). The generated config carries placeholders, so it will fail in the editor rather than at runtime if they are left unset.

## Blast radius

Moderate blast radius — holds an api key; runs on your machine.
- Floor 23, ceiling 23 (tier: moderate)
- This is impact, not likelihood. A high radius is not a defect: a filesystem server is supposed to write files. It is never part of the trust score.

## Machine-readable views of this entry

- Signed JSON: https://forgeregistry.com/api/v1/packages/plyo-mcp
- Install plan: https://forgeregistry.com/api/v1/packages/plyo-mcp/install-plan
- Alternatives: https://forgeregistry.com/api/v1/alternatives/plyo-mcp
- HTML page: https://forgeregistry.com/registry/plyo-mcp
- MCP: POST https://forgeregistry.com/api/mcp → `forge_get_package` / `forge_install_plan`

## About this document

Generated by Forge (https://forgeregistry.com) — a compact rendering of the same record served, signed, at the JSON URL above. Trust and scan facts are the registry's own measurements; anything Forge did not measure is named as unmeasured rather than omitted.