StampSend
Sign in Start free

Page01 · 00:40 A key

Everything you can do in the app, your agent can do too.

Same library, same analytics, same permissions. Make a key, paste it into the client you already use, and ask. Free plan included; nothing here costs extra.

  1. Sign up, or sign in.
  2. Open Settings, API keys. Name the key, pick its scopes, create it. The secret is shown once.
  3. Pass it as Authorization: Bearer ac_send_... to the API and the MCP server.
read
See what you can see: your library, a document, its analytics, its link.
write
Change what you own: title, settings, visibility, the invited list, a new version, delete.
send
Create new share links: documents, spaces, request links.
admin
Everything above, plus the team: members, invites, billing, branding.
Make a key Connect an agent

Page02 · 01:10 MCP

One server, five tools, your permissions.

https://api.stampsend.com/mcp, Streamable HTTP, stateless, Bearer token. Manifest at https://api.stampsend.com/.well-known/mcp.json. Call tools/list first; the server's own names are authoritative.

  • list_documents The caller's library: their own documents and their team's, most recent first.
  • get_document One document with its link, settings and view stats.
  • get_document_analytics Who opened a document, which pages, for how long. Owner or team admin only.
  • get_document_last_open The most recent open: when, and the viewer's email on a team plan when they gave it. Null when nobody has opened it. On the free plan the email is always null. Owner or team admin only.
  • create_document_link The public link for an existing document, on the web origin. Uploading a file is done through the web app or the REST API.
  • set_document_visibility One of public, signedIn, team, invited, private. "private" means just you, not your team's admins. Needs the write scope.
  • set_document_note Plain text, up to 280 characters, shown above the document to every viewer who gets past the gate. Changes the live link; null or empty removes it. Needs the write scope.

Claude Code

claude mcp add --transport http send https://api.stampsend.com/mcp --header "Authorization: Bearer ac_send_YOUR_KEY"

Claude Desktop claude_desktop_config.json

{
  "mcpServers": {
    "send": {
      "command": "npx",
      "args": [
        "-y",
        "mcp-remote",
        "https://api.stampsend.com/mcp",
        "--header",
        "Authorization: Bearer ac_send_YOUR_KEY"
      ]
    }
  }
}

Cursor .cursor/mcp.json

{
  "mcpServers": {
    "send": {
      "url": "https://api.stampsend.com/mcp",
      "headers": {
        "Authorization": "Bearer ac_send_YOUR_KEY"
      }
    }
  }
}

ChatGPT and other clients: add a remote MCP server at the address above with a Bearer token.

Page03 · 00:55 REST API

The API describes itself.

Interactive docs, generated from the running server, and the OpenAPI document behind them. Base path /v1. Errors are { error: { code, message, details? } }. Uploading a file is three calls: create the document, PUT the bytes to the URL it returns, complete it. 

curl -s https://api.stampsend.com/v1/documents \
  -H "Authorization: Bearer ac_send_YOUR_KEY"

Page04 · 00:25 For agents

What an agent reads first.

Four files, generated from the same constants as this site, so they cannot say a different price.

  • llms.txt The product in one page, for a model: what it is, prices, promises, where the surface is.
  • llms-full.txt The long version: positioning, pricing, promises, how to get a key, every tool, client snippets.
  • agents.md How an agent gets a key, what it can do, limits, and what is never exposed.
  • .well-known/mcp.json The MCP manifest: server URL, auth, tools. The API serves the same document.