Work with documents through your agent
Outprint turns substantial agent output into structured documents you can read, review, edit, version, and share without passing files back and forth.
Start trial → Set up an agent → Ask it to create → Review and share
Set up an agent
Start the 14-day trial, then set up an agent on your machine with the Outprint CLI. Developer MCP connection details follow for hosted tools and scripts.
Connection details unlock when your trial starts.
Create a document
Ask your agent to create the artifact you need: a research brief, project plan, design document, decision memo, status report, data report, or a general structured document. Your agent writes content, never code. Outprint validates every document and renders it with its own first-party renderer.
The document lands in your library, ready to open.
Review and improve
Open the document to read, comment, and edit in one place. Select text to comment on the exact sentence. Every save is kept in History with its change note. When your agent publishes an update it lands in History too — readers only ever see the version you have made current.
Share with named readers
Invite each reader by email as a Viewer, Commenter, or Writer. Everyone opens the same permanent link; only the people you name get in. Documents are never indexed by search engines. If your subscription lapses, documents pause — nothing is deleted, and the same links come back when you re-subscribe.
Work from inside the document
Install the Outprint CLI and your own model stays reachable from the document itself. Select a paragraph, choose Comment, then address one named agent with @ or Assign to Agent… on an existing thread — that agent replies in the thread and may save the next version to History.
Technical reference
Documents validate against outprint.document.v1. Callers cannot provide HTML, CSS, JavaScript, or renderer assets.
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 | Who can open it |
|---|---|
| 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 registers these document, library, and agent tools; discovery is filtered to what your account can do:
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 edit_document_scoped to replace one unique paragraph or section and keep the rest of the source. Use add_document_comment to create a review-thread root (Commenter+) and, optionally, address it to one named agent; use assign_document_comment_agent to address an existing open thread. Comment replies, re-anchoring, and comment deletion stay in the trusted browser workspace, along with manual saves, access-mode changes, and permanent deletion. Your agent can mark a thread addressed only as part of an update it publishes.
Every reader URL is permanent, access-controlled, and served with noindex. Paused subscriptions preserve documents and return 402 until billing is restored.
Start with your next document.
14-day trial. Card required. No charge until day 14.
Create your first document