Plyo

dev.plyoPublished by plyo.devOfficial publisherv1.0.0Updated Oct 24, 2026

The home for AI-built projects: visitors, restore, publish with a safety check, data backups.

VerifiedStreamable HTTPWeb executableProductivity & WorkflowCloud & Infrastructure

Overview

AI-generated overview

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

What you can do
Plyo is a hosted service for projects built with AI. Through its remote MCP endpoint, an assistant can work with a project's visitor information, restore earlier versions, publish a project after a safety check, and handle data backups. The manifest does not list individual tools, so the exact operations are not documented here.
When to use it
Worth considering if you keep AI-generated projects on Plyo and want an assistant to help with publishing, rolling back to an earlier version, checking visitor activity, or managing backups without leaving the chat.
Requirements
A remote MCP endpoint at api.plyo.dev over streamable HTTP. OAuth authentication is required, so you need a Plyo account and must complete the OAuth sign-in flow. No environment variables or headers are declared.
Before you install
Publishing and restoring change the live state of a project, and backups may overwrite or replace existing data, so confirm before letting an assistant run them. Access is granted through OAuth to your Plyo account, so review which permissions you approve. Visitor data may be personal information.

Installation

In SourceWeft

  1. Open Plyo in the dashboard and add it to a workspace.
  2. Connect the required credentials. They are stored privately and never shown on public pages.
  3. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/dev.plyo%2Fplyo/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config. The client completes OAuth sign-in on first connect.

{
  "mcpServers": {
    "plyo": {
      "type": "http",
      "url": "https://api.plyo.dev/mcp"
    }
  }
}

Tools

0
This server asks you to sign in, so SourceWeft could not read its tools without an account and has not indexed them. What a connected account sees can depend on that account and its permissions.

Version history

1
  1. v1.0.0LatestSep 16, 2026

Score

67% 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 daysRequired25 pts
  • Auth declaredRequired10 pts
  • 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

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • LicenseNot applicable

    A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.

Other Plyo integrations