Native MCP endpoint — the agent-first surface

Send mail from Claude (MCP)

Claude can quote, send, and track real USPS letters through paperplane’s native MCP endpoint — add one URL to your MCP config and ask Claude to mail the letter; you approve a payment link and USPS does the rest.

Add connector in Claude

Open in Claude

From $0.99 · postage included · no account needed

MCP config (Claude Desktop / Claude Code)Example

{
  "mcpServers": {
    "mail": { "url": "https://sendpaperplane.com/api/mcp" }
  }
}

paperplane · Claude & MCP

Mail this deliverable to the client, certified.

Here’s the draft. I’ll get a quote before anything is sent.

Total, postage included$12.99

Sandbox free · holds 30 minApprove to send

Nothing prints until you approve. Order ord_8k2d.

Instead of a hand-rolled Lob call

A mail API wants an account, an API key, a funded balance and a PDF you rendered yourself before the first request. The MCP endpoint takes plain text, quotes it, and hands your human a payment link.

How it works

Set up Claude & MCP in three steps.

Native MCP endpoint — the agent-first surface

Step 01
Add the MCP server
Drop the snippet below into Claude Desktop, Claude Code, or any MCP-compatible client.
Step 02
Ask Claude to send it
It calls quote_letter for the exact price, then send_letter.
Step 03
Approve and track
Approve the paperplane payment link (or use a prepaid credit code), then track screening → printing → mailed → delivered.

Copy the config.

MCP config (Claude Desktop / Claude Code)

{
  "mcpServers": {
    "mail": { "url": "https://sendpaperplane.com/api/mcp" }
  }
}

Try it in the sandbox (free, nothing mailed)

“Send a test letter to 1 Main St, Richmond VA in sandbox mode and show me the quote.”

Under the hood

MCP isn’t a bridge to the product — it is the product. The endpoint at /api/mcp exposes four tools (quote_letter, send_letter, get_letter_status, buy_credits) over the same engine as the website, plus a free sandbox. An agent with its own wallet can pre-fund sends with buy_credits.

Supported action fields

Every integration maps into the same fixed set of fields, the ones the REST API and MCP tools take directly.

Field	What it does
mail_class	first_class, certified, certified_err (Certified with electronic Return Receipt), or priority
text or pdf_url	the letter body as plain text, or a fetchable PDF to print as-is
to	recipient name + street/city/state/zip, verified against USPS data
from	return address, printed on the envelope and used for undeliverable mail
email	where the receipt and status updates go — no account required

Or skip the automation tool: ask Claude or ChatGPT

Every integration here sits on the same MCP endpoint agents use directly. Instead of wiring a trigger to an action, ask Claude or ChatGPT to draft and mail the letter. Same mailing tools (quote_letter, send_letter, get_letter_status), same price, same free sandbox.

Send mail from Claude Send mail from ChatGPT

Send your first letter from Claude & MCP.

Sandbox runs the whole pipeline for free and mails nothing. Live sends start at $0.99, one all-in price.

Send a letter

{
  "mcpServers": {
    "mail": { "url": "https://sendpaperplane.com/api/mcp" }
  }
}

Common questions

Can Claude pay for the letter by itself?

Not with a card: a human approves the paperplane payment link first. With a prepaid credit code, or credits an agent bought with buy_credits, sending is hands-off.

Which Claude surfaces support this?

Anything that speaks MCP: Claude Desktop, Claude Code, and other MCP-compatible clients. The endpoint uses streamable HTTP, so no local process is needed.

Is it safe to let an assistant send mail?

A human approves every live payment, screening checks every letter before printing, and sandbox mode exists so agents can test end-to-end for free.