Skip to main content
The thanks.io MCP server lets an AI assistant work in your thanks.io account. Once it is connected, you can ask in plain language and the assistant does the work with the tools listed on this page:
  • Send real mail. Postcards, windowed and windowless letters, notecards, magnacards and gift cards, to saved mailing lists or addresses you give it.
  • Preview and price first. Every order can be rendered as proof images with its exact total before anything is charged.
  • Design. Use your saved creatives and templates, or have ThanksAI Studio draw a new front design from a description.
  • Build audiences. Create mailing lists and add recipients.
  • Track results. Check printing and delivery, QR code scans and gift card redemptions, and see which designs, messages and lists perform best.
  • Automate. Create recurring campaigns and turn them on or off.
The server is a remote MCP server at:
This is a different server from the Documentation MCP Server at https://docs.thanks.io/mcp. The documentation server only searches these docs and cannot read your account or send mail. Use the server on this page to work with your account.

Before You Start

You will need:
  • A thanks.io account
  • An AI assistant that supports remote MCP servers over HTTP, such as Claude, ChatGPT, Gemini, Claude Code, Cursor or GitHub Copilot in VS Code

How It Connects

Most assistants need only the server URL. When you add it, the assistant opens a thanks.io sign-in page; sign in and approve access, and you are connected. There is no API key to copy or paste. The server supports OAuth 2.0 with dynamic client registration, so assistants register themselves automatically. You do not need to create an OAuth application in your dashboard first.

API key (fallback)

If an assistant cannot sign in on its own, connect with an API key sent as a bearer token:
  1. In your dashboard, open Settings → API & MCP Access.
  2. In the API Keys section, click Create API Key, name it, and leave Allow MCP access turned on.
  3. Copy the key. It is shown only once.
  4. Configure your assistant to send it in the Authorization header:
A key created without Allow MCP access is refused by the MCP server. Treat an MCP-enabled key like a password: anyone holding it can act on your account, and can send mail once orders are allowed (see below).

Spending Permissions

Connecting an assistant does not let it spend money. Two settings under Settings → API & MCP Access, in the MCP Permissions section, decide what it may pay for. Both start off. Without them, an assistant can still check results, plan, design, save templates and creatives, build mailing lists from full addresses, and preview orders. When it needs a permission you have not turned on, the tool is refused, nothing is charged, and the assistant tells you which setting to switch on.
Once Allow orders via MCP is on, your assistant can send real mail. Orders are charged to your credit balance or card and cannot be recalled once printing starts. Gift card orders are also charged the face value of every card. The server instructs assistants to show you a preview with the total and wait for your confirmation before every send, so read the preview before you approve. Turning on a recurring campaign authorizes every send it will make on its schedule.

Set Up Your Assistant

The quickest way is to ask your assistant to set itself up. Paste this into the assistant you use:
Or follow the steps for your assistant. Menu names can change as these apps update.
On claude.ai or the Claude desktop app:
  1. Open Settings, then Connectors.
  2. Choose Add custom connector, name it thanks.io, and paste https://mcp.thanks.io/mcp.
  3. Click Connect, sign in to thanks.io, and approve access.

What to Ask

Some examples to start with:
  • “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.”

How Sends Work

The server guides every assistant through the same steps before any mail goes out:
  1. Pick the audience: a saved mailing list, or addresses you provide.
  2. Pick what to print: usually a saved creative from your creatives library, or a front design and a message.
  3. Preview the order with preview-order, which renders proof images and calculates the exact total without charging anything.
  4. Show you the proofs and the total, and wait for your confirmation.
  5. Send with the matching send tool.
After saving a design, placing an order or creating a campaign, the assistant gives you a link to review it in your dashboard, where you can also cancel an order that is still under review. To act for one of your sub-accounts, ask the assistant to use that sub-account. It finds the sub-account with list-sub-accounts and passes its sub_account_id to the other tools.

Tools

Plan from results

Account and catalog

Creatives library

ThanksAI Studio

Audience

Preview then send

The send tools need Allow orders via MCP. A recipient given an email address but no street address needs Allow lead purchases via MCP, for preview-order and the send tools as well as add-recipient and add-recipients.

Order lifecycle

Recurring campaigns

Prompts

The server also offers ready-made prompts for planning: plan your next campaign, review your results, set up a tracked test, win back quiet contacts, a full strategy session, and playbooks for real estate, insurance and e-commerce. How you pick a prompt depends on your assistant; many show them in a menu or as slash commands.

Disconnecting

To disconnect an assistant, remove the connector or MCP server in the assistant’s own settings. If you connected with an API key, delete the key under Settings → API & MCP Access to revoke it.

Get Help

Questions about connecting an assistant? Email support@thanks.io.