Use Ollav from your agent via MCP

Connect your agent once and it can share an HTML page as a live link, read the comments people pin to it and publish the fix at the same link. This takes about five minutes with a test key, so nothing touches your team's live documents or your plan.

1. Get a test key

Open https://app.ollav.app/keys, choose Test, keep the scopes upload, read and comment, and create the key. It is shown once.

export OLLAV_API_KEY=ol_test_...

A test key works in your own sandbox: documents carry a TEST mark and are deleted after 30 days, there are no plan limits, and it may make 60 tool calls a minute.

2. Connect your client

Claude Code

claude mcp add --transport http ollav https://app.ollav.app/mcp --header "Authorization: Bearer $OLLAV_API_KEY"
claude mcp list

ollav shows as connected. Or install the plugin, which adds a skill telling Claude when to use Ollav: /plugin marketplace add ollav-app/ollav, then /plugin install ollav@ollav.

Cursor

~/.cursor/mcp.json:

{
  "mcpServers": {
    "ollav": {
      "url": "https://app.ollav.app/mcp",
      "headers": { "Authorization": "Bearer ${env:OLLAV_API_KEY}" }
    }
  }
}

Restart Cursor from the shell where OLLAV_API_KEY is set. Settings → MCP shows ollav with a green dot.

ChatGPT

ChatGPT connects with OAuth, which gives it a live key. To try test mode first, create the app with the key in the URL:

Settings → Apps & Connectors → Create (developer mode)
Name:            Ollav
MCP server URL:  https://app.ollav.app/mcp/ol_test_YOUR_KEY
Authentication:  No authentication

That URL contains the key, so treat it like a password. When you're ready to share with your team, recreate the app with https://app.ollav.app/mcp and OAuth.

Claude.ai, Claude Desktop, Codex, VS Code and other clients: see Connect your client.

3. Share something

Ask your agent:

Make a one-page pricing mockup in HTML and share it on Ollav.

It calls share_html and gives you a link like https://content.ollav.app/p/qkjgjQCQGz. Open it: the page has a TEST mark, and you can click any element to pin a comment. Leave one, say on the main button: "Make this say Start free trial".

A coding agent with a shell uploads a file on disk with curl instead of passing the HTML through the model, which costs no tokens. The share_html description tells it how.

4. Have it act on the review

Read the review comments on that page and fix them.

The agent calls get_review (the open threads as Markdown and JSON, each with the element's text so it can find it in the source), edits the page, calls publish_new_version with the same slug (same link, comments kept) and resolve_comment on the thread, often replying with add_comment to say what changed. Reload the link to see the new version.

That's the loop: share, review, publish a new version, resolve.

5. Check it, or fix it

To confirm the key and endpoint outside the client:

curl -s https://app.ollav.app/mcp \
  -H "Authorization: Bearer $OLLAV_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"jsonrpc":"2.0","id":1,"method":"tools/list"}'

You get 11 tools. If the client reports an error, every Ollav error carries a code, a hint the agent can follow and a doc_url. The common ones:

Everything else: Troubleshooting MCP.

Next

• Switch the client to a live key (ol_live_...), or OAuth, to share with your team.
• Every tool, its inputs, outputs and errors: the MCP docs.
• No MCP? Publish your first prototype with curl.