Use paperplane in Dust

Dust workspaces can attach remote MCP servers as first-class tools, and paperplane’s endpoint is public and keyless — so giving your Dust agents the ability to mail real letters is a two-minute admin task. To frame it honestly: this is user-side setup. paperplane has no native listing in Dust’s tool catalog yet; you are adding our standard MCP server — the same endpoint every MCP-speaking client uses — through Dust’s bring-your-own-server flow.

Connect it (workspace admin)

• In Dust, go to Spaces → Tools and click Add Tool, then Add MCP Server.
• Enter the server URL: https://sendpaperplane.com/api/mcp.
• Authentication: none needed — the server supports anonymous access, so skip the OAuth and bearer-token options.
• Let Dust sync; the tool appears with paperplane’s three tools.
• Assign the tool to the space(s) whose agents should be able to mail letters, then enable it on the agents themselves in their configuration.

What the agent gets

• quote_letter — free, read-only. Itemized pricing (First-Class $1.99, Certified $12.99, Certified + electronic Return Receipt $14.99, Priority $24.99). Given the real recipient and content, it also mints a single-use confirmation_token bound to that exact letter and price.
• send_letter — the one write tool: real money, real paper, irreversible once printed. It requires the token and rejects any send that drifted from the quote. Live sends return a Stripe payment link (or draw on a prepaid credit code); sandbox: true runs the whole pipeline free with nothing mailed.
• get_letter_status — read-only tracking: screening → printing → mailed → delivered.

Sandbox-first walkthrough

After assigning the tool to an agent, test in a conversation with it:

"Quote a one-page certified letter to Maria Alvarez, 1 Main St,
Richmond VA 23220 with the text 'Dust integration test.' Show me the
quote, then send it in sandbox mode and give me the order id."

Expected behavior: the agent calls quote_letter and shows a $12.99 quote with a confirmation_token, then calls send_letter with the identical letter plus sandbox: true, returning a completed ord_test_… order. Address verification, content screening, simulated printing, and tracking all ran; nothing was printed, mailed, or charged. Once the behavior looks right, real sends are the same call without sandbox — a human approves the payment link, or a prepaid credit code makes it hands-off.

Where this fits

Dust agents typically sit on company knowledge and workflows — which is exactly where physical mail shows up as a last mile: a support agent escalating a billing dispute to a certified letter, an ops agent mailing contract termination notices, an assistant that turns a CRM record into a posted welcome note. For flows that would rather call HTTP directly, the same backend is REST (POST /v1/quotes, POST /v1/orders, GET /v1/orders/:id) — see the developer docs. The confirmation-token contract is documented in how AI agents mail letters via MCP and runs live in the no-signup demo.