API Tools
postagent.sh
Provides API endpoints for postal mail generation, including document creation, template management, quoting, and checkout.
ENDPOINT 1
https://api.postagent.sh/mcp
MCP server metadata
- Name
- PostAgent
- Version
- 0.5.0
Before the first PostAgent action in a session, call check_postagent_updates or read postagent://agent-manifest. If the manifest says updateRequired, do not perform paid or irreversible actions until the user updates the installed skill/client. Use this server to print and mail physical letters and postcards, to verify postal addresses, and (KYC-verified payers only) to run bulk campaigns. LETTERS — choosing the upload tool depends on PERSONALIZATION, not recipient count: if the content is final and identical for everyone (even when mailing the same letter to many recipients), use create_letter; if the content varies per recipient through {{fields}} placeholders (mail merge), use create_template and supply each recipient's values on create_mail_quote. Each physical letter is its own quote + payment + job: to mail N recipients, run the quote/pay cycle N times against the same documentId. Proof of mailing/delivery: set options.extraService to certified, certified_return_receipt, or registered on create_mail_quote. POSTCARDS — upload front and back artwork with create_postcard_art (single-page pdf/png/jpeg, correct trim+bleed), then create_postcard_quote; 4x6 postcards may go to international recipients. ADDRESS VERIFICATION — verify_address is a standalone ~2¢ paid check; quotes already verify both addresses for free, so only use it when no mail is being sent. CAMPAIGNS — create_campaign_quote bulk-sends one creative to up to 500 recipients but is KYC-walled: it returns kyc_required (403) until the paying wallet is verified. Onboarding is operator-run — request access at https://interpretai.tech/contact (also in the 403's details.contactUrl) to get enabled; until then, fall back to per-recipient create_mail_quote. Always quote first, present the price, recipient, sender, selected-route `design` constraints, and preview to the user, and only pay after the user explicitly confirms. Service level (`economy`/`standard`/`express`) and `extraService` (certified/registered/etc.) are SOFT preferences: if no available provider can honor them for this destination, the router downgrades or drops them and surfaces a `fulfillment.warnings` array on the quote response (codes `service_level_downgraded`, `extra_service_unavailable`). ALWAYS inspect `fulfillment.warnings` before paying and disclose any warnings to the user as part of the confirmation prompt — silently mailing a letter without requested certification or at a slower service level is a contract failure. Each quote advertises ranked `paymentOptions`: prefer x402 (USDC on Base) for autonomous payment, then MPP fiat (call pay_mail_with_shared_payment_token with a Shared Payment Token) if available; if the payer is a human with only a credit card, call create_card_checkout for a hosted Stripe link. If the customer has NO payment method yet, do not stop at checkout — read the postagent://payment-methods resource, which lists every rail with examples and step-by-step setup (how to get an x402 wallet or mint a Shared Payment Token). The quote price is final and inclusive — do not expect or surface a cost breakdown.
Known tools 14
create_templateUpload a REUSABLE template containing `{{field}}` placeholders (e.
Potential side effectscreate_mail_quoteVerifies the recipient and sender US addresses and locks a 15-minute USDC price for a documentId.
Inferred read-onlycreate_card_checkoutCreates a Stripe-hosted Checkout page for a locked quote and returns a `checkoutUrl` plus a `statusUrl`.
Inferred read-onlypay_mail_with_shared_payment_tokenAutonomous, no-browser FIAT payment for a locked quote using a Stripe Shared Payment Token (SPT / Machine Payments Protocol).
Potential side effectsprepare_mail_paymentReturns the x402 PAYMENT-REQUIRED challenge for a locked quote so an x402-capable wallet client can sign it.
Potential side effectssubmit_paid_mail_jobDetached-signature fallback for x402 wallets that can emit a standalone PAYMENT-SIGNATURE header.
Potential side effectsget_mail_job_statusReturns normalized status, carrier/tracking/proof data, and tracking events for a previously created job.
Inferred read-onlycreate_postcard_artUpload ONE side of a postcard (front or back) as single-page PDF, PNG, or JPEG artwork.
Potential side effectscreate_postcard_quoteVerifies the recipient and sender addresses and locks a 15-minute USDC price for mailing a postcard built from two postcard_art documents (front + back, uploaded via create_postcard_art).
Inferred read-onlycreate_campaign_quoteQuote ONE bulk send to MANY recipients (up to 500): a single template or static document, fulfilled through PostAgent's campaign workflow.
Potential side effectsget_campaign_statusReturns a campaign's validation/sending progress: status (validating | sent | partial | failed), recipient counts (total / validated / failed), and a failures report URL when some recipients could not be validated.
Inferred read-onlyCONNECT WITH APPROVAL
Client installation
Review this server and its permissions before adding it. Secret placeholders must be set locally.
Codex
~/.codex/config.toml
[mcp_servers.postagent]
url = "https://api.postagent.sh/mcp"
enabled = true
Claude Code
.mcp.json
{
"mcpServers": {
"postagent": {
"type": "http",
"url": "https://api.postagent.sh/mcp"
}
}
}
Claude Desktop
Settings → Connectors → Add custom connector
Name: postagent
Remote MCP URL: https://api.postagent.sh/mcp
Add this remote URL as a custom connector in Claude Desktop. Availability depends on the user plan and workspace policy.
Cursor
.cursor/mcp.json
{
"mcpServers": {
"postagent": {
"url": "https://api.postagent.sh/mcp"
}
}
}
Visual Studio Code
.vscode/mcp.json
Add to Visual Studio Code{
"servers": {
"postagent": {
"type": "http",
"url": "https://api.postagent.sh/mcp"
}
}
}
Generic MCP
Client-specific MCP configuration
{
"name": "postagent",
"transport": "streamable-http",
"url": "https://api.postagent.sh/mcp"
}
MCP Inspector
Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.
TRUST AND VERIFICATION EVIDENCE
Loading Trust v2 evidence…
Checking the associated registrable domain. The BuiltWith key remains server-side.
Evidence is source-attributed and does not guarantee that a third-party server is safe. Risk labels are conservative metadata heuristics.