protocontent

protocontent

Publish the HTML (and other files) your coding agent makes to a shareable, sandboxed URL — and watch a whole session's artifacts on one live page, from any device.

Your agent already writes files. protocontent is the same primitive — write a file — except it lands at a URL instead of in your repo. It's the home for everything an agent produces that isn't meant to be committed: plans, prototypes, dashboards, screenshots, generated images. HTML first (it's the richest format), content-agnostic by design.

Built because Thariq Shihipar's "The Unreasonable Effectiveness of HTML" nails generate HTML but leaves "upload it somewhere and share the link" as a manual gap. protocontent is that missing verb.

See it live

The design docs are hosted on protocontent itself (dogfooding):

• 📂 Session page: https://protocontent-plans-vd7.protocontent.app/
• 📐 Architecture plan
• 📋 Product spec
• 🗺️ Roadmap / next steps

How it works

• An npx protocontent stdio MCP bridge runs alongside your agent (laptop or cloud VM), reads a file/folder path, and uploads the bytes.
• A Cloudflare Worker stores it (R2 blobs + D1 metadata) and serves it on a per-session subdomain of the isolated content domain *.protocontent.app.
• A Durable Object pushes live updates over WebSocket, so the session page refreshes the moment the agent publishes.
• The control plane (api. / mcp.protocontent.com) is a separate registrable domain from content (*.protocontent.app) — so untrusted agent HTML can't touch your session or cookies.

Tools: publish_html, publish_folder, list, history, keep, unpublish.

Install (any MCP agent)

claude mcp add protocontent -- npx -y protocontent

…or add npx -y protocontent as a stdio MCP server in your agent's config. Zero config — it mints an anonymous project on first run and gives back a tappable link plus a live session URL.

Artifacts are ephemeral — published to a URL, not committed. The bridge keeps them out of git for you: on startup, if it's inside a git repo, it ensures .protocontent/ is in your .gitignore (idempotent; opt out with PROTOCONTENT_NO_GITIGNORE=1). Stage anything you publish under .protocontent/.

Use it in Claude Code (plugin)

For Claude Code, install the plugin — it bundles the MCP server plus a publishing-artifacts skill and a conservative Stop hook, so your agent publishes the right artifacts, shares the link on every publish, updates in place (same name → same URL), and ends with both the session-index and per-artifact links:

/plugin marketplace add jaronheard/protocontent
/plugin install protocontent@protocontent

The Stop hook is fail-open and nudges at most once per turn; disable it with PROTOCONTENT_DISABLE_STOP_HOOK=1. For non-Claude agents (Cursor, Codex, Aider, …), copy the snippet in AGENTS.md into your project.

Repo layout

protocontent/          Cloudflare Worker — src/, wrangler.jsonc, schema.sql
protocontent/bridge/   the npx stdio MCP bridge (published to npm as `protocontent`)
plugin/                Claude Code plugin — MCP + publishing-artifacts skill + Stop hook
AGENTS.md              portable "publish & share" snippet for non-Claude agents
*.html                 design docs (also live on protocontent.app)

Self-host / deploy

See protocontent/README.md. In short: a Cloudflare account + wrangler login, create the R2 bucket and D1 database, apply schema.sql, add a proxied wildcard DNS record, then wrangler deploy.

Status

Deployed on Cloudflare · bridge published to npm as protocontent · MIT licensed.

License

MIT © Jaron Heard