For AI assistants

Let your assistant publish it.

Vela Drop is an MCP server. Point your assistant at one URL and it can publish a page it has just written, tag it per recipient, and tell you who opened it.

The endpoint.

One URL. No API key, no OAuth, no account to create.

https://veladrop.com/mcp

Why there's nothing to sign in to. Each page's edit link is already an unguessable key that controls exactly one page and expires with it after 30 days. An account would add a second secret without protecting anything the first one doesn't.

Set it up.

Pick the app you use. Each takes about a minute.

Run this in your terminal:

claude mcp add --transport http veladrop https://veladrop.com/mcp

That registers it for the current project. To make it available in every project, add --scope user. Confirm with claude mcp list, then just ask: "publish this page with Vela Drop."

Open Settings → Connectors.
Click Add custom connector.
Name it Vela Drop and paste https://veladrop.com/mcp as the URL.
Save. Leave the authentication fields empty — there is nothing to enter.
Start a new chat and ask Claude to publish any HTML file it has written.

Vela Drop speaks standard MCP over Streamable HTTP, so any compliant client works. Most take a JSON block like this:

{
  "mcpServers": {
    "veladrop": {
      "type": "http",
      "url": "https://veladrop.com/mcp"
    }
  }
}

There is no headers block to fill in, because there is no authentication.

What it looks like.

You

Build me a one-page pricing summary for Acme and publish it. I need separate links for their CFO and their procurement team.

Claude

I've written the page. Publishing it now.

create_drop create_link create_link

Done — it's live. Two tagged links: …veladrop.app/cfo and …veladrop.app/procurement. I've saved your dashboard link — ask me any time who has opened it.

You

Yes. And check back tomorrow.

Claude

get_analytics

As of now: the CFO link has 4 opens from 2 people, last opened 20 minutes ago from the UK on desktop. One more open was a mail scanner, not a reader, so I've left it out. Procurement hasn't opened theirs yet.

Illustration of a typical exchange. Your assistant's wording will differ.

The tools.

Eleven of them. Your assistant picks what it needs — you shouldn't have to think about this list.

Tool

What it does

create_drop

Creates the page and returns the view link, the edit link, and a one-time upload URL

refresh_upload_url

Issues a new upload URL if the first expired before use

get_drop

Status, title, size, expiry, and headline numbers

create_link

Adds a tag, which is what makes that link work. One word, no slashes, up to 20 per page

list_links

Every tag with its own statistics

get_analytics

Opens split into people and machines, unique visitors, countries, devices, referrers

tracking_guide

How to make a page report what happens inside it. Read before writing anything with navigation

set_title

Sets the browser tab title

claim_drop

Attaches your email, after you confirm it, so the page can be found again later

list_drops

Which pages an address has claimed. Never the edit links — those are emailed to the owner

delete_drop

Deletes everything, immediately and permanently

Or just drag a file in.

The MCP server and the drop zone create exactly the same thing.

Drop a file