Marketing & Social Media · Cardly + Claude
Cardly MCP with Claude: Automate Personalised Direct Mail Campaigns
The short answer
Claude connects to Cardly through the Model Context Protocol (MCP), a secure standard that lets Claude use the tool with permissions you control. Once connected, Claude can help create personalised cards, schedule mail campaigns, check delivery status and manage customer outreach through natural language instructions, with people approving important actions.
What is Cardly?
Cardly is a platform for creating and sending personalised direct mail to customers. It helps businesses cut through digital clutter by reaching customers through their physical mailboxes. Marketing teams, customer success teams, sales teams and small business owners use it to send greetings, thank-you notes, reminders and special offers that feel personal and are more likely to be noticed than another email.
How Claude connects to Cardly through MCP
The Model Context Protocol (MCP) is an open standard that lets Claude securely use other software. Think of it as a universal adapter between Claude and a tool. It gives Claude a defined, controlled way to read information and take actions, and the organisation decides exactly what Claude is allowed to do.
Once Cardly is connected, Claude can typically help you draft personalised card messages, look up recipients, schedule sends for campaigns and check whether cards have been dispatched or delivered. You describe what you need in plain language, and Claude carries out the steps within the Cardly account you have authorised.
Access is controlled from the start. Connections use the API key sign-in method that Cardly supports, with least-privilege access so Claude only sees what it needs. Consequential actions, such as sending a batch of cards to a live customer list, can be set to require a person's approval before they happen, and audit logs record what was done.
What you can automate
Customer thank-you campaigns
After a large order or a renewal, Claude can help prepare a personalised thank-you card for each customer, using their name, purchase history and account manager. Your team reviews a sample batch, approves it, and the cards are queued in Cardly. This keeps the relationship warm without adding hours of manual writing to your week.
Birthday and milestone greetings
Customer success teams can use Claude to build a monthly list of client anniversaries, contract milestones and birthdays drawn from the CRM. Claude prepares the card wording and the recipient details, and Cardly sends them on schedule. The approach is simple, consistent and easy to audit.
Win-back and re-engagement offers
When customers have gone quiet, Claude can identify the group, suggest a short personalised note with a relevant offer, and submit it for approval. Physical mail often stands out against a crowded inbox, so this can be a useful complement to email rather than a replacement for it.
Delivery tracking and follow-up
Operations staff can ask Claude for a plain-language status update on a campaign, such as how many cards have been dispatched and which addresses returned errors. Claude can then flag the exceptions so the team can correct addresses and follow up quickly.
Event and conference follow-up
After a trade show or webinar, sales teams can send a handwritten-style card to the most valuable new contacts within days rather than weeks. Claude helps match each contact to the right message and tracks which cards have gone out, so no hot lead is forgotten.
An end-to-end workflow: Post-purchase thank-you and review request
TriggerA new order is marked as delivered in the company's ordering system.
Claude reads the order details and customer record from the CRM, such as name, product and account owner.
Claude drafts a short, personalised thank-you message suited to the customer's segment.
The account owner reviews and approves the card wording in a shared queue.
Claude creates the card in Cardly with the approved message and mailing address.
Claude checks dispatch status in Cardly and logs the result back to the CRM.
Any address errors are flagged to the operations team for correction.
OutcomeCustomers receive a personal thank-you card within a few days of delivery, account owners see every send recorded against the customer, and the team spends less time on manual mail preparation. Results will vary by business, but teams commonly report stronger customer recall than with email alone.
How we set it up
Book a free automation audit
We review your customer outreach, marketing and sales workflows to identify where personalised direct mail would add the most value. You leave with a clear list of priority campaigns.
Connect Cardly securely
We connect Claude to Cardly using the API key sign-in method, with least-privilege access so Claude only has the permissions each workflow needs. Keys are stored securely and rotated on a schedule.
Design the end-to-end workflow
We map how Cardly connects with your CRM, Microsoft 365 and other business systems. Approval steps are set for any send to live customers, so people stay in control of what goes out.
Test against real past cases
We run the workflow against past customer records and sample cards to check accuracy, tone and address handling before anything reaches a real recipient.
Launch, monitor and train
We go live with monitoring and audit logs in place, then train your marketing, customer success and operations teams to use Claude with Cardly confidently and safely.
Who benefits
- Marketing managers
- Run personalised mail campaigns without building every card by hand, and see delivery status in one place.
- Customer success leads
- Keep clients feeling valued with timely thank-you and milestone cards, prepared with the right details from the CRM.
- Sales directors
- Follow up with important new contacts quickly after events and meetings, with each send tracked against the deal.
- Operations and IT heads
- Get clear audit logs, controlled API key access and approval steps that keep customer data handling under your control.
Security and control
- Least-privilege API key access so Claude can only perform the actions each workflow requires.
- Human approval for any batch sent to live customers before it is dispatched.
- Audit logs recording what was prepared, approved and sent, and by whom.
- Test runs against sample records before any campaign goes live.
- Regular key rotation and secure storage of credentials.
For teams in the US, UK, India and the Middle East
Organisations in the United States and the United Kingdom can host the workflow in a region that meets their requirements, and customer data is handled in line with applicable privacy rules. In India, handling of personal data follows the Digital Personal Data Protection Act, 2023. Businesses in the UAE and Saudi Arabia are subject to local data protection laws, so the hosting region and data flows are designed to meet those obligations. We choose the hosting region with you before launch.
Learn more about Claude and MCP
Anthropic's AI model and assistant.
Secure links between Claude and business tools.
How engineers build and change software with Claude.
Hosted agents that run multi-step work.
The open standard Claude uses to connect to tools.
Frequently asked questions
What does the Cardly MCP server do?
The Cardly MCP server acts as a secure bridge between Claude and your Cardly account. It lets Claude read and act on approved information, such as creating cards and checking delivery status, through the access you grant. You stay in control of which actions are allowed, and every connection is set up with a defined scope.
Is connecting Cardly to Claude secure?
Security is built in from the start. The connection uses the API key sign-in method, with least-privilege permissions so Claude only sees what each workflow needs. Keys are stored securely, rotated regularly, and every action is recorded in audit logs. Approval steps can be added for any send to live customers.
What can Claude do with Cardly once it is connected?
Typically, Claude can help draft personalised card messages, look up recipients, schedule campaigns, send approved cards and check whether they have been dispatched or delivered. You give instructions in plain language, and Claude performs the steps within the access you have authorised.
How long does setup take?
Timelines depend on the complexity of your workflows and the systems they connect to. A focused setup for one campaign can often be completed in a few weeks, including the audit, testing and team training. Larger, multi-system programmes take longer. We confirm the timeline during your free automation audit.
What access or plan do I need to connect Cardly?
In general, you need an active Cardly account and an API key that the account owner can generate and share with us for the connection. The exact permissions depend on your Cardly setup, so we confirm what is needed during the audit and set the narrowest access that the workflow requires.