plyo-mcp

MCPcommunity

v0.4.3io.github.plyo-devUnknownUpdated 1mo agonpm GitHub

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

Works in

ClaudeCursorCopilotGemini

Inferred from the transports this listing declares (stdio). A client not listed here hasn’t been ruled out — it just isn’t something Forge can confirm.

Automatically indexed from public sources. Not yet verified by the developer on Forge.Claim this listing →

1mo agoLast update

Needs 1 credential before it runs

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

Declared by the author in the official MCP registry. Forge does not store, broker, or ever see these values — the config below is scaffolded with placeholders you fill in locally.

Package

Authorio.github.plyo-dev

LicenseUnknown

Version0.4.3

Sourcenpm+mcp-registry

GitHubplyo-dev/plyo-mcp

SBOMCycloneDX 1.6 ↓

Trust Status

B

60/100Good

✓Listed in Forge index+10/10

—Publisher identity verified+0/20

→ Publisher: run `forge publish` from the package repo to claim ownership

—Ed25519 publish signature+0/5

→ Included automatically when the publisher runs `forge publish`

—Domain verification+0/5

→ Publisher: host /.well-known/forge.json on the package homepage with { "publisher": "<github-login>" }

—npm Trusted Publishing (Sigstore)+0/5

→ Publish from GitHub Actions with --provenance so the attestation binds this package to this repo

—npm maintainer match+0/5

→ Earned once your identity is verified above and that login is an npm maintainer of this package

✓CVE scan · clean+30/30

✓Static analysis · clean+20/20

Paste into Claude Code, Cursor, or any AI assistant to fix all gaps

StatusCommunity-indexed

PublisherUnverified

SignatureUnsigned

Domain—

Provenance—

Dependencies✓ 60 resolved+ · none vulnerable

Tool surface11 tools · none privileged

Security scan✓ Cleanv0.5.0 · todayHow well does this scan work?

EvalsNone

IndexedAug 30, 2026

Verification confirms publisher identity (repo ownership), not code safety. The security scan covers known CVEs and suspicious install scripts.

Tools

11 tools · none privileged

Statically extracted from the published packagev0.5.0 · 21h ago

Read out of the source npm actually ships, at scan time. The package was never executed. Tools registered dynamically at runtime, or hidden inside bundled or minified code, can be missed — so this is a floor on the tool surface, not a complete census of it.

Filter toolsPrivileged only

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

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

No input schema was published for this tool.

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

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

No input schema was published for this tool.

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

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

No input schema was published for this tool.

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

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

No input schema was published for this tool.

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

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.

No input schema was published for this tool.

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

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.

No input schema was published for this tool.

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

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

No input schema was published for this tool.

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

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

No input schema was published for this tool.

get_pending_tasksFix instructions the user queued for you from Plyo (they pointed at problems on their site). Call once at session start. Returns each task once.

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.

No input schema was published for this tool.

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

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.

No input schema was published for this tool.

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

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

No input schema was published for this tool.

11 of 11 tools published a description.

Tool names and descriptions are written by the publisher and shown verbatim as inert text. They are the strings an MCP client passes to a model, so Forge scans them for prompt-injection patterns — any finding appears with the security scan above. “Privileged” is a keyword match on the tool name, not an audit of what the tool does: a benign-sounding name can still do anything.

About

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

Keywords

mcp

Alternatives

Comparing tool surfaces…

Tools exposed

11 tools · none privileged · observed 2026-09-29 by static extraction. A tool surface is what one scan read on one day, not a live capability list.

list_projects
create_project
link_project
save_checkpoint
start_draft
publish
get_build_error
get_timeline
get_pending_tasks
backup_data
restore

Linked names open Forge’s index of every entry observed exposing that tool. Browse all indexed tools.

Dependency tree

What one Forge scan resolved from npm metadata on 2026-09-29 — observed resolution, not a publisher declaration.

60 packages resolved · 2 direct · none carrying advisories Resolution stops at depth 4 and 60 packages.

zod3.25.76
@modelcontextprotocol/sdk1.31.017 dependencies
- ajv8.20.04 dependencies
  - fast-deep-equal3.1.3
  - fast-uri3.1.8
  - json-schema-traverse1.0.0
  - require-from-string2.0.2
- zod4.6.5
- cors2.8.6+1 not drawn1 dependency
  - object-assign4.1.1
- hono4.13.11
- jose6.2.12
- express5.2.1+27 not drawn1 dependency
  - content-type1.0.5
- raw-body3.0.2+4 not drawn
- ajv-formats3.0.11 dependency
  - ajv8.20.0shown above
- cross-spawn7.0.6+3 not drawn
- eventsource3.0.71 dependency
  - eventsource-parser3.1.1
- content-type1.0.5shown above
- pkce-challenge5.0.1
- @hono/node-server2.1.3
- json-schema-typed8.0.2
- eventsource-parser3.1.1shown above
- express-rate-limit8.7.0+2 not drawn
- zod-to-json-schema3.25.2

The crawl stopped at the depth-4 limit. Anything below that level was never resolved.

The crawl stopped at the 60-package limit. The rest of the tree was never resolved.

36 more resolved packages are not drawn here (display cap: 24). Every dependency carrying an advisory is drawn regardless of the cap. Full inventory (CycloneDX SBOM)

Declared but not resolved

54 declared dependencies never landed in the tree. They are missing from Forge's resolution, not from the package.

package cap reached: 49
below the depth cap: 5

wrappy 1 — required by once@1.4.0package cap reached
http-errors ^2.0.1 — required by send@1.2.1package cap reached
mime-types ^3.0.2 — required by send@1.2.1package cap reached
ms ^2.1.3 — required by send@1.2.1package cap reached
on-finished ^2.4.1 — required by send@1.2.1package cap reached
range-parser ^1.2.1 — required by send@1.2.1package cap reached
statuses ^2.0.2 — required by send@1.2.1package cap reached
ms ^2.1.3 — required by debug@4.4.3package cap reached
debug ^4.4.0 — required by router@2.2.0package cap reached
depd ^2.0.0 — required by router@2.2.0package cap reached
is-promise ^4.0.0 — required by router@2.2.0package cap reached
parseurl ^1.3.3 — required by router@2.2.0package cap reached

+42 more not listed. The counts by reason above cover all of them.

Not followed: peerDependencies. This tree covers runtime dependencies only, so anything those pull in was never resolved.