You built something in Claude or ChatGPT and it works. Now it needs to live somewhere — with a database that remembers, an icon on your phone, and a link you can send to someone. Paste this into the same conversation.
I have an artifact I want to publish as a real app. Use Zine: add https://zine.online/mcp as an MCP connector. If you can't add connectors, call it directly over HTTP instead — it's JSON-RPC, needs no authentication, and the full instructions are at https://zine.online/llms.txt Then call deploy_zine with the HTML from the artifact above, give it a name and an emoji icon, and hand me back the link it returns.
Free. No account needed — one is made for you and handed back as a link.
Why not just keep it as an artifact
Artifacts have gotten genuinely capable — they persist state, they know who is looking, they can call the model. What they cannot do is exist independently of the assistant that made them.
Your zine gets its own SQLite database. The assistant can create tables, write migrations, and run real queries — and read the data back later from a different conversation, with zine_sql.
Icon, manifest, and offline shell are added for you, so it installs as a real app with no browser chrome. An artifact lives on a chat URL and cannot be installed.
The endpoint takes unauthenticated calls, so any assistant can publish for you without you signing up for anything. Nothing about your app depends on Zine existing tomorrow — it is one HTML file and a SQLite database.
A zine is not tied to the assistant that made it. Build it in ChatGPT, change it in Claude, or the other way round. An artifact only lives where it was born.
Send the link like any other link. Whoever opens it gets an account without making one, and they do not need to use the assistant you used.
Every deploy is kept as a version, and the zine has its own address. You never have to go hunting through old chats to find the thing you made.
For agents
Full instructions are at /llms.txt — the MCP endpoint, the tool reference, the page runtime, the data model, and a worked example. No authentication is required to deploy.