Skip to content
Get Started
Blog

Sent is now an official Claude connector

Connect Sent and Claude can send messages from your account and reach the rest of the platform, from templates and contacts to compliance and analytics.

A Claude chat box with the Sent connector being switched on

Sent is live as an official Claude connector, built and maintained by us. Connect it and Claude can send SMS, WhatsApp, and RCS from your Sent account, and reach the rest of the platform too: contacts, message templates, compliance requirements, Sender Profile readiness, number lookup, analytics, and balance.

What Claude can reach

The connector exposes 25 tools:

AreaToolsWhat Claude can do with them
Messagesmessages.send, messages.get, messages.activities.listSend a template to one or many recipients on SMS, WhatsApp, or RCS, or let smart routing pick the channel. Schedule up to 30 days ahead. Get content, channel, status, and the full event trail: queued, sent, delivered, read, failed.
Templatestemplates.list, templates.get, templates.get_by_name, templates.deleteSearch by name, status, or category. Fetch a template and its variables.
Contactscontacts.create_many, contacts.list, contacts.get, contacts.delete, contacts.message_summaryCreate up to 10 contacts from phone numbers per call. Browse, inspect, delete. See message counts and deliverability rates per channel for any contact.
Compliancecompliance.requirements, compliance.setup_planSender requirements by country and number type: 10DLC, toll-free, short code, local, mobile, alphanumeric. Get a setup plan listing every required field.
Sender Profilessender_profiles.list, sender_profiles.get, sender_profiles.update (create and delete also available)List and inspect profiles, check channel readiness, update details.
Lookupnumbers.lookupValidity, carrier, line type, country, VoIP status, porting history.
Analyticsdashboard.deliverability, dashboard.messages_sent, dashboard.contactsDeliverability rate, volume over time, total contacts.
Accountaccount.get, balance.get, onboarding.statusAccount details, balance, onboarding and KYC state.
Feedbackfeedback.sendAnonymously tell us what the connector should do that it doesn’t yet.

When you don’t name a channel, Sent’s router channel picks one per recipient. It weighs different factors including deliverability, coverage, and cost across WhatsApp, SMS, and RCS. The final status records the channel that was actually used.

Try asking: “Send order_shipped to +14155550123 on WhatsApp and tell me when it’s delivered.” “Why did yesterday’s message to +44 7700 900123 fail?” “What do we need before we can text customers in the UK?”

The tool list will grow. If Claude can’t do something with Sent that you expected, say so in the conversation; feedback.send routes it to our team.

The connector is Sent’s hosted MCP server at mcp.sent.dm, so the same tools are available from Claude Code, Cursor, or any other MCP client without the directory listing. Everything it does goes through the public API.

If messaging is a feature of your product rather than something a person does in a conversation, build on the API directly.

Built-in guardrails

Opt-outs are enforced. A recipient who has opted out is blocked before the send, and Claude reports which numbers it skipped.

Compliance runs the same as everywhere else. A send through Claude passes the same registration and consent checks as a send through the API. If something is missing, Claude can tell you what, before it tries.

Provisioning stays in the Dashboard. Sender Profiles are created and deleted there, not through Claude. The only billed action in a conversation is a number lookup, which Claude confirms before running.

Scoped access. Claude only sees the organization and Sender Profile you authorized, and never holds your API key.

What’s scoped down through Claude

Connections through claude.ai, Claude Desktop, Claude mobile, and Cowork run a narrower policy than Claude Code or any other MCP client pointed at the same server.

The server enforces it per connection:

  • One recipient per send. Bulk sends go through the Dashboard or the API.
  • UTILITY and AUTHENTICATION templates only. MARKETING templates are refused; these campaigns go through the Dashboard or the API.
  • A shared organization quota. 10 sends a minute and 100 a day are the default, across every Claude connection in the org.
  • No Sender Profile create or delete. Both stay in the Dashboard. compliance.setup_plan returns a Dashboard link instead of a create call.

Claude Code and other MCP clients get the full set of 27 tools.

Get started

Connect Sent to Claude with one click. The full tool reference is in our docs.

Share

Published on

Read More

One API. Every channel.

Contact Sales