Productivity & Project Management · Lob + Claude
Lob MCP with Claude: Send and Verify Direct Mail Through Natural Language
The short answer
Claude works with Lob through the Model Context Protocol (MCP), an open standard that gives Claude secure, permission-controlled access to the tool. Once connected, Claude can help send letters, validate addresses, track mail and manage templates using plain-English instructions, while your team approves important actions.
What is Lob?
Lob is a direct mail automation and address verification platform for businesses. It lets organisations send physical mail at scale through a simple API, and check that addresses are valid before anything is posted. Typical users include marketing teams running customer campaigns, finance teams sending statements, and operations teams handling notices and forms that still need to arrive on paper.
How Claude connects to Lob 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 like Lob. It gives Claude a defined set of things it can read and do, and nothing beyond that.
Once Lob is connected, Claude can typically check and verify mailing addresses, prepare letters from your templates, send mail on instruction, and look up the status of items already posted. You can ask in everyday words, for example asking Claude to confirm a list of addresses before a campaign goes out.
Permissions and approvals keep your people in charge. Access is set to least privilege, so Claude only sees what it needs. Consequential actions, such as sending a large batch of physical mail, can require a named person to approve first, and every action is recorded in an audit log.
What you can automate
Address checking before a mailing
Before a campaign or statement run, Claude can validate every address on a list against Lob's verification service. Staff receive a short report of corrected, undeliverable and incomplete addresses, so postage is not wasted on mail that cannot be delivered.
Customer letters from a CRM
When a customer record meets set criteria, such as a renewal date approaching, Claude can prepare a personalised letter from an approved template and queue it for sending. A team member reviews the batch before it leaves.
Tracking mail on request
Customer service staff can ask Claude where a letter is in the delivery process. Claude looks up the status in Lob and gives a plain answer, which saves time on phone calls and e-mail chains.
Template management
Marketing or operations leads can ask Claude to list, review or update mail templates. Changes can be drafted and checked before they go live, keeping branding and wording consistent across campaigns.
Compliance-friendly notices
Where rules require a physical notice, such as a formal change to terms, Claude can prepare the mailing, confirm the addresses and log each dispatch. This gives compliance teams a clear record of what was sent and when.
An end-to-end workflow: Annual policy renewal letters
TriggerA renewal date is 60 days away for a customer in the CRM.
Claude reads the customer record from the CRM and confirms the renewal date and policy type.
Claude validates the customer's postal address through Lob's address verification.
Claude fills an approved renewal letter template with the customer's details and prepares the mailing.
A team member reviews a batch summary in Microsoft 365 and approves the run.
Claude sends the letters through Lob and records each dispatch in the CRM.
Claude later reports tracking status to the service team when customers ask about their letter.
OutcomeRenewal letters reach customers on time, with verified addresses, fewer returned items and a complete record for compliance review.
How we set it up
Free automation audit
We review how your team currently sends mail, checks addresses and tracks dispatches, and identify the workflows worth automating with Claude and Lob.
Secure connection
We connect Claude to Lob using the API key sign-in method, with the key stored securely and access limited to the actions your workflow needs.
Workflow design
We design the end-to-end process across Lob and your other systems, such as your CRM or Microsoft 365, and agree which actions need human approval.
Testing with real cases
We test the workflow against past mailings and address lists, checking accuracy, edge cases and approval steps before anything goes live.
Launch, monitoring and training
We launch with audit logs and monitoring in place, then train your team on how to use Claude with Lob day to day and review performance with you.
Who benefits
- Marketing managers
- Run direct mail campaigns faster, with verified addresses and templates managed in plain language.
- Operations leads
- Automate routine notices and letters while keeping approvals and records in their hands.
- Customer service teams
- Answer questions about mail delivery quickly without searching through several systems.
- Finance and compliance heads
- Gain a clear audit trail of physical mail sent to customers.
Security and control
- Least-privilege access, so Claude only reaches the parts of Lob your workflow requires.
- Named human approval for large or consequential mailings before they are sent.
- Full audit logs of every action Claude takes in Lob and connected systems.
- Address and data handling reviewed against your internal policies before launch.
- Ongoing monitoring with the ability to pause or revoke the connection at any time.
For teams in the US, UK, India and the Middle East
Organisations in the United States and the United Kingdom can host the Claude workflow in their chosen region to align with local data handling expectations. Businesses in India must consider the Digital Personal Data Protection Act, 2023, when handling customer names and addresses, and we design for it. Organisations in the UAE and Saudi Arabia must meet their national data protection laws, and we select hosting regions to meet those requirements. Each deployment is configured around the rules that apply to your business.
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 Lob MCP server do?
The Lob MCP server acts as a secure bridge between Claude and your Lob account. It lets Claude carry out tasks such as validating addresses, sending letters, tracking mail and managing templates, using the permissions you set. It does not give Claude access beyond what the server allows.
Is connecting Lob to Claude secure?
Security depends on how the connection is set up. We use the API key sign-in method, store the key securely, apply least-privilege access and keep full audit logs. Consequential actions can require human approval. We review the setup with your IT team before launch.
What can Claude do with Lob once connected?
Typically, Claude can verify addresses, prepare letters from templates, send mail on instruction, track the status of items and help manage templates. Exactly what it can do depends on the workflow we design together and the permissions you approve.
How long does setup take?
A simple connection and single workflow can often be set up within a few weeks. More complex projects involving several systems, approval chains and testing take longer. We confirm a realistic timeline during the free automation audit.
Which Lob account and permissions are needed?
In general, you need a Lob account with an API key that has the permissions your planned workflow requires. We advise on the minimum access needed during the audit, so you avoid granting more than is necessary.