What DirectMailAmerica does
DirectMailAmerica exposes mailing operations through the Model Context Protocol. Agents can retrieve the product catalog, upload print-ready artwork for live quotes, preview rendered documents, and release an approved quote for mailing. Supported products include one-piece First-Class letters, Certified Mail pieces, Express postcards, and full-color postcards, with product and artwork requirements determined by the catalog.
The service also supports email-to-mail automation. A workspace can receive email, apply ordered rules, format matching messages as letters or postcards, and hold them for approval or send them under previously authorized recurring-mailing consent. Letterhead presets, email history, generated previews, mailing rules, budgets, and usage are managed through MCP tools.
How it works
Start with a no-cost catalog or pricing lookup, then create a product-specific quote when artwork and recipients are ready. Product quotes accept a print-ready PDF and 1–100 US recipients, upload the artwork for live pricing, and remain valid for 36 hours. The returned quote includes an exact expiration time. Two-sided postcards can use supplied reverse text or reverse artwork, subject to the catalog’s dimensions and file limits.
Before sending, review the PDF, sender, recipients, print settings, and total. Sending requires the saved quote ID, confirmed:true, the matching approved total, and an idempotency key. Retrying the same quote and key is designed to avoid duplicate mailing. Changes require a new quote and fresh approval.
Email workflows use a workspace inbox and ordered matching rules. Rules can match exact senders, recipients, and subject text, and can specify addresses, formatting, letterhead, page limits, color, approval behavior, and budgets. Manual inbox processing checks both letter and postcard services, while scheduled processing follows the same matching, consent, budget, and duplicate protections.
Setup and configuration
Workspace access uses OAuth or a DirectMailAmerica workspace Bearer key, depending on the operation. Public catalog, standard pricing, connection-status, and account-link tools do not require authentication; mailing, workspace data, credits, and most previews do. Browser sign-in by itself does not authorize the MCP connection.
Production and staging behave differently. Staging prevents mail from being sent, but some actions can still spend real money, including certain credit purchases. Use the separate simulation endpoint for no-cost mailing tests. Production credentials are required for operations such as sending, creating an email inbox, saving or editing letterheads, changing email settings, and deleting email data.
Fund a workspace with prepaid credits through Square hosted checkout or x402 USDC on Base or Solana. The credit tools operate on workspace balances; mailing tools can spend those credits when the approved request is released.
Tools and capabilities
- Inspect connection state, workspace access, OAuth scopes, tool permissions, and environment.
- Browse products, retrieve fixed pricing, create 36-hour artwork-based quotes, and send approved quotes.
- Preview letterheads, email-derived letters, and mailing-rule output as embedded PDF resources.
- Save, version, archive, restore, download, and reuse letterhead presets.
- List jobs, inspect letter status, and retrieve owned email, PDF, EML, and ZIP resources.
- Create and manage email inboxes, matching rules, budgets, approval settings, and manual processing.
- Read balances, purchase credits, create Square checkout links, and reconcile completed payments.
Limitations and notes
Mailing is limited to US recipients, and quotes must satisfy the selected product’s artwork and dimension requirements. Combined artwork for product quotes is limited to 25 MiB; letterhead PDFs are limited to one unlocked, unrotated US Letter page and 4 MB. Email downloads support up to 50 messages and 20 MB of documents.
Sending is deliberately approval-bound. Any change to approved content, recipients, options, or total requires a new quote. Email autosend requires explicit human consent for recurring mailings; it must not be inferred. Inbox processing has a 60-second per-workspace cooldown and processes up to ten emails per inbox per run.
Staging does not mail, but it is not a universal no-cost environment. For test runs that must not charge or send, use the dedicated simulation endpoint. Status reads do not refresh mailing status automatically, and uncertain submissions should be reconciled rather than resubmitted.