Rich Doc

Install

Install Rich Doc for agents.

Use the CLI when your agent is working locally with files. Add the hosted MCP server when your agent lives inside ChatGPT, Claude, Cursor, or another client that supports remote tools.

CLI install downloads.richdoc.app/cli/install.sh
MCP server https://richdoc.app/mcp
Authentication Your Rich Doc account
Best for File-first publishing and review workflows

The CLI and MCP server are complementary. Use the CLI for local terminal workflows, and add MCP when your cloud or desktop chat client needs an authenticated Rich Doc tool surface.

Install the CLI

The CLI is the fastest path when your agent can read and write files on your machine. It publishes HTML files, exports editable copies, uploads revisions, and checks for newer CLI releases.

Terminal setup
curl -fsSL https://downloads.richdoc.app/cli/install.sh | sh
rich-doc --version
rich-doc auth login
File workflow
rich-doc publish ./report.html --title "Q2 Report"
rich-doc editable export doc_... -o editable.html
rich-doc editable publish doc_... ./editable.html

The downloaded CLI defaults to https://richdoc.app. Use --origin only for local development or another explicit Rich Doc origin.

Connect an MCP Client

MCP is the right path when the agent runs inside a cloud or desktop chat client and needs to call Rich Doc directly from that environment.

  1. Open the MCP, connectors, or tools settings in your AI client.
  2. Add a new remote MCP server.
  3. Paste https://richdoc.app/mcp as the server URL.
  4. Follow the sign-in prompt and approve Rich Doc access.
  5. Ask your client to publish, review, or revise an HTML document in Rich Doc.

Client labels vary, but the Rich Doc setup stays the same: use the hosted server URL above and complete the Rich Doc sign-in flow when prompted.

Client Docs

Use these docs when you need MCP client-specific instructions. The only Rich Doc value to copy is the server URL: https://richdoc.app/mcp.

What Agents Can Do

  • Publish HTML files as Rich Doc documents with a shareable review link.
  • Bring images and other document assets along with the published work.
  • Read existing documents, comments, replies, and review status before making changes.
  • Revise a document while keeping comments anchored to the right parts of the page.
  • Update sharing access when a document is ready for collaborators.
Recommended workflow
New document: upload an HTML file -> get a Rich Doc review link

Revision: export an editable copy -> make changes in the HTML file
  -> upload the revised file -> Rich Doc keeps comments and history aligned

For best results, have your agent work with an HTML file instead of pasting an entire document into chat. Rich Doc uses the file upload flow to preserve large pages, assets, comments, and version history.