Publishing a document
You can publish to 00doc in three ways. Pick the one that matches your workflow.
Dashboard upload
Claude + MCP
Cursor + MCP
Open a document
Go to the dashboard, create a new document or open an existing one. Drop your file
Drag an .html file onto the upload zone, or use the file picker.
Confirm
The preview updates and the share link reflects the new version.
Connect MCP with endpoint https://00doc-mcp.workers.dev/mcp, then ask in natural language:
“Publish this as an HTML report titled ‘Weekly KPIs’ to 00doc”
Claude calls publish_document with title, html, and optional note. You get back document_id, version_id, and the share URL. Add the same MCP URL in Cursor settings, then prompt from the AI chat:
“Generate a one-page HTML spec for the billing API and publish it to 00doc”
Cursor invokes publish_document the same way Claude does. HTML quality
- Prefer valid, complete documents (
<!DOCTYPE html>, semantic structure). The sanitizer strips risky markup; broken or empty pages are hard for readers and agents to use.
- Inline CSS or linked stylesheets you control work best for predictable rendering in the preview and on
/d/[token].
- Test locally in a browser before upload if you use heavy scripts — the public view runs in a sandboxed iframe with a tightened CSP.
Titles matter. Use a specific title (“Q3 renewal — Contoso”) instead of “Document 2”. It shows in the dashboard, in history, and when agents fetch metadata.
Prompts for AI-generated HTML
Give the model:
- Audience (executive, engineer, customer)
- Structure (sections, tables, callouts)
- Output format: “Return a single HTML file with embedded CSS”
Then ask it to publish via 00doc so you do not paste multi-kilobyte HTML manually.
