postals-mcp

What this does

postals-mcp exposes a set of tools to Claude over the Model Context Protocol. After you add it to claude_desktop_config.json (snippet above) and restart Claude Desktop, those tools become callable inside any conversation.

Requirements

This server needs the following environment variables to be set before it can run:

POSTALS_API_KEY
POSTALS_SENDER_NAME
POSTALS_SENDER_ADDRESS
POSTALS_SENDER_CITY
POSTALS_SENDER_STATE
POSTALS_SENDER_ZIP
POSTALS_DEFAULT_CARD_IMAGE
POSTALS_HANDWRITING_STYLE
POSTALS_DAILY_LIMIT
POSTALS_TEST_MODE
CLOUDFLARE_ACCOUNT_ID
CLOUDFLARE_API_TOKEN

Set these via the env object in your MCP config (see claude_desktop_config.json snippet above).

How do I install postals-mcp?

Run the Claude Code command in the install section to add postals-mcp to Claude Code, or copy the ready-made config for your client from the install section on this page. Restart your client afterwards and the tools appear in your next conversation.

Which clients work with postals-mcp?

This page carries setup and config for Claude Code, Claude Desktop, Cursor and VS Code. Any other MCP client that accepts a standard server config can connect to postals-mcp as well.

Does postals-mcp need an API key?

Yes. Before it can run, set these environment variables: POSTALS_API_KEY, POSTALS_SENDER_NAME, POSTALS_SENDER_ADDRESS, POSTALS_SENDER_CITY, POSTALS_SENDER_STATE, POSTALS_SENDER_ZIP, POSTALS_DEFAULT_CARD_IMAGE, POSTALS_HANDWRITING_STYLE, POSTALS_DAILY_LIMIT, POSTALS_TEST_MODE, CLOUDFLARE_ACCOUNT_ID, CLOUDFLARE_API_TOKEN. They go in the env block of your MCP config.