Work with documents through your AI
Outprint turns substantial AI output into structured documents you can read, review, edit, compare, and share without passing files back and forth.
Start trial → Connect your AI → Ask it to create → Review and share
Connect once
Start the 14-day trial, then add Outprint as an MCP connection in the AI tool you already use.
Connection details and the machine-readable contract unlock when your trial starts.
Create a document
Ask your AI to create the artifact you need: a research brief, project plan, design document, decision memo, status report, data report, or a general structured document. Outprint validates outprint.document.v1 and renders it with first-party code. Callers cannot provide HTML, CSS, JavaScript, or renderer assets.
Your document appears in Documents.
Review and improve
Open the document to read, comment, and edit in one surface. Select text to leave a review comment; writers and owners save versions, ask their own AI to publish a next version, and make any retained version current for readers. AI-authored updates are listed in History; only the current version is reader-visible until an owner or writer makes another version current.
Technical reference
Share with explicit roles
Invite a collaborator as Viewer, Commenter, or Writer. Owner authority is never delegated. Revocation and role changes take effect on the next request.
| Access | Reader |
|---|---|
| private | The owner and authorized team members only. |
| link | Active named collaborators who sign in with the invited email. |
The focused MCP surface
The connector exposes exactly fifteen document tools:
Use get_document_catalog for the pinned catalog and complete recipe scaffolds. Use publish_document once for initial creation. After creation, update_document creates a History snapshot that becomes the working tip. Use add_document_comment to create a review-thread root (Commenter+). MCP does not post comment replies; reply, resolve, re-anchor, and delete stay in the trusted browser workspace. Browser-only commands also handle manual saves, lifecycle changes, restore, access settings, and terminal deletion.
Every reader URL is permanent, access-controlled, and served with noindex. Paused subscriptions preserve documents and return 402 until billing is restored.