Ploa

dev.ploaPublished by ploa.devOfficial publisherv0.2.2Updated Nov 7, 2026

Ship apps for iPhone, iPad, Mac, Apple TV, Vision Pro and Android to the App Store and Google Play

VerifiedStreamable HTTPWeb executableDeveloper Tools

Overview

AI-generated overview

Ploa lets an assistant ship iPhone, iPad, Mac, Apple TV, Vision Pro and Android apps to the App Store and Google Play.

What you can do
  • Ship apps for Apple platforms and Android to the App Store and Google Play.
  • No tools are listed in the manifest, so the exact operations available to an assistant are not documented here; the description only covers app publishing.
When to use it
Worth considering if you build mobile or Apple-platform apps and want an assistant to help with getting releases to the App Store and Google Play.
Requirements
A remote endpoint at ploa.dev, or the local npm package @ploa/cli run with npx over stdio. OAuth authentication is required; a token can be supplied via the PLOA_TOKEN secret or obtained once with the CLI login command. PLOA_SERVER can point at a different Ploa server.
Before you install
The server requires an account token (PLOA_TOKEN) that grants access to your Ploa workspace. Publishing apps changes live store listings and releases, so review any action before it is carried out. No tool list is published, so what the assistant can actually do should be confirmed before installing.

Installation

In SourceWeft

  1. Open Ploa 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.ploa%2Fploa/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": {
    "ploa": {
      "type": "http",
      "url": "https://ploa.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

2
  1. v0.2.2LatestNov 7, 2026
  2. v0.1.0Oct 31, 2026

Score

60% 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.

  • License10 pts

    Declare a license in the repository or the registry entry.