Collaboration & Communication · Saperly + Claude
Saperly MCP with Claude: Phone, SMS and Voice Workflows for Your Agents
The short answer
Claude works with Saperly through the Model Context Protocol, an open standard that acts as a secure adapter between the two. Once connected with an API key, Claude can provision phone numbers, send text messages, place voice calls and manage compliance tasks from natural language instructions, within permissions the organisation sets.
What is Saperly?
Saperly is a phone carrier API built for AI agents. It provides phone numbers, voice calling, SMS messaging and compliance tools in one place, so teams do not have to stitch together separate carrier, messaging and regulatory systems themselves. It is typically used by product teams, customer operations groups and developers who want chatbots and AI agents to communicate reliably by phone and text.
How Claude connects to Saperly through MCP
The Model Context Protocol, or MCP, is an open standard that lets Claude use other software securely. Think of it as a universal adapter between Claude and a tool. The organisation decides exactly what Claude is allowed to see and do, and the connection can be switched off at any time.
Once Saperly is connected using an API key, Claude can typically work with the phone numbers in your account, send SMS messages, place voice calls and check compliance status, all from plain-English instructions. For example, a team member might ask Claude to send a appointment reminder to a list of customers, and Claude carries out the request through Saperly.
Permissions and approvals keep people in charge. Access can be limited to only the actions a workflow needs, and consequential steps such as sending messages to large lists or buying new numbers can require a named person to approve them first. Activity can be logged so every action is traceable.
What you can automate
Appointment and booking reminders
A clinic, salon or service business can have Claude send text reminders ahead of appointments, using details from the booking system. Staff describe the reminder rules in plain English, and Claude sends the messages through Saperly. Replies can be routed to the front desk for follow-up.
Outbound voice notifications
Operations teams can use Claude to place voice calls for time-sensitive notices, such as delivery changes or service interruptions. Claude can read the approved script and contact list, then place the calls through Saperly, with a supervisor approving the list before anything goes out.
Support chatbot handoffs
When a website or app chatbot reaches a point where a customer needs a human, Claude can send a text message with a callback link or arrange a phone call through Saperly. This helps customers move from chat to phone without losing context.
Compliance and number management
Telecom administration can be time-consuming. Claude can help a compliance or IT lead review phone number status, check registration tasks and prepare summaries of what needs attention. Final changes stay with a named person who signs off on them.
Two-factor and verification messages
Product and security teams can have Claude trigger one-time verification texts or calls for account sign-in flows. Claude manages the sending through Saperly, while the organisation controls message wording and rate limits to reduce misuse.
An end-to-end workflow: Customer delivery notification with CRM follow-up
TriggerA delivery in the order system is marked as delayed by more than two hours.
Claude reads the delayed order and the customer's contact preferences from the CRM.
Claude drafts a short SMS explaining the new delivery window, using the approved message template.
A dispatch supervisor reviews the batch and approves it in the workflow.
Claude sends the approved messages through Saperly and records delivery status.
Customers who do not respond within an hour are flagged for a voice call, which Claude schedules through Saperly.
Outcomes are written back to the CRM so the support team sees the full history.
OutcomeCustomers hear about delays quickly and clearly, support enquiries about delivery times typically fall, and the CRM holds an accurate record of every contact.
How we set it up
Free automation audit
We review your customer messaging, reminder and call workflows to identify where Saperly and Claude will save the most time, and where human approval should sit.
Secure API key connection
We connect Claude to Saperly using an API key, stored securely and scoped to the least access each workflow needs. Where a direct API route suits your team better, we set that up instead.
Workflow and approval design
We design the end-to-end workflow across Saperly and your other systems such as CRM, ticketing or Microsoft 365, defining templates, contact rules and the points where people approve actions.
Testing against real cases
We test the workflow against past scenarios and sample contact lists in a controlled setting, checking message accuracy, timing and approval routing before anything reaches customers.
Launch, monitoring and training
We launch with audit logs and monitoring in place, then train your team on how to use the workflow, review activity and respond when something needs attention.
Who benefits
- Customer operations manager
- Sends timely, consistent customer messages without manually building each list or message.
- Product manager
- Adds reliable phone and text features to apps and chatbots without building telecom systems in-house.
- IT or compliance lead
- Gets clear visibility of number and messaging activity, with approval points and logs for review.
- Developer or engineering lead
- Connects AI agents to telecom capabilities through a single, well-defined interface.
Security and control
- Least-privilege access, so Claude only reaches the Saperly actions each workflow needs.
- Named human approval for bulk sends, new number purchases and changes to compliance settings.
- Approved message templates and contact rules to reduce the risk of unwanted or incorrect messages.
- Audit logs of every message, call and change made through the connection.
- Clear controls to pause or revoke the API key at any time.
For teams in the US, UK, India and the Middle East
Organisations in the United States and the United Kingdom need to follow telephone and messaging consent rules, and Claude workflows can be designed to respect opt-in and opt-out preferences. In India, the Digital Personal Data Protection Act, 2023 governs how customer contact data is handled, and workflows can be built to match it. Organisations in the UAE and Saudi Arabia must observe their local data protection laws, and the hosting region for any custom application is chosen to meet these requirements.
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 Saperly MCP server do?
The Saperly MCP server is the connector that lets Claude use Saperly securely. It translates Claude's requests into Saperly actions such as sending an SMS or placing a call. Your organisation controls which actions are allowed, and the connection can be paused or removed at any time.
Is connecting Saperly to Claude secure?
Security depends on how the connection is set up. We store the API key securely, limit access to only the actions each workflow needs, add approval steps for sensitive actions and keep audit logs. We cannot guarantee security outcomes in every environment, but these controls are standard good practice for this kind of connection.
What can Claude do with Saperly once connected?
Typically, Claude can help provision phone numbers, send SMS messages, place voice calls and check compliance status, all from natural language instructions. The exact actions available depend on your Saperly account and the permissions you grant to the connection.
How long does setup take?
Simple workflows can often be connected and tested within a few weeks, while multi-system workflows with several approval stages usually take longer. The free automation audit gives a realistic timeline for your specific setup.
Which account access or permissions are needed?
Generally, you need a Saperly account with an API key that has permission for the actions you want Claude to perform. Using a key with only the required permissions is recommended. We confirm the exact requirements during the audit, based on how your Saperly account is set up.