From AI session to shared page
in about a minute
ProtoServe is a home for the single-file HTML pages your AI sessions produce — exports, demos, case studies, one-pagers. Publish from wherever you work; every page gets an unguessable live URL and lands on your dashboard with an auto-generated thumbnail, description, and tags.
Get an account
Sign in with Google — that's the whole signup. Red Bridge accounts can publish immediately; everyone else lands in a pending state until an admin approves them, and can browse pages shared with them in the meantime.
Connect your AI tool
ProtoServe runs an MCP server at https://protoserve.com/mcp. Any client that speaks streamable
HTTP with OAuth can connect — you sign in with Google once and approve access.
Claude Code
One command in any terminal, then authenticate via /mcp.
claude.ai & desktop
Settings → Connectors → Add custom connector → paste the /mcp URL.
Codex & others
Add the server in ~/.codex/config.toml — remote-MCP support varies by version.
# Claude Code claude mcp add --transport http protoserve https://protoserve.com/mcp # Codex (~/.codex/config.toml) [mcp_servers.protoserve] url = "https://protoserve.com/mcp"
Once connected, your assistant has four tools: publish_page, update_page, list_pages, and share_page — publishing something new and revising it later are both one sentence.
Publish your first artifact
Just ask, in your own words:
You get back a live URL, and the page appears on your dashboard moments later with its thumbnail and tags. That's the whole loop — nothing to install per project, no token to paste, no file paths to copy. Your assistant reads the page and hands it to ProtoServe for you.
Prefer a raw terminal upload, or publishing very large pages? See the slash command below.
Share and organize
Every dashboard card has a Share button — pick people by avatar, share with a group, or invite anyone by email; pages show up in recipients' “Shared with me” view, even before their first sign-in, and the notification bell in their header lets them know. Tags are generated automatically on publish; click any tag pill to filter your dashboard.
The same Share dialog has a Private toggle — flip it and only you and the people (or groups) the page is shared with can open it. Click the ★ on any card to collect it in your Favorites, and keep an eye on each card's view count. The Activity view in the sidebar is a searchable timeline of all of it — everything you've published and shared, and everything shared with you.
The /send-to-protoserve slash command
The MCP connection above is all most people ever need. But if you
live in Claude Code — or you're publishing a very large page — the /send-to-protoserve path/to/page.html
slash command uploads a local file's raw bytes straight to the API, without routing the whole document through your
assistant's context the way the MCP tool does. It's a plain markdown file in your commands directory — install it with one
curl, then mint a token on the API tokens page and save it where the command expects:
# install the command (any machine with Claude Code) mkdir -p ~/.claude/commands curl -o ~/.claude/commands/send-to-protoserve.md https://protoserve.com/send-to-protoserve.md # save your API token (create one at protoserve.com/tokens) mkdir -p ~/.config/protoserve echo "ps_YOUR_TOKEN" > ~/.config/protoserve/token chmod 600 ~/.config/protoserve/token
New Claude Code sessions pick it up automatically. Working in a shared repo?
Drop the same file into the repo's .claude/commands/ instead and every collaborator gets the command —
each still using their own token.
Ground rules
Self-contained pages only
One HTML file with all CSS/JS inlined — no external assets (they'd be blocked anyway). 10 MB max.
Unlisted by default, private on demand
Each slug ends in 16 random hex characters — nothing is indexed or enumerable, but anyone with the exact link can view. Marking a page private goes further: only you and the people it's shared with can open it.
Pages run sandboxed
Your scripts work, but cookies and localStorage are unavailable by design — artifacts can never act as a signed-in user.
Humans in the loop
Sign-in is open, but publishing waits for admin approval — the audience is always known.
Last updated July 30, 2026 · Curious what ProtoServe is all about? About ProtoServe