Get feedback on what you build in Cursor
You built a prototype in Cursor and now need other people to look at it. Ollav turns the HTML file into a link where reviewers pin comments to the exact element, and Cursor can read those comments, fix them and publish the next version to the same link.
Who this is for
You use Cursor to produce HTML: a landing page, an internal tool mock, an email preview, a single-file app. You want feedback from teammates or clients without setting up a deploy or collecting notes in a chat thread.
How the loop works
1. Connect once
Create an API key at https://app.ollav.app/keys and make it available to Cursor as OLLAV_API_KEY. Then add Ollav to ~/.cursor/mcp.json (or .cursor/mcp.json in a project):
{
"mcpServers": {
"ollav": {
"url": "https://app.ollav.app/mcp",
"headers": { "Authorization": "Bearer ${env:OLLAV_API_KEY}" }
}
}
}Cursor reads OLLAV_API_KEY from the environment it was started in, so restart Cursor from that shell. Settings → MCP should show ollav with a green dot.
2. Publish
Ask Cursor: "Publish prototype.html to Ollav and give me the link." You get a link to the uploaded file (one self-contained HTML file, up to 15 MB). Nothing is deployed. The document is private to your workspace by default and not indexed.
3. Review
Reviewers sign in, click the element they mean and pin a comment, or react with an emoji. Members and invited guests can comment, and guests are free.
4. Close the loop
Ask Cursor: "Read the review, reply to each comment, apply the fixes, resolve the threads and publish a new version." The link stays the same and the earlier comments are kept, so you can run as many rounds as you like.
For prompts and the full tool list, see the Cursor guide, the agent feedback loop and the MCP docs. After you sign up, a short first-run checklist helps you get connected.
When something else fits better
- You only need the file online. A static host such as Netlify Drop or GitHub Pages is quicker and has no review features. See Ollav vs. static hosting.
- You're building a multi-file app. Ollav hosts one self-contained file with no server code. Deploy the app, then use a feedback tool on the deployed site such as BugHerd.
- Reviewers can't sign in. Ollav reviewers sign in so every comment has a name on it. For comments with no account at all, look at dot..
- You review designs, not code. If the artifact is a Figma file, stay in Figma. See Figma comments for code prototypes.
FAQ
How do I set up Ollav in Cursor?
Create an API key at https://app.ollav.app/keys, expose it as OLLAV_API_KEY, and add the ollav entry to mcp.json shown above. Restart Cursor from the shell that has the variable set, then check Settings → MCP for a green dot.
What can Cursor do with the comments?
Read open comments as Markdown, reply to them, resolve threads and publish a new version at the same link. The same actions are available over the REST API.
Do reviewers need Cursor or an Ollav account?
They don't need Cursor. They do sign in to Ollav to comment, as workspace members or invited guests. Guests are free.
Does the link change with each version?
No. Every version is at the same link and earlier comments are kept.
Does Ollav run my project?
No. It hosts one self-contained HTML file and serves it as a page. Inline your CSS, JavaScript and images, or load them from absolute https:// URLs. Relative asset paths and server-side code aren't supported.
What does it cost?
There is a Free tier and you don't need a card to start. Pro is EUR 12 a month and Team is EUR 10 per seat a month with a minimum of 3 seats, both excluding VAT. See the pricing page.
Try it
Sign up on the Free tier, no card needed, and have Cursor publish its next page.