MCP — one config block in Cursor

Send mail from Cursor

Cursor’s agent can send real USPS mail: add paperplane’s MCP endpoint to Cursor’s MCP settings and the agent gains quote_letter, send_letter, and get_letter_status — from $0.99, free sandbox.

Add to Cursor

From $0.99 · postage included · no account needed

.cursor/mcp.jsonExample

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

paperplane · Cursor

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 writing a mail integration

Wiring a mail provider means an SDK, a key in .env, a PDF renderer and a test account before anything ships. One config block gives the Cursor agent four tools, and sandbox mode runs in CI for free.

How it works

Set up Cursor in three steps.

MCP — one config block in Cursor

Step 01
Add the MCP server
Open Cursor Settings → MCP and add a server, or drop the snippet into .cursor/mcp.json.
Step 02
Ask the agent to send
e.g. “mail this deliverable summary to the client, certified.”
Step 03
Approve and track
Approve the paperplane payment link, or set a prepaid credit code. Use sandbox mode in CI — free, nothing printed.

Copy the config.

.cursor/mcp.json

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

Or call REST directly from your code

curl -X POST https://sendpaperplane.com/v1/orders \
  -H 'Content-Type: application/json' \
  -d '{
    "mail_class": "first_class",
    "sandbox": true,
    "text": "Dear Ms. Alvarez, ...",
    "to":   { "name": "Maria Alvarez", "line1": "1 Main St",
              "city": "Richmond", "state": "VA", "zip": "23220" },
    "from": { "name": "Alex Rivera", "line1": "12 Grove Ave",
              "city": "Richmond", "state": "VA", "zip": "23221" },
    "email": "alex@example.com"
  }'

Under the hood

Cursor speaks standard MCP, so nothing Cursor-specific is needed — improvements (buy_credits for agent-funded sends, richer status) land in the shared endpoint and show up here automatically.

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 Cursor.

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

Why would a code editor send physical mail?

Because agents do more than code: invoicing a client, mailing a contract, sending a certified notice from a workflow you are building. If your agent runs in Cursor, the capability is one config block away.

Does this need an API key or account?

No — the endpoint is open. Sandbox is free; live orders carry their own payment via a paperplane payment link or prepaid credit code.

Can I use this in scripts instead of the agent?

Yes — the REST API (POST /v1/orders) is the same surface. The curl on this page is a complete working example.