PieterPost remote MCP server
Send letters and postcards through chat.
Connect PieterPost to a compatible MCP client. Draft a message, choose a saved Mailbook contact, create a secure checkout link, and let PieterPost print, stamp, and mail it after you review the details.
See the MCP flow in action
This walkthrough shows one compatible MCP client. The same PieterPost server URL and OAuth approval flow work across clients that support remote MCP.
Connect PieterPost to your assistant
Paste this public remote MCP endpoint into ChatGPT, Claude, or another compatible client:
https://pieterpost.com/mcp/setup/Popular AI workspaces use different names for connectors and MCP. Look for remote MCP or custom connector support; availability can vary by plan and product.
ChatGPTOpenAI
ClaudeAnthropic
GeminiGoogle
PerplexityPerplexity
GrokxAI
CopilotMicrosoft
MistralMistral AI
QwenAlibaba Cloud
CohereCohere
DeepSeekDeepSeek
Meta AIMeta
ChatGPT
Add PieterPost as a remote MCP connector so ChatGPT can draft mail, create review links, and call PieterPost tools after you authorize OAuth.
OpenAI MCP docs- 1Open ChatGPT settings and go to Apps & Connectors.
- 2Create or add a custom connector, name it PieterPost, and paste the MCP server URL.
- 3Choose OAuth when prompted, scan the available tools, then authorize your PieterPost account.
- 4Start a chat with PieterPost enabled and ask for a letter, postcard, checkout link, or order update.
Claude
Use PieterPost as a custom connector in Claude surfaces that support remote MCP servers and OAuth authorization.
Claude connector docs- 1Open Claude and go to Customize > Connectors.
- 2Click the plus button, then choose Add custom connector.
- 3Name it PieterPost and paste the MCP server URL.
- 4Click Add, then Connect, and approve PieterPost when the browser opens.
- 5Ask Claude to prepare a letter or postcard, then review the PieterPost link before paying.
Other MCP clients
Use the same remote MCP endpoint from any client that supports streamable HTTP transport and OAuth-based authorization.
MCP authorization docs- 1Create a remote MCP server connection in your client.
- 2Set the server URL to the PieterPost MCP endpoint.
- 3Let the client discover the OAuth metadata and complete the PieterPost authorization flow.
- 4Use the listed tools for drafts, contacts, checkout links, wallet status, and order lookup.
Once PieterPost appears in your connector list, connect it to start the PieterPost OAuth approval flow. The client may show the tools before asking you to approve account access.
What PieterPost adds to chat
MCP gives your assistant a controlled set of PieterPost tools. It is useful when the idea, recipient details, review link, and order status all belong in the same conversation.
Prepare mail
Turn a prompt, note, or pasted draft into a clean letter or postcard and open it in PieterPost for review.
Use Mailbook contacts
Use saved contacts and address requests from your PieterPost Mailbook after you authorize the connector.
Create checkout links
Create secure checkout links so the sender can review the message, recipient, price, and postage before paying.
Track and manage
Check wallet balance, quote an order, find order status, or create top-up links for API-credit workflows.
A simple sending workflow
PieterPost keeps the conversational work in your assistant and the final approval in PieterPost, so every letter or postcard can be checked before it is mailed.
Draft
Ask your assistant to write a birthday note, thank-you letter, customer follow-up, invite, or postcard message.
Choose recipient
Pick a saved Mailbook contact or provide a postal address in the conversation.
Review
Open the PieterPost review link and check the exact copy, address, format, and image before checkout.
Send
Pay securely in PieterPost or use approved API credits for explicit direct-send workflows.
Safety and permissions
PieterPost uses OAuth, so your MCP client asks you to connect your PieterPost account before it can use account-specific tools. Checkout links keep review and payment in PieterPost. Direct API-credit sends require the right OAuth scope and a clear confirmation before they run.