Sendpage

com.sendpageappPublished by sendpageapp.comOfficial publisherv1.0.0Updated Oct 24, 2026

Publish an HTML document as a link anyone can open in one tap, plus PDF, image and Word export.

VerifiedStreamable HTTPWeb executableProductivity & WorkflowFiles & Storage

Overview

AI-generated overview

Publishes an HTML document as a one-tap shareable link, with PDF, image and Word export, so an assistant can hand over a readable page instead of a file.

What you can do
  • Publish an HTML document and get back a share link, document id and edit token, plus a warning naming images that would fail to load
  • Replace a document's contents or title while keeping the same link
  • List documents published with the key, with links and view counts
  • Export a published document as PDF, PNG or DOCX
When to use it
Useful when an assistant has produced an HTML report, dashboard or interactive page and the recipient should open it on any device without attachments, raw source or print-to-PDF column loss. Also handy for correcting a published page after sending, since the link stays the same.
Requirements
Remote Streamable HTTP endpoint at sendpageapp.com; no local runtime. A bearer API key in the Authorization header, generated free without signup. Network access to the service.
Before you install
The API key is shown once and stored only as a hash; if lost, revoke and generate another. Links are unlisted, not secret: anyone with the URL can read the document, so password protection is needed for confidential content. Free tier allows 5 documents a month with a footer, and documents are capped at 2 MB including inlined images. Publishing and updating write data to a third-party service.

Installation

In SourceWeft

  1. Open Sendpage in the dashboard and add it to a workspace.
  2. Connect Authorization token credentials. They are stored privately and never shown on public pages.
  3. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/com.sendpageapp%2Fsendpage/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config.

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

README

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:

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

Or by hand, in .mcp.json:

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

Tools

ToolWhat it does
publish_documentHTML 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_documentReplace the contents or title. The link does not change, so a typo found after sending costs a correction rather than a second URL.
list_documentsDocuments 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. publish_document returns the offending files by name, 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.

The Skill

skills/sendpage/SKILL.md teaches Claude when to offer a link, how to repair a document whose images would not load, and to update an existing document rather than publish a second one.

bash
mkdir -p ~/.claude/skills/sendpagecurl -o ~/.claude/skills/sendpage/SKILL.md \  https://sendpageapp.com/skills/sendpage/SKILL.md

Limits

  • Free: 5 documents a month, each with a small "Made with SendPage" footer. Pro removes both.
  • 2 MB per document, inlined images included.
  • Links are unlisted, not secret. Anyone with the URL can read the document, and robots.txt keeps them out of search results. Password protection exists for anything confidential, and it gates the exports and the preview thumbnail too — not just the page.
  • The API key is stored only as a hash. It is shown once when generated and cannot be recovered; if you lose it, revoke it and generate another.

Notes on the transport

Stateless Streamable HTTP: a single POST returns one JSON body, and GET answers 405 to decline the optional server-initiated SSE stream. Sessions are never created, so any instance can serve any request — which is what makes the server hostable on a serverless runtime, where a long-lived SSE connection would be killed by the execution limit rather than by anything the client did.

Without a key the endpoint answers 401 with a WWW-Authenticate header — that is a missing credential, not a broken server.

Issues

This repository holds the connection metadata and the Skill. For problems with the server itself, open an issue here.

Use it in DeepSeek Harness (dsh)

This repo is also a DeepSeek Harness bundle — install it and SendPage's tools mount straight into dsh, with no manual MCP config:

sh
dsh plugin --profile web add https://github.com/jcaiagent7143-ui/sendpage-mcp

Then set your free key (get one at https://sendpageapp.com/docs/mcp) so publishing and exporting work — in the environment, or in $DSH_HOME/.credentials.yaml:

yaml
SENDPAGE_API_KEY: <your key>

The tools appear under the sendpage namespace — mcp__sendpage__publish_document, mcp__sendpage__export_document (png/pdf/docx), and the rest. Prefer to wire the raw endpoint yourself? It's https://sendpageapp.com/mcp (Streamable HTTP).

Source: README.md at commit 32a6e68

Tools

0
This server asks for a credential such as an API key, so SourceWeft could not read its tools without one and has not indexed them.

Version history

1
  1. v1.0.0LatestSep 16, 2026

Score

50% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declaredRequired10 pts
  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts

    Declare a license in the repository or the registry entry.