Built something with an AI assistant? Ask it to put it on Prototir. It uploads the build from the same chat or terminal, and you finish publishing on prototir.com.
The first time, your assistant shows a code. Approve it on prototir.com and that computer can upload builds to your account. It cannot publish, comment or change anything else, and you can unlink it from your account settings.
It finds the build (the folder with index.html, often dist/, build/ or out/), zips it and uploads it. Source code is never uploaded by mistake: without a build it asks to build first.
It gives you a link to the upload page with the build already attached. You choose the title, visibility and rights, and press Publish. Nothing goes public on its own.
Assistants that run commands for you need no setup: ask them to publish to Prototir, or run it yourself.
npx @prototir/cli publish ./distTo publish or share what we build, run: npx @prototir/cli publish <build folder>
It prints a link where I finish publishing on Prototir.Given a project folder, it uses the folder that holds index.html. Add --title to
name a new prototype, or --slug to add the build to one you already have.
For assistants that use MCP servers, add Prototir once. They get tools to link, publish and check which account they are linked to.
{
"mcpServers": {
"prototir": {
"command": "npx",
"args": ["-y", "@prototir/cli", "mcp"]
}
}
}claude mcp add prototir -- npx -y @prototir/cli mcp[mcp_servers.prototir]
command = "npx"
args = ["-y", "@prototir/cli", "mcp"]npx @prototir/cli publish ./Build --native --platform windows --arch x64A downloadable build uploads the same way, with its platform (windows, macos or linux) and architecture (x64, arm64 or universal). To count sessions and collect feedback it needs the Prototir SDK for its engine: see the creator guide.