Introduction

1. Agents drop their work over MCP: a plan in Markdown, an HTML report, or a small static app made of files.
2. Every drop starts private. Only its owner, and the workspace's editors and admins, can open it.
3. People review it full screen. Select text or click a spot in an image to comment. The owner shares a link that can view, comment, or edit.
4. The agent reads the open comments and drops the next version. Older doc versions stay in history. Apps keep only their latest file set.

1. Sign in at drop.vitehub.dev with GitHub. Anyone with a GitHub account can.

2. Add Drop's MCP server to your agent. With Claude Code:

   claude mcp add --transport http --scope user drop https://drop.vitehub.dev/mcp

   The first time it connects, the client opens Drop in your browser. Allow it, and the agent acts as you. Connect an agent has the setup for Codex, Cursor, VS Code, and other clients.

3. Ask your agent to drop a plan, for example "Write a plan for the billing migration and drop it for review." It answers with the review link.

A drop is something an agent, or you, published for review:

• A doc: Markdown, or a self-contained HTML page. Markdown renders with tables, task lists, callouts, and Mermaid diagrams. HTML runs as-is, scripts included, in a sandbox.
• An app: a folder of static files with an index.html, like a prototype or a dashboard.
• A file you upload: an image, a PDF, a log.

Every drop opens full screen and has its own link. Docs keep earlier versions; publishing an app replaces its files and deletes the old files. Review and share covers comments, sharing, and versions.

On instances with quotas enabled, Free includes 3 drops, 100 MiB of storage, and 1,000 file writes per calendar month. An app can contain up to 50 files and 2 MiB. Pro includes 100 drops, 1 GiB, and 10,000 writes per month, with apps up to 200 files and 4 MiB. Operators can configure Pro limits.

A drop is one doc, app, or uploaded file with its version chain. Every retained document version and app file counts toward storage. A document version uses one write; an app publish uses one per file. Temporary code images use one write and no drop slot; their bytes count until cleanup deletes them. The owner's plan applies even when someone else edits.

At a limit, your existing drops and shared links keep working. Revisions are allowed while storage and writes remain available. Deleting a drop frees its slot and storage, but does not refund monthly writes. Monthly budgets reset at the start of each UTC calendar month. Publishing also has a short burst limit.

Upgrade or deploy your own. Self-hosted instances have owner quotas off by default.

Everyone who signs in joins as a Member. The GitHub accounts a Drop's owner lists as admins join as Admin, and admins change roles on the Members page.

drop.vitehub.dev is one Drop anyone can use. Drop is open source and built on ViteHub, so you can run your own on Cloudflare, Vercel, Netlify, Deno Deploy, or a server of yours. Host it yourself compares them.