SendPage MCP server

Publish an HTML document as a shareable link the recipient can open in one tap — without leaving the conversation that wrote it.

Endpoint: https://sendpageapp.com/mcp · Transport: Streamable HTTP (stateless) · Auth: bearer API key, free, no signup

---

Why

An HTML file is a set of drawing instructions, not a document. Sent as an attachment it arrives as raw source, gets stripped by corporate mail filters as a known phishing vector, or simply will not open on a phone — which is where most people read first. Printing to PDF loses interactive charts and quietly cuts the right-hand columns off wide tables, which is the failure worth fearing: nobody notices until a client asks about a figure that is not in the document.

A link avoids all of it. The recipient taps once and reads the page as designed, on whatever device they have.

Connect it

Generate a free key at https://sendpageapp.com/docs/mcp, then:

claude mcp add --transport http sendpage https://sendpageapp.com/mcp \
  --header "Authorization: Bearer sp_live_..."

Or by hand, in .mcp.json:

{
  "mcpServers": {
    "sendpage": {
      "type": "http",
      "url": "https://sendpageapp.com/mcp",
      "headers": { "Authorization": "Bearer sp_live_..." }
    }
  }
}

Tools

Tool	What it does
publish_document	HTML in, share link out. Returns the link, the document id and an edit token — plus a warning naming any images that would fail to load.
update_document	Replace the contents or title. The link does not change, so a typo found after sending costs a correction rather than a second URL.
list_documents	Documents published with this key, with links and view counts.

The missing-image warning

AI tools emit a page plus an images/ folder, and people paste only the HTML — so the images 404 and every reader sees broken icons. returns the offending files , so they can be inlined as data URIs and the document updated before the link is handed over. This is the single most common way a published page is quietly wrong.