Give Claude, ChatGPT, Gemini, or Cursor a real postal channel. One URL, OAuth sign-in, no API key to paste.
Your AI agent plans the campaign, renders proof images with an exact total, waits for your approval, then prints, addresses, and mails real postcards, letters, notecards, MagnaCards, and gift cards — and tracks every QR scan and delivery.
Full account access through plain-language tools — no REST plumbing, no glue code.
Postcards, windowed and windowless letters, notecards, MagnaCards, and gift cards — to saved mailing lists or addresses your agent is given.
Every order renders proof images with its exact total before anything is charged. Your agent shows you the proof, you approve, then it mails.
Use saved creatives and templates, or have the agent draw a brand-new front design from a plain-English description.
Create mailing lists, add recipients one at a time or in bulk, and check deliverability status — all from the chat.
Printing and delivery status, QR code scans, gift card redemptions, and which designs, messages, and lists perform best.
Create recurring campaigns for any list. New campaigns start paused — your agent turns them on only when you say so.
The server uses OAuth 2.0 with dynamic client registration: your assistant registers itself, opens a thanks.io sign-in page, and you approve access. Or paste this into the assistant you already use and let it set itself up.
I'd like to connect you to my thanks.io account so you can help me with direct mail. thanks.io has a remote MCP server at https://mcp.thanks.io/mcp that uses OAuth sign-in, so no API key is needed. Walk me through adding it as a connector in the app I'm using to talk to you right now, one step at a time.
claude mcp add --transport http thanksio \ https://mcp.thanks.io/mcp
{
"mcpServers": {
"thanksio": { "url": "https://mcp.thanks.io/mcp" }
}
}If your assistant can't sign in on its own, create a key under Settings → API & MCP Access with Allow MCP access on, and send it as a bearer token. Treat an MCP-enabled key like a password.
{
"mcpServers": {
"thanksio": {
"url": "https://mcp.thanks.io/mcp",
"headers": { "Authorization": "Bearer YOUR_API_KEY" }
}
}
}Autonomous mail sounds scary until you see the guardrails. Spending permissions start off, and every send follows the same preview-then-confirm flow.
preview-order renders proof images and calculates the exact total without charging anything. Your agent shows you the proof and waits.
Allow orders via MCP and Allow lead purchases via MCP both start off in your dashboard. Without them, paid tools are refused — nothing is charged, and the agent tells you which switch to flip.
Every order gets a dashboard link where you can cancel while it's still under review, then follow printing, delivery, and QR scans in real time.
The server also ships ready-made prompts for campaign planning, results reviews, and full strategy sessions.
How is my mail doing? Which of my postcards gets the most QR scans?
Send my open house postcard to the Austin Sellers list. Show me the proof and the total first.
Design a postcard for a spring HVAC tune-up special, then save it as a creative.
Set up a birthday card campaign for my Clients list, but leave it paused.
Don't mix them up: one works your account, the other reads the docs.
https://mcp.thanks.io/mcp
Connects your assistant to your thanks.io account. Sends real mail, manages lists and creatives, creates campaigns, reads results. OAuth or API key.
https://docs.thanks.io/mcp
Read-only access to the thanks.io API documentation for AI coding assistants. Setup guide at docs.thanks.io/mcp-server, or npx mint-mcp add thanksio.
The thanks.io MCP server is a remote Model Context Protocol server at https://mcp.thanks.io/mcp. It lets AI assistants like Claude, ChatGPT, Gemini, and Cursor work directly in a thanks.io account: send postcards, letters, notecards, MagnaCards, and gift cards; preview orders with proof images before paying; design with ThanksAI Studio; build mailing lists; track QR scans and deliveries; and manage recurring campaigns.
In Claude or the Claude desktop app, open Settings, choose Connectors, click Add custom connector, name it thanks.io, and paste https://mcp.thanks.io/mcp. Click Connect, sign in to your thanks.io account, and approve access. For Claude Code, run: claude mcp add --transport http thanksio https://mcp.thanks.io/mcp
No. The server supports OAuth 2.0 with dynamic client registration, so assistants sign in through a thanks.io authorization page automatically — there is no API key to copy or paste. An API key sent as a bearer token is available as a fallback for assistants that cannot sign in on their own.
Not until you allow it. Two settings under Settings → API & MCP Access — Allow orders via MCP and Allow lead purchases via MCP — both start off. With them off, an agent can preview orders, plan, design, and build lists, but every paid action is refused. Orders are also previewed with an exact total and wait for your confirmation before sending.
The product MCP server at https://mcp.thanks.io/mcp connects an assistant to your thanks.io account so it can send and manage real mail. The documentation MCP server at https://docs.thanks.io/mcp is read-only: it only searches the thanks.io API documentation and cannot read your account or send anything.
Mail sent through MCP costs the same as mail sent any other way on thanks.io: pay-as-you-go with no minimums and postage included. A free account comes with $10 in credits to test with. Sample 4x6 postcards run about $0.77 on Business and $0.64 on Professional.
Postcards, windowed letters, windowless letters, folded notecards, MagnaCards with a tear-off magnet, and gift cards. Gift card orders are charged for the mailing plus the face value of each card.
For deeper questions, the full MCP server documentation covers every tool, and thanks.io/agents covers REST API, webhooks, and Zapier routes for agents.
Free account, $10 in credits, no minimums, postage included. Postcards from $0.64.