Send

Turn a Claude conversation into a hosted HTML page on a public send.co link, then edit it in place.

Opens Agent Studio, where connecting is one click. The connector URL below works in any MCP client.

Paste it into any MCP client. Setup docs

What the Send connector does

The Send MCP server turns a Claude conversation into a hosted web page. The agent writes a complete HTML document, Send publishes it at a shareable send.co link, and Send then tracks who opened it and for how long. Sign-in is OAuth. Send is a publishing tool, not a mail or messaging tool — the name misleads.

Verified connector

Listed by Anthropic as a partner connector in its Connectors Directory.

Connection checked by Agentman on .

Anthropic states this reflects the level of review a connector received, not a security audit.

Send tools (4)

  • CreateDocument
  • EditDocument

Tool names from Anthropic's directory listing. This server requires sign-in, so we could not read tool descriptions or parameter schemas.

Limits

  • No delete, expire or disable tool exists. Nothing the agent publishes can be taken down by the agent. That is a dashboard action.
  • No gating parameter exists. No documented tool accepts a password, expiry date, or allow-list. Everything the agent publishes is link-public at creation.
  • EditDocument is destructive to the previous version. It overwrites in place with no version argument and no companion tool to revert.
  • No application scopes. Four of five advertised scopes are OpenID identity claims and a refresh token. The fifth, claudeai, is undocumented. Nothing at the OAuth grant separates reading a document from publishing one.
  • We could not read tool schemas or safety annotations. The endpoint returned 401 to an anonymous request, so no parameter types or server-declared hints are published here.
  • Anthropic's directory listing is stale. It names 2 of the 4 tools Send documents.
  • HTML must be fully self-contained. Send's docs require zero external dependencies — no CDN scripts, no external stylesheets, no remote images. Images must come through manage_images and be referenced as asset:{fileId}, never base64-inlined.
  • Send's own pages disagree on price. Its llms-full.txt lists Solo at 30 dollars, Pro at 60 and Business at 180 per month; its pricing page, retrieved the same day, shows Pro at 29 per user per month and Business at 149, with no Solo plan. We report the pricing page as current and flag the machine-readable file as out of date.
  • The changelog is placeholder content. send.co/changelog showed three generic entries dated "over 2 years ago" on 2026-08-22, so it cannot be used to date connector changes.
  • send.co/mcp/docs.md is not Markdown. Appending .md returns the HTML page with a 200 status rather than a machine-readable version, so the usual .md affordance does not work here.

Frequently asked questions

Is a document created by the Send MCP server public?

Yes, anyone holding the link can open it with no account and no sign-in. We fetched a Send share URL anonymously on 2026-08-22 and received the rendered page. Send's own pricing FAQ states viewers open the link in their browser and need no Send account. Publishing is the product, so treat CreateDocument as publishing to the open web.

How many tools does the Send MCP server have?

Send documents four; Anthropic's directory lists two. The directory names CreateDocument and EditDocument. Send's MCP documentation page also specifies GetDocument, which reads any document including ones other people shared, and manage_images, which browses your uploaded image library. The directory listing is stale by two tools, both of them reads.

Can the Send connector delete a document it created?

No tool in either list deletes anything. Send documents no delete, disable or expire tool, and Anthropic's directory names none. Removal happens in the Send dashboard, not through the agent. EditDocument overwrites a live document in place, so the shared link updates for everyone who already has it and the previous version is not recoverable through MCP.

What OAuth permissions does the Send MCP server request?

Five scopes, four of which grant nothing specific. Send's RFC 9728 descriptor advertised openid, profile, email, offline_access and claudeai on 2026-08-22. The first three are OpenID identity claims and offline_access is a refresh token. Only claudeai is application-specific, and it is undocumented, so no scope separates reading a document from publishing one.

Does the Send connector send anything to a third party?

Not by itself, but it creates the surface that does. The tools publish a page and return a link; Send transmits nothing onward at creation. Once someone opens that link, Send emails the owner a view notification and, on Pro and Business plans, posts a linkViewed webhook to a URL you configured in the dashboard. Both are account settings, not tool parameters.

What does Send track when someone opens a document?

Opens, dwell time, approximate location, device and per-page engagement. Send's pricing FAQ names those, and adds that name, email, phone or custom fields appear on the viewer's activity record when you require them. Its privacy policy lists viewer IP address among the data collected. Viewers see a lead-capture form only where you enabled one.

Can I password protect a document the agent creates?

Not on the Free plan and not through a tool. Send's pricing page places passcode protection, expiration control and allow or block lists on paid tiers, and no MCP tool accepts a password, expiry or gating parameter. A document published by the agent is therefore open to anyone with the link until you change its settings in the Send dashboard.

Do I need a paid Send plan to use the MCP connector?

No, the Free plan hosts documents. Send's pricing page gives Free hosting, lead capture and analytics, and states that free sites expire unless you upgrade. Pro at 29 dollars per user per month adds passcode protection, expiration control, custom domains and webhooks; Business at 149 dollars per month adds email verification, allow or block lists and NDA agreements.

Sources

Use it in an agent

Put Send to work.

Connect Send once and your agents call these tools on their own: on a schedule, in a workflow, with nobody at the keyboard.