For AI assistants

Let your assistant publish it.

Your AI already wrote the page. Connect Vela Drop over MCP and it can publish that page, hand you the link, and watch who opens it — without you leaving the conversation.

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. Your assistant saves that link and passes it back on later calls — so it is the credential, and no second login would add anything. Treat the edit link like a password: anything holding it can change or delete that page.

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:

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

Confirm it connected 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. Vela Drop appears in the tools menu, and you can ask Claude to publish any HTML file it has written.

Custom connectors are available on paid Claude plans.

Cowork uses the same connector list as Claude Desktop, so adding it once covers both.

Open Settings → Connectors.
Click Add custom connector, name it Vela Drop, and paste https://veladrop.com/mcp.
Save, with the authentication fields left empty.
In a Cowork session, ask for the page and then for it to be published. The file it built in the workspace goes straight up.

Cowork is the natural fit here: it already has the file on disk, so it uploads it directly rather than re-typing it into a tool call.

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 curl -T pricing.html create_link · cfo create_link · procurement

Done — it's live. Two tracked links:

…veladrop.app/cfo and …veladrop.app/procurement

I've saved your dashboard link. Ask me any time who has opened it. Want me to claim it with your email so you can find it again if we lose this conversation?

You

Yes. And check back tomorrow.

Claude

claim_drop get_analytics

Claimed. As of now: the CFO link has 4 opens from 2 visitors, last opened 20 minutes ago from the UK on desktop. Procurement hasn't opened theirs yet.

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

The tools

Ten 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 tracked link with a tag, up to 20 per page
list_links	Every tracked link with its own statistics
get_analytics	Opens, unique visitors, countries, devices, referrers
set_title	Sets the browser tab title
claim_drop	Attaches your email so the page can be found again later
list_drops	Every live page for an email — how an assistant recovers links it has lost
delete_drop	Deletes everything, immediately and permanently

delete_drop is marked destructive, so a well-behaved client will ask you before running it.

Two things worth knowing

The file doesn't go through the conversation

create_drop hands back a short-lived upload URL and your assistant pushes the file straight to us — a plain curl -T. Nothing large is retyped into a tool call, so a big page costs you no context and never hits a message size limit. Assistants without shell access can still create pages and manage links; they just need you to do the upload step.

Pages don't change

Ask for an edit and your assistant publishes a new page with new links. That's deliberate — a link you already emailed will never change under your recipient. The old page stays live until someone deletes it, so tell your assistant which one you're actually sending.

Or just drag a file in.

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

Drop a file How it works