Ollav

app.ollavPublished by ollav.appOfficial publisherv1.1.0Updated Oct 29, 2026

Share HTML prototypes as live links; read element-pinned review comments; publish new versions.

VerifiedStreamable HTTPWeb executableProductivity & Workflow Developer Tools Communication & Collaboration

Server details

Identifier: app.ollav/ollav
Transport: Streamable HTTP
Runtime: Web executable
Trust: Verified
Published: Oct 29, 2026

Security note

MCP servers receive tool arguments from a conversation and may perform external actions. Review what a server can do before you enable it, and give it only the access it needs.

The registry verified that this server's namespace belongs to ollav.app, which also runs its endpoint. That identifies the publisher; it does not make the server's tools safe.

SourceWeft's checks cover whether the listing is complete and the endpoint answered; they do not review the server's code or what its tools do.

Add a badge to your README

Show readers this MCP server is listed on SourceWeft. The badge links to this page.

[![Listed on SourceWeft](https://sourceweft.com/badge/mcp/app.ollav%2Follav.svg)](https://sourceweft.com/mcp/app.ollav%2Follav?utm_source=readme&utm_medium=badge)

Overview

AI-generated overview

Ollav is a hosted MCP server that lets an assistant share HTML prototypes as live links, read element-pinned review comments, and publish new versions.

What you can do: Share and version HTML documents: publish a file as a commentable link, update it at the same URL, list and inspect documents with their version history
Read review feedback: fetch open threads as Markdown and JSON with a polling cursor, or pull every comment including resolved ones
Write review feedback: pin a comment to a specific element, reply, resolve or reopen threads, react with an emoji, delete comments
Export account data as a signed ZIP download link
When to use it: Useful when a team reviews HTML prototypes or pages and wants an agent to take part in the loop: share the page, collect pinned feedback, edit, and republish. Fits design and front-end review workflows where comments must stay attached to specific elements.
Requirements: Remote Streamable HTTP endpoint at app.ollav.app/mcp; nothing to run locally. Authentication is required: OAuth sign-in with workspace selection, or an API key sent as an Authorization bearer header (OLLAV_API_KEY in client configs). Keys are created in the Ollav account, with separate sandbox and live keys. Clients that only support local stdio servers need a bridge such as mcp-remote.

Before you install

The API key is a bearer credential granting access to the workspace's documents and comments; keep it in an environment variable rather than in shared config. Live keys act on real work, so prefer sandbox keys while testing. The assistant can publish new versions at existing URLs, add, resolve and delete comments, and generate a signed export link to all account data, so review changes before approving. Shared links and comments are visible to the people you send them to.

Installation

In SourceWeft

Open Ollav in the dashboard and add it to a workspace.
Connect the required credentials. They are stored privately and never shown on public pages.
Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/app.ollav%2Follav/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config. The client completes OAuth sign-in on first connect.

{
  "mcpServers": {
    "ollav": {
      "type": "http",
      "url": "https://app.ollav.app/mcp"
    }
  }
}

README

Ollav MCP

Ollav is where humans and AI agents review HTML together. Your agent shares a prototype as a live link, your team pins comments to the exact element they mean, and the agent reads those comments, fixes the page and publishes the next version at the same URL.

This repo holds Ollav's Claude Code plugin and MCP setup. The server itself is hosted: there is nothing to run.

Endpoint (Streamable HTTP): https://app.ollav.app/mcp
API keys: https://app.ollav.app/keys (ol_test_... for a sandbox, ol_live_... for real work)
Full docs: https://ollav.app/docs/mcp · Quickstart: https://ollav.app/docs/agents
MCP Registry: app.ollav/ollav

Claude Code

Install the plugin (the MCP server plus a skill that tells Claude when to use Ollav):

Set OLLAV_API_KEY in your environment first. Or add just the MCP server:

bash

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

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

Check it: claude mcp list shows ollav as connected.

Claude.ai and Claude Desktop

Settings → Connectors → Add custom connector. Name: Ollav, URL: https://app.ollav.app/mcp. Claude signs you in with OAuth and you pick the workspace it may use.

Cursor

~/.cursor/mcp.json (or .cursor/mcp.json in a project):

json

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

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

ChatGPT

Settings → Apps & Connectors → Create (developer mode). Name: Ollav, MCP server URL: https://app.ollav.app/mcp, Authentication: OAuth. Attach an HTML file and say "share this on Ollav".

OpenAI Codex CLI

Or in ~/.codex/config.toml:

Any other MCP client

Point it at https://app.ollav.app/mcp and send Authorization: Bearer <key>. Clients that only run local stdio servers can bridge with npx -y mcp-remote https://app.ollav.app/mcp --header "Authorization: Bearer $OLLAV_API_KEY".

Tools

Tool	What it does
`share_html`	Publish an HTML file and get a link people can comment on
`publish_new_version`	Update something already shared: same URL, comments kept
`list_documents`	Find documents shared earlier
`get_document`	Metadata, share URL and version history
`get_review`	Open feedback threads as Markdown + JSON, with a polling cursor
`get_comments`	Every comment, resolved ones too
`add_comment`	Pin a comment to an element, or reply
`resolve_comment`	Mark a thread done (or reopen it)
`react_to_comment`	Acknowledge a comment with an emoji
`delete_comment`	Delete a comment and its replies
`export_data`	Signed link to a ZIP of your data

The loop

share_html → people comment → get_review → edit → publish_new_version → resolve_comment.

License

MIT. This repo holds configuration only; use of the hosted service is covered by Ollav's terms at https://ollav.app.

Source: README.md at commit bb560f3

Tools

This server asks you to sign in, so SourceWeft could not read its tools without an account and has not indexed them. What a connected account sees can depend on that account and its permissions.

Version history

v1.1.0LatestOct 29, 2026

Score

85% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

Reached in the last 30 daysRequired25 pts
Auth declaredRequired10 pts
Tools listed15 pts
Answer tools/list without a credential, or ship a package that starts in a sandbox without one.
DescriptionRequired15 pts
Logo10 pts
Documentation15 pts
License10 pts