{
  "markdown": "# SendPage MCP server\n\nPublish an HTML document as a shareable link the recipient can open in one tap —\nwithout leaving the conversation that wrote it.\n\n**Endpoint:** `https://sendpageapp.com/mcp` · **Transport:** Streamable HTTP\n(stateless) · **Auth:** bearer API key, free, no signup\n\n---\n\n## Why\n\nAn HTML file is a set of drawing instructions, not a document. Sent as an\nattachment it arrives as raw source, gets stripped by corporate mail filters as a\nknown phishing vector, or simply will not open on a phone — which is where most\npeople read first. Printing to PDF loses interactive charts and quietly cuts the\nright-hand columns off wide tables, which is the failure worth fearing: nobody\nnotices until a client asks about a figure that is not in the document.\n\nA link avoids all of it. The recipient taps once and reads the page as designed,\non whatever device they have.\n\n## Connect it\n\nGenerate a free key at **https://sendpageapp.com/docs/mcp**, then:\n\n```bash\nclaude mcp add --transport http sendpage https://sendpageapp.com/mcp \\\n  --header \"Authorization: Bearer sp_live_...\"\n```\n\nOr by hand, in `.mcp.json`:\n\n```json\n{\n  \"mcpServers\": {\n    \"sendpage\": {\n      \"type\": \"http\",\n      \"url\": \"https://sendpageapp.com/mcp\",\n      \"headers\": { \"Authorization\": \"Bearer sp_live_...\" }\n    }\n  }\n}\n```\n\n## Tools\n\n| Tool | What it does |\n|---|---|\n| `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. |\n| `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. |\n| `list_documents` | Documents published with this key, with links and view counts. |\n\n### The missing-image warning\n\nAI tools emit a page *plus* an `images/` folder, and people paste only the HTML —\nso the images 404 and every reader sees broken icons. `publish_document` returns\nthe offending files **by name**, so they can be inlined as data URIs and the\ndocument updated before the link is handed over. This is the single most common\nway a published page is quietly wrong.\n\n## The Skill\n\n[`skills/sendpage/SKILL.md`](skills/sendpage/SKILL.md) teaches Claude when to\noffer a link, how to repair a document whose images would not load, and to update\nan existing document rather than publish a second one.\n\n```bash\nmkdir -p ~/.claude/skills/sendpage\ncurl -o ~/.claude/skills/sendpage/SKILL.md \\\n  https://sendpageapp.com/skills/sendpage/SKILL.md\n```\n\n## Limits\n\n- **Free: 5 documents a month**, each with a small \"Made with SendPage\" footer.\n  Pro removes both.\n- **2 MB per document**, inlined images included.\n- **Links are unlisted, not secret.** Anyone with the URL can read the document,\n  and `robots.txt` keeps them out of search results. Password protection exists\n  for anything confidential, and it gates the exports and the preview thumbnail\n  too — not just the page.\n- The API key is stored only as a hash. It is shown once when generated and\n  cannot be recovered; if you lose it, revoke it and generate another.\n\n## Notes on the transport\n\nStateless Streamable HTTP: a single `POST` returns one JSON body, and `GET`\nanswers `405` to decline the optional server-initiated SSE stream. Sessions are\nnever created, so any instance can serve any request — which is what makes the\nserver hostable on a serverless runtime, where a long-lived SSE connection would\nbe killed by the execution limit rather than by anything the client did.\n\nWithout a key the endpoint answers **401 with a `WWW-Authenticate` header** —\nthat is a missing credential, not a broken server.\n\n## Issues\n\nThis repository holds the connection metadata and the Skill. For problems with\nthe server itself, open an issue here.\n\n---\n\n## Use it in DeepSeek Harness (dsh)\n\nThis repo is also a DeepSeek Harness **bundle** — install it and SendPage's tools\nmount straight into dsh, with no manual MCP config:\n\n```sh\ndsh plugin --profile web add https://github.com/jcaiagent7143-ui/sendpage-mcp\n```\n\nThen set your free key (get one at https://sendpageapp.com/docs/mcp) so publishing\nand exporting work — in the environment, or in `$DSH_HOME/.credentials.yaml`:\n\n```yaml\nSENDPAGE_API_KEY: <your key>\n```\n\nThe tools appear under the `sendpage` namespace — `mcp__sendpage__publish_document`,\n`mcp__sendpage__export_document` (png/pdf/docx), and the rest. Prefer to wire the raw\nendpoint yourself? It's `https://sendpageapp.com/mcp` (Streamable HTTP).\n",
  "bytes": 4498,
  "sha": "5f40452fbbc73b719c88426ae24942cd44ef3495605343eba8d35b286cb2a178",
  "repo_slug": "jcaiagent7143-ui/sendpage-mcp",
  "fonte": "repo",
  "truncated": false,
  "api": "https://agentalog.com/api/listings/mcp_com_sendpageapp_sendpage_97cf0b06/readme"
}