CLI and MCP

What it is

CLI and MCP use the same deploy path as the browser upload. You build a static bundle, Shippie scans it, uploads the package, and makes the app available from its live URL and Apps listing.

Use the browser form when you want the simplest path. Use CLI or MCP when you are already working from a repo, editor, or automated agent.

Fast path

Build your app to dist, build, out, or another static output folder. Then run shippie deploy with the output path and slug you want to claim.

• Example: shippie deploy ./dist --slug my-app.
• Private trials can be claimed later from Maker.
• Remixes should include the remix source so lineage stays visible.

What gets blocked

Shippie hosts static local apps. Server routes, bundled secrets, hidden trackers, ad code, unsafe network calls, and undisclosed user-data exits are blocked or flagged before publish.

External reference data is allowed when it is disclosed cleanly and does not send personal app content out by surprise.

After deploy

Open the live URL to test the app, save it to Apps when you want it close, and use Make for deploy history, visibility, feedback, access, and updates.