DocuPost

@DocuPost send a letter to our client Jane Smith at 456 Oak Avenue, Portland OR 97204 with the signed contract PDF we just finalized

Letter queued for mailing. Recipient: Jane Smith, 456 Oak Avenue, Portland OR 97204. Sender: [your configured return address]. Document: signed_contract_final.pdf (3 pages). Estimated delivery: 3-5 business days via USPS First Class. Tracking ID: DCP-2847291. You'll receive a confirmation email once the letter enters the mail stream.

This example shows the core letter-sending workflow. Before running this, confirm you have a valid PDF URL or base64-encoded document ready, and that your DocuPost account has sufficient postage credits. The MCP does not validate recipient addresses beyond basic formatting—incorrect addresses will still consume credits.

@DocuPost send holiday postcards to our top 12 customers using the design at https://cdn.example.com/holiday-2024.png with a thank-you message on the back

Postcard batch initiated for 12 recipients. Front design: holiday-2024.png (verified, 1800×1200px). Back message: custom thank-you text (under 500 characters). All recipient addresses validated against your CRM list. Estimated cost: $18.00 (12 postcards × $1.50 each). Delivery window: 5-7 business days. Batch ID: DCP-PC-9182. You can track individual postcards in your DocuPost dashboard.

Postcard sending requires both a front image URL and either back text or a back image URL. This example assumes you've already uploaded the design to a publicly accessible CDN. DocuPost enforces image dimension and file size limits (check their docs). Rate limit: 100 postcards per hour on standard plans.

@DocuPost review our last 30 days of sent mail and summarize which customer segments received the most physical correspondence, then draft a postcard campaign for the under-communicated group

DocuPost MCP does not currently expose a 'list sent mail' or analytics tool—this example cannot be fulfilled as written. The MCP provides only send_letter and send_postcard actions. To analyze past mailings, you would need to query DocuPost's REST API directly or export data from their dashboard. For campaign planning, you can use the AI to draft messaging and recipient lists, then execute sends via @DocuPost once the list is finalized.

This example intentionally highlights a limitation: the MCP is write-only (send actions), with no read/reporting tools. If your workflow requires tracking or analytics, you'll need to integrate DocuPost's API separately or rely on their web dashboard. Always verify recipient lists externally before bulk sends—mistakes are costly and irreversible once mailed.

When DocuPost beats email for unsigned contract reminders

A 6-person sales team closes 40-60 deals a month, but 15% of contracts stall because prospects ignore DocuSign emails. The team uses Switchy to draft a physical letter reminder—personalized with the deal context—and sends it via DocuPost's send_letter tool. The physical mail gets opened within 3 days, and signature rates jump 22%. This works because the MCP needs only an API key and a PDF; no complex auth flow. The trade-off: each letter costs $1.50-$2.00, so reserve it for deals over $5k where the close is worth the postage. If you're chasing 200+ unsigned contracts monthly, the per-unit cost adds up fast and you're better off with a dedicated mail automation platform.

How a 3-person support team automates handwritten-feel postcards

A small SaaS support team wants to send thank-you postcards to customers who renew annual plans, but manually addressing 80 cards a quarter is a time sink. They connect DocuPost to Switchy, pull the customer list from their CRM via another MCP, and batch-send postcards with the send_postcard tool. Each card uses a templated front design (hosted image URL) and a short thank-you message on the back. The entire workflow takes 20 minutes instead of 4 hours. The catch: you need pre-designed image assets and a clean address list. If your CRM data is messy or you want dynamic postcard layouts per customer segment, you'll spend more time wrangling inputs than the MCP saves. Best for teams with stable design templates and structured customer data.

When DocuPost is the only option for legal mail requirements

A 10-person fintech compliance team must send physical notices to customers when accounts are flagged for review—email doesn't meet their state's legal delivery standard. They use Switchy to generate the notice PDF from a template, verify the recipient address against their database, and trigger DocuPost's send_letter tool. The MCP handles the mailing in one API call, and the team logs the send timestamp for audit trails. This scenario has no trade-off: if your industry requires certified or trackable physical mail, DocuPost (or a competitor) is non-negotiable. The MCP's simplicity—just two tools, no OAuth dance—makes it faster than logging into a vendor portal. If you're sending fewer than 10 notices a month, the per-letter cost is negligible; above 500, negotiate volume pricing directly with DocuPost.