# PieterPost MCP [Health: Active]

**Category:** 📦 Delivery  
**Repository:** https://github.com/pieterpost-com/pieterpost-mcp  
**GitHub Stars:** 0  
**Views:** 2  
**Installs:** 0  
**Upvotes:** 0  
**Directory Page:** https://allmcps.com/mcp/pieterpost-mcp

## Description
Let AI agents prepare, review, pay for, and send real letters and postcards.

## Claude Desktop Quick Installation
Remote MCP endpoint (confidence: high). Install path detected from listing signals. Add as a URL/SSE server in your client:

```json
"mcpServers": {
  "pieterpost-mcp": {
    "url": "https://pieterpost.com/mcp/"
  }
}
```

## Documentation

## What PieterPost MCP does

PieterPost MCP gives AI assistants access to PieterPost’s physical-mail service. An agent can prepare letters, postcards, and printed greeting cards, request pricing, upload files such as photos, and check the status of orders. Greeting-card workflows include PNG previews and a private editor link where a user can refine the design before ordering.

The service is designed around a user-controlled sending process. Rather than immediately dispatching mail, an agent can create a PieterPost review link or hosted payment link. The recipient reviews the content and pays before PieterPost sends the item. Card drafts remain unpaid and do not create a completed order.

## How it works

Clients connect to the hosted Streamable HTTP endpoint at `https://pieterpost.com/mcp/setup/`. The public endpoint at `https://pieterpost.com/mcp/public/` supports guest use without an account or authentication. Account-specific operations and saved Address Book contacts use PieterPost’s OAuth issuer at `https://pieterpost.com/mcp/oauth`.

A typical card workflow starts by selecting available card options, creating a design, and retrieving or updating that design. A supplied photo can be uploaded first; the resulting asset ID is then used in the card design. The user receives a private editor or review link to inspect the result and continue toward ordering.

## Setup and configuration

Add the hosted server URL to an MCP client that supports remote Streamable HTTP servers:

```json
{
  "type": "mcp",
  "name": "PieterPost",
  "server_url": "https://pieterpost.com/mcp/setup/"
}
```

Use the public endpoint when a guest workflow is sufficient. Use the setup endpoint when account access, OAuth permissions, or saved contacts are needed. No local server process or environment variables are required for the hosted service.

## Tools and capabilities

The documented greeting-card tools are:

- `list_card_options` for available card choices.
- `create_card_design` to start a card draft.
- `get_card_design` to retrieve a design.
- `update_card_design` to modify a design.

The wider mail workflow supports drafting letters and postcards, quoting prices, creating review links, creating hosted payment links, uploading assets, using Address Book contacts, and checking order status. Explain fallback-font and print warnings to the user before ordering a greeting card.

## Limitations and notes

PieterPost sends physical mail only after the user reviews and pays through the relevant flow. Creating a greeting-card draft alone does not place a paid order. The guest endpoint provides the four card tools and public mail tools, while account features and saved contacts require OAuth access. The service is intended for MCP clients that can connect to its remote Streamable HTTP endpoint.

_Full upstream README: https://allmcps.com/mcp/pieterpost-mcp/readme_