Pieter Post
Never lick a stamp again
117 followers
Never lick a stamp again
117 followers
Never lick a stamp again! Tired of stamps, envelopes, and post office trips? Pieter Post makes sending mail as easy as sending a text.
This is the 2nd launch from Pieter Post. View more
PieterPost MCP
Launching today
PieterPost MCP connects AI agents to postal mail. From ChatGPT, Claude, Codex, Claude Code, or any MCP client, agents can prepare letters and postcards, use Mailbook contacts, upload attachments or postcard images, create checkout links, and track orders. It brings PieterPost online mail, API, and payment-link workflows into agent tools.
Free
Launch Team
Pieter Post
Physical mail as an MCP tool is a fun edge because it's one of the few agent actions that's genuinely irreversible once it's in the postbox. What's the confirm boundary here: does a human have to click through the checkout link, or can an agent with a saved payment method quote-and-send in one shot? For a tool that spends money on a physical artifact I'd want the resolved address read back and a hard human gate, since a hallucinated recipient isn't a retry, it's a stranger opening my letter.
Pieter Post
@dipankar_sarkar Exactly. That boundary is the core design. The normal flow is quote, review the final text and resolved address, create a checkout link, then mail after payment. No silent send unless someone has set up a trusted direct-send path with explicit limits. What would you want on the approval screen before it goes physical?
Connecting AI agents to physical mail is a genuinely underexplored
space. The irreversibility angle is the interesting design challenge
here — curious if you're adding a confirmation step before anything
actually ships, since a hallucinated address isn't a retry, it's a
stranger's mailbox.
Would love to see a "draft mode" where agents prepare everything but
a human approves before it goes physical.
Pieter Post
@l_build Yes, draft mode is the default shape we want people to use first. Let the agent prepare the recipient, message, assets, and quote, then a human approves before anything gets paid or mailed. Where would you use that kind of flow first?
ModuleX
Letting an agent create a checkout link before anything mails is a clever gate, but I'm curious what the agent actually sees back after it uploads a postcard image. Does it get any confirmation of how the final print looks, or is it flying blind on the physical artifact once payment clears?
Pieter Post
@sezerufukyavuz Great question. The agent can prepare the upload, message, recipient, and checkout. The person still reviews before payment and mailing, so it should not be flying blind. For postcards, we want the preview to show the image, recipient, price, and final send step clearly. What would you want confirmed before trusting it?
Tooling Studio
Love it! 😍 How are you thinking about pricing the MCP side? Is it just pay per letter/postcard sent, or will there also be something like a monthly/API plan if people start wiring this into their own tools? Mostly asking because this feels like something I’d try once manually, then immediately want to automate if it works.
Pieter Post
@nick_kramer Yep, MCP is free. You only pay for the letters or postcards you actually send. We wanted it to feel like normal PieterPost: try one, review it, send it, and if it fits your workflow you can keep using it without a separate MCP subscription. What would you automate first?
How does Pieter Post actually handle the physical delivery part, do you print and mail things on my behalf or is there some kind of kiosk pickup I need to visit nearby?
Pieter Post
@meryemvfjh We print, stamp, and mail it for you. No kiosk and no post office trip needed. You write it online or through the API/MCP flow, review it, pay, and PieterPost handles the physical part. What would you send first?
Two things for me. First, the fully resolved postal address read back verbatim, plus which Mailbook entry it matched, since 'John in London' quietly resolving to the wrong saved contact is the failure I'd never catch. Second, an idempotency key on the send, so if the agent's tool call times out and retries I get one postcard and not two. Duplicate physical sends are the money version of a double-submit.