◈OpenTree DashboardSign in

$ asciinema play

The whole thing, in about ninety seconds

No video to watch — every step below is a command you can run right now, in order, and each one shows what it should print. That is a better demo than a screen recording, because you end up with a live link instead of a memory of one.

Second 0 — publish with no account

$ echo '<h1>Hello</h1>' > index.html
$ curl -X POST https://read.botook.ai/v1/publish -F file=@index.html
{"url":"https://read.botook.ai/p/pEwH6mEsX29bjAVLSmRYDj/","expires_in_hours":24,"claim":"…"}

Open the link. That is a live private page, and it took one command.

Second 15 — install the server

npx -y opentree-mcp

Or register it over HTTP in whichever client you already use:

claude mcp add --transport http opentree https://read.botook.ai/mcp \
  --header "Authorization: Bearer otr_live_YOUR_KEY"

Second 30 — publish from the terminal agent

Ask the session for a page and then for a link. It calls the tool itself:

publish_html({ content: "<h1>Q3 review</h1>…", expires_in_hours: 168 })

Second 45 — put a gate on it

set_password({ site_id: "…", password: "hunter2" })
set_email_gate({ site_id: "…", allowed_email_domain: "client.com" })

The reader now meets a passcode field, or a one-time email confirmation, before any content is served.

curl -X PUT https://read.botook.ai/sites/SITE_ID \
  -H "Authorization: Bearer otr_live_YOUR_KEY" -F file=@index.html

Same URL, new content. Whoever you sent it to sees the current version without being told.

Second 75 — see whether anyone read it

curl https://read.botook.ai/sites/SITE_ID/engagement \
  -H "Authorization: Bearer otr_live_YOUR_KEY"

Opens, unique viewers, how far people scrolled, whether anyone reached the end.

Second 90 — put your own domain in front

curl -X POST https://read.botook.ai/custom-domains \
  -H "Authorization: Bearer otr_live_YOUR_KEY" \
  -H "content-type: application/json" \
  -d '{"hostname":"share.example.com","site_id":"SITE_ID"}'

Add the CNAME and TXT it returns, verify, and the page answers on your hostname.

Without a terminal at all

Paste HTML into the box at the bottom of the home page and press publish. Same endpoint, same result, no install.

In the dashboard

The dashboard does all of the above with buttons: publish, set a passcode, change expiry, mint and revoke keys, add domains, read feedback, watch the activity feed.

What a viewer experiences

  1. They click a link.
  2. They pass whatever gate you set — often nothing at all.
  3. They read the page, and can react or comment if you enabled the toolbar.

No account, no install, no download. On any browser, including a phone.

Try it against your own deployment

Every command above works unchanged against a self-hosted install — swap the origin. Setting one up is four commands.

The docs for the full surface, integrations for your client, use cases for what people publish.

Keep reading