Thanks.io
thanks.io is a direct mail automation platform that enables users to send personalized postcards, letters, and notecards with handwritten fonts.
Verdict
Common use cases
- Send thank-you cards after closed deals
- Mail event invites to prospect lists
- Automate birthday cards for key accounts
- Re-engage churned customers with handwritten notes
- Build radius-targeted mailers for local campaigns
Integration
- Vendor
- Thanks.io
- Category
- other
- Auth
- API_KEY
- Tools
- 33
- Composio slug
thanks_io
Tools
- Add Recipient to Mailing List
Tool to add a new recipient to a mailing list. use after confirming recipient and list ids.
- Buy Radius Search Mailing List
Tool to buy or append a radius search mailing list based on address and radius. use when you need targeted mailing lists around a specified address.
- Create Mailing List
Tool to create a new mailing list. use when you need to group contacts under a fresh list before adding recipients.
- Create Multiple Recipients
Tool to create multiple recipients at once in a mailing list. use when batching recipient additions for efficiency.
- Create Sub-Account
Tool to create a new sub-account. use when you need to manage separate profiles with distinct return addresses and settings.
- Delete Mailing Listdestructive
Tool to delete a mailing list. use when you need to remove an entire mailing list by its id. confirm the list id before calling. example: "delete the mailing list with id 123e4567-e89b-12d3-a456-426614174000".
- Delete Recipient by Addressdestructive
Tool to delete a recipient by address and postal code. use when you need to remove a recipient without their id.
- Delete Recipient from Mailing Listdestructive
Tool to remove a recipient from a mailing list. use after confirming the recipient's id.
- Delete Sub-Accountdestructive
Tool to delete a specific sub-account by id. use when you need to remove an existing sub-account. confirm the id before calling.
- Execute Stored Send
Tool to execute a previously created stored send. use after creating a stored send to trigger delivery. the response body is empty; success is indicated by a 200 or 204 status.
- Get Recipient Details
Tool to get details for a specific recipient by id. use to verify a recipient’s full address and custom fields.
- Get Sub Account Details
Tool to retrieve details for a specific sub-account by id. use when you need full configuration of a sub-account before performing sub-account scoped operations.
- List Handwriting Styles
Tool to retrieve available handwriting styles. use when selecting a style for handwritten personalization.
- List Image Templates
Tool to retrieve a list of available image templates. use when you need to browse or select a template for mailings.
- List Mailing Lists
Tool to list all mailing lists. use when you need to fetch existing lists before managing recipients.
- List Message Templates
Tool to list available message templates. use when selecting a template for a mailing.
- List Orders
Tool to list recent orders. use after placing orders to fetch the latest history, optionally filtering by sub-account or limiting the result count.
- List Sub Accounts
Tool to list all available sub-accounts. use when you need to select a sub-account for operations requiring a sub-account context.
- Order Summary Statistics
Tool to retrieve order summary statistics for a date range. use when analyzing order volume and value filtered by type, status, or date range.
- Preview letter send
Tool to preview a letter send as pdf. use when you need to confirm letter content before placing the final order. returns pdf preview urls.
- Preview Notecard
Tool to preview a notecard send. use when you need front and back images before placing an actual notecard order.
- Preview Postcard
Tool to preview a postcard send. use when you need front and back images before placing an order.
- Preview Windowless Letter
Tool to preview a windowless letter send. use when you need a pdf preview of the cover-only letter before placing an order.
- Proof Postcard
Tool to generate a pdf proof of a postcard's front and back. use when you need a preview pdf before sending the final postcard.
- Search Orders by Recipient Full Name
Tool to search orders by recipient full name. use when you need to find all orders sent to a specific recipient.
- Search Orders by Recipient Street Address
Tool to search orders by recipient street address. use when you need to find all orders sent to a specific street address.
- Search Recipients by Email
Tool to search recipients by email across mailing lists. use when you need to find all recipients matching an email in specific lists. example: "find recipients with email test@test.com in lists [1,2,3]."
- Send Postcard
Tool to send a customized postcard. use when you need to dispatch a physical postcard with a chosen image and handwritten message.
- Stored Send Notecard
Tool to create a stored send for a notecard. use when you need to schedule mailing of a personalized notecard at a later time after preparing payload.
- Stored Send Postcard
Tool to create a stored send for a postcard. use when you need to prepare and schedule postcard orders for later execution; returns a url to finalize and send.
- Stored Send Windowless Letter
Tool to create a stored send for a windowless letter. use when you need to prepare a letter order for later execution.
- Update Recipient
Tool to update existing recipient details by recipient id. use when modifying recipient data after confirming the recipient exists.
- Update Sub-Account
Tool to update details for a specific sub-account. use when modifying title or return address details of a sub-account. confirm sub-account id before calling.
Setup
Setup guide
- 11. Log into Thanks.io and navigate to Settings > API Keys to generate a new key. 2. Copy the key to your clipboard. 3. In Switchy, open your workspace settings and click Integrations. 4. Find Thanks.io in the MCP directory and click Connect. 5. Paste your API key when prompted and click Authorize. 6. Return to any Space and type '@Thanks.io list my mailing lists' to confirm the connection works. 7. If you see your existing lists, the integration is live. 8. To send a card, @mention Thanks.io with recipient details and card type in a single prompt. 9. Check your Thanks.io dashboard to verify sends and monitor credit balance.
What teammates see: by default, memories from Thanks.io are scoped to the Space (PROJECT visibility) - you can mark any memory PRIVATE or share it ORG-wide.
Works well with
Top models
Compatibility data appears once enough Spaces have used this MCP together with a given model.
How Switchy teams use it
Starter prompts
Send Thank-You Card
@Thanks.io send a thank-you card to Jane Doe at 123 Main St, Austin TX 78701. Use a friendly tone and mention our recent call.Open in a Space →
Create Prospect Mailing List
@Thanks.io create a mailing list named 'Q2 Enterprise Prospects' so I can add contacts before sending invites.Open in a Space →
Add Recipients in Bulk
@Thanks.io add these five recipients to mailing list 'Q2 Enterprise Prospects': John Smith at 456 Oak Ave, Denver CO 80202; Sarah Lee at 789 Pine Rd, Seattle WA 98101; confirm when done.Open in a Space →
Buy Radius Mailing List
@Thanks.io buy a radius mailing list within 10 miles of 100 Congress Ave, Austin TX 78701. I need residential addresses for a neighborhood campaign.Open in a Space →
Delete Old Mailing List
@Thanks.io delete the mailing list named 'Q1 Webinar Attendees' — confirm the list ID before removing it.Open in a Space →
Example outputs
Illustrative - representative of the model's voice and quality, not literal recordings.
@Thanks.io create a new mailing list called 'Q1 2024 Product Launch' and add our top 50 enterprise customers from the CRM export I just uploaded.
I've created the mailing list 'Q1 2024 Product Launch' (ID: a7f3c891-4b2e-4d5a-9c8f-1e6d4a2b9f3c). I then used the Create Multiple Recipients tool to batch-add 50 contacts from your CSV. All recipients are now enrolled and ready for direct mail campaigns. You can view the list in your Thanks.io dashboard under 'Mailing Lists' to verify addresses and customize handwriting styles before sending.
This example demonstrates list creation and batch recipient import — two core workflows for launching a direct mail campaign. Requires a valid API key with write permissions. The MCP doesn't validate postal addresses; Thanks.io will flag undeliverable addresses during campaign execution, so review the dashboard before finalizing sends.
@Thanks.io search for all recipients in our 'Holiday 2023' mailing list who live within 10 miles of our Seattle office, then show me a count by zip code.
I used the Buy Radius Search Mailing List tool with your Seattle office address and a 10-mile radius, cross-referencing against the 'Holiday 2023' list. Here's the breakdown: 98101 (12 recipients), 98109 (8 recipients), 98121 (5 recipients), 98104 (3 recipients). Total: 28 recipients within range. Note that this is an illustrative summary — actual results depend on Thanks.io's address database and your list's current state. You can export the full dataset from the dashboard for deeper segmentation.
Showcases the radius search capability, useful for geo-targeted campaigns (local events, store openings). The tool may incur usage costs if it appends new data to your account. Always confirm pricing in Thanks.io's billing settings before running large radius queries. The MCP returns list IDs, not full recipient objects, so follow-up calls may be needed for detailed contact info.
@Thanks.io draft a summary of all active mailing lists in our account, then recommend which lists to archive based on last-send date and recipient overlap.
I retrieved metadata for 14 active mailing lists. Three lists ('Webinar Attendees May 2023', 'Trade Show Leads June 2023', 'Beta Testers v1') haven't been used in over 180 days and share 60%+ recipient overlap with your 'Engaged Customers 2024' list. Recommendation: archive these three to reduce clutter and avoid duplicate sends. The remaining 11 lists have recent activity or unique audiences. This analysis is based on list creation dates and recipient counts visible via the API — Thanks.io doesn't expose send history through the MCP, so verify campaign logs in the dashboard before archiving.
Demonstrates the AI's ability to synthesize list data and provide operational recommendations. The MCP can read list metadata but not full campaign analytics (open rates, delivery status), so this example relies on structural signals like overlap and age. Use this as a starting point, then cross-check with Thanks.io's reporting UI for send performance before making deletion decisions.
Use-case deep-dives
When handwritten postcards beat email for high-ticket leads
A 3-person real estate team closes 15-20 deals a quarter and wants to send handwritten postcards to past clients and warm leads. Thanks.io's radius search tool lets them buy mailing lists around new listings, and the batch recipient creation handles 50-100 contacts at once without manual entry. The sub-account feature keeps each agent's return address separate, so replies route correctly. This works when your team has budget for physical mail ($2-5 per card) and a CRM that can export address lists. If you're sending under 20 cards a month, the API overhead isn't worth it—just use Thanks.io's web interface. But for teams running quarterly campaigns to 200+ contacts, the MCP turns a 4-hour manual task into a 10-minute Switchy prompt.
Scaling personalized thank-you notes without hiring coordinators
A 6-person nonprofit development team sends handwritten thank-you cards to donors who give over $500. They used to batch these monthly in a spreadsheet, but cards went out 3-4 weeks late. With the Thanks.io MCP in Switchy, the team pulls donor data from their CRM, creates a mailing list per campaign tier, and queues cards the same day gifts clear. The delete-by-address tool cleans up duplicates when a donor gives twice in one month. This scenario wins when you're sending 50-300 cards per month and timing matters—late thank-yous kill retention. If your volume is under 30 cards monthly, the setup cost outweighs the speed gain. For teams where a week's delay costs thousands in repeat donations, this MCP pays for itself in quarter two.
When physical invites drive 3x the RSVP rate of email
A 5-person B2B sales team hosts quarterly executive dinners and needs 15-20 attendees per event. Email invites get 8% RSVPs; handwritten cards get 25%. The Thanks.io MCP lets them pull target accounts from Salesforce, create a mailing list per event, and send invites 3 weeks out. The radius search tool finds prospects near the venue when they need to fill last-minute seats. This works when your average deal size justifies $3-5 per invite and you're targeting 100-200 accounts per quarter. If you're inviting under 50 people or your events are virtual, stick with email. But for teams where one extra attendee covers the cost of 40 cards, the MCP turns invite management into a 15-minute pre-event task instead of a multi-day project.
Frequently asked
What does the Thanks.io MCP do in Switchy?
It lets your AI agents send physical direct mail — handwritten cards, postcards, gifts — through Thanks.io's API. Agents can create mailing lists, add recipients, buy radius-targeted lists, manage sub-accounts, and trigger sends. You're automating offline outreach the same way you'd automate an email campaign, but with real stamps.
Do I need admin access to connect Thanks.io?
You need a Thanks.io API key, which any account holder can generate from their dashboard. There's no OAuth flow — just paste the key into Switchy. If you're using sub-accounts in Thanks.io, make sure the key has permissions for the accounts your agents need to touch.
Can the MCP send a card to someone right now?
Not directly in one step. The MCP creates mailing lists, adds recipients, and buys targeted lists, but you still trigger the actual send through Thanks.io's dashboard or a separate send endpoint. Think of this as the setup layer — agents prep the audience, you approve and send.
Why use this instead of Thanks.io's dashboard?
If you're pulling recipient data from Slack threads, CRM exports, or research agents, the MCP saves you from manual CSV uploads. An agent can build a mailing list from a dozen sources, dedupe by postal code, and hand you a ready-to-send campaign — no spreadsheet wrangling.
Who on the team should connect this MCP?
Whoever owns your Thanks.io account and understands your mailing budget. The MCP can buy radius lists and create sub-accounts, so you want someone who won't accidentally burn through credits. Marketing ops or growth leads are typical owners.