PieterPost MCP

Product Introduction

1. Definition: The PieterPost MCP (Model Context Protocol) server is a remote, OAuth-secured connector that integrates the PieterPost physical mail API directly into AI agent workflows. It is a technical bridge that allows Large Language Models (LLMs) and AI assistants to programmatically interact with postal mail services.
2. Core Value Proposition: It exists to automate and streamline the creation and sending of physical letters and postcards from within conversational AI interfaces. Its primary value is bridging the digital conversation to physical mail delivery, enabling AI agents to draft, address, price, and initiate the mailing process without leaving the chat environment.

Main Features

1. AI-Powered Mail Drafting: The MCP server provides tools that allow an AI agent (like ChatGPT or Claude) to format a user's prompt or pasted text into a clean, print-ready letter or postcard draft. This involves structuring the content, applying proper formatting for physical print, and preparing it for the PieterPost rendering engine.
2. Mailbook Contact Integration: After OAuth authorization, the MCP tools can access the user's saved PieterPost Mailbook contacts. The agent can list, search for, and select recipients by name, pulling accurate, pre-verified postal addresses directly into the mailing workflow, eliminating manual data entry errors.
3. Secure Checkout Link Generation: A core safety feature. Instead of sending mail directly, the MCP server generates a unique, secure PieterPost review link. This link opens a PieterPost page where the human user can see the exact draft, recipient address, postage cost, and any uploaded images for final visual approval and payment, keeping financial transactions outside the AI's scope.
4. Order Management & Wallet Tools: The server provides read-and-write tools for order lifecycle management. This includes checking the user's PieterPost API credit wallet balance, generating top-up links for credit purchases, fetching real-time order status updates (like "printed" or "mailed"), and obtaining price quotes for a draft before finalization.

Problems Solved

1. Pain Point: The friction and context switching between having an idea in a chat conversation and executing it as a physical mail piece. Manually copying text, finding addresses, logging into a separate mail service, and reformatting content is time-consuming.
2. Target Audience: Busy Professionals & Executives who use AI assistants for drafting communications; Marketing and Sales Teams running personalized, automated outreach campaigns; Developers and Tinkerers building AI agents that require physical world interaction; Individuals managing reminders, invitations, or personal correspondence through AI.
3. Use Cases: An AI assistant drafting and initiating a personalized thank-you letter to a client after a meeting; automatically sending a postcard for a contact's birthday based on a calendar reminder; a customer support bot generating and mailing a formal follow-up letter with terms; an agent mailing a physical invite drafted during an event planning conversation.

Unique Advantages

1. Differentiation: Unlike standalone mailing websites or basic APIs, PieterPost MCP is natively embedded within the AI agent's toolset. It doesn't require a separate dashboard or complex API integration by the end-user. Compared to other mailing services, its specific focus on the MCP standard makes it uniquely plug-and-play for the growing ecosystem of MCP-compatible AI clients.
2. Key Innovation: The implementation of the Model Context Protocol (MCP) with OAuth 2.0 authorization for a physical mail service. This technical approach provides a standardized, secure, and discoverable way for any compliant AI client to safely access a controlled set of mail-sending tools, with human-in-the-loop approval (via checkout links) as a default safety mechanism.

Frequently Asked Questions (FAQ)

1. Is PieterPost MCP secure for sending sensitive mail? Yes, PieterPost MCP employs OAuth for secure account access and is designed with a safety-first workflow. It generates review and checkout links, ensuring a human must visually confirm all details and complete payment in the secure PieterPost environment before any mail is physically produced.
2. What AI assistants or clients are compatible with PieterPost MCP? It is compatible with any client that supports remote MCP servers and OAuth, including ChatGPT (via custom connectors), Claude (in surfaces with custom connector support), and other MCP clients like Cline or Windsurf. Compatibility depends on the client's specific feature availability.
3. Can PieterPost MCP send mail automatically without my approval? No, by default, the standard workflow requires you to click a generated checkout link and approve payment. Automatic sending is only possible if you explicitly use API credit tools and have pre-authorized that specific OAuth scope, and even then, it requires a clear programmatic confirmation.
4. How does PieterPost MCP handle recipient addresses? It integrates directly with your PieterPost Mailbook, allowing the AI to use your saved, verified contacts. You can also provide a new address in the chat, which the agent will format and include in the draft for your review on the checkout link.
5. What is the difference between using PieterPost MCP and the PieterPost API directly? The PieterPost MCP server is a pre-built, standardized adapter for the PieterPost API designed specifically for AI agents. It simplifies integration, manages OAuth flows, and exposes a curated set of tools within the chat interface, whereas the direct API requires developer-level integration for each application.