Connect a publishing MCP server to your agent and it can turn the HTML it generates into a live link by itself. With PubSpace that's one command: claude mcp add --scope user --transport http pubspace https://pubspace.ai/mcp. Your agent gets tools to publish a page, update it in place at the same link, list and fetch pages, take one offline, and, if you don't have an account yet, sign you up from the chat.
In Claude Code:
claude mcp add --scope user --transport http pubspace https://pubspace.ai/mcp--scope user registers it for every project on your machine. For other MCP clients (Cursor, Claude Desktop, Codex, and others), add the server URL https://pubspace.ai/mcp. Once you have an account, add your key as an X-API-Key header. PubSpace is listed in the official MCP Registry as ai.pubspace/mcp.
Without a key, your agent can still see what PubSpace does. When you ask it to publish, it asks for your email and a name for your space, creates the account, and asks you for the 6-digit code we email you. Then it publishes, in the same conversation. It also gives you the one-line command that keeps you connected next time.
Every tool is annotated read-only or destructive so your client can ask before anything irreversible. There's plain HTTP too: everything MCP does is also POST /api/publish. Full reference: llms.txt.
| Agent writes a file | Agent pushes to a repo / static host | Agent publishes to PubSpace | |
|---|---|---|---|
| You get a link back | No | Yes, after a deploy | Yes, at once |
| Update at the same link | — | Yes | Yes |
| Password or work-email lock | — | Extra setup | Built in |
| Setup | None | Repo, host, credentials | One command |
More guides
How to share a Claude artifact as a link →
Share an interactive HTML dashboard with stakeholders →