Sent MCP Server

The Sent MCP server exposes Sent's messaging tools (send, lookup, contacts, templates, analytics, Sender Profiles, SMS compliance, and feedback) directly inside your AI agent. No API keys to paste, no context-switching to another tab. Your agent can send a real SMS, look up a contact, or check deliverability without leaving your editor.

What you can do

27 tools in total. Connections through Claude's hosted connector get 25 of them; see Claude connector policy.

Setup

https://mcp.sent.dm/mcp

claude mcp add --transport http sent https://mcp.sent.dm/mcp

{
  "mcpServers": {
    "sent": {
      "url": "https://mcp.sent.dm/mcp"
    }
  }
}

{
  "servers": {
    "sent": {
      "type": "http",
      "url": "https://mcp.sent.dm/mcp"
    }
  }
}

Send a WhatsApp message to +1234567890 using the order_confirmation template
with customerName="Alex" and orderNumber="#9981"

Look up the phone number +447911123456 and tell me what channel it supports

Show me deliverability stats for the last 7 days

Available tools reference

The Available in Claude column shows which tools connections through Claude's hosted connector can use. Every tool is available to Claude Code and other MCP clients.

Messaging

Contacts

Templates

Lookup & Analytics

Account

Sender Profiles

SMS Compliance

Feedback

Claude connector policy

Connections authorized through Claude's hosted connector (claude.ai, Claude Desktop, Claude mobile, and Cowork) get a restricted policy. The Sent server enforces it on every request from that connection, even when no plugin is installed:

• No Sender Profile provisioning. sender_profiles.create and sender_profiles.delete are not listed and refuse direct calls. Create and delete Sender Profiles in the Sent Dashboard. compliance.setup_plan returns a Dashboard link instead of a create call.
• One recipient per send. messages.send accepts one phone number per call. Use the Dashboard or the REST API for bulk sends.
• No MARKETING templates. messages.send refuses a template in the MARKETING category. UTILITY and AUTHENTICATION templates send as usual. Send marketing campaigns from the Dashboard or the REST API.
• Organization send quota. All Claude connections in an organization share one quota, by default 10 sends per minute and 100 sends per day. A send on several channels counts once per channel. Adding connections or Sender Profiles does not reset it.
• Opt-outs. A recipient who has opted out is refused before anything is queued, from Claude or from any other client.

Claude Code and other MCP clients keep the full set of 27 tools. Claude connections authorized before this policy were moved onto it when they used a key the connector had created for them (named MCP-YYYY-MM-DD). A Claude connection you authorized with one of your own API keys keeps that key's access until you deactivate the key in Dashboard → API Keys and reconnect the connector.

Example use cases

• Send one approved template message to a customer and check its delivery status.
• Review a message's activity timeline when a send looks stuck.
• Find, add, or remove contacts, and summarize a contact's message history.
• Find an approved template by name, or delete one you no longer use.
• Check messages sent, deliverability, and contact totals, or look up a phone number's capabilities.
• Check account details, balance, onboarding status, and the SMS requirements for a market.
• Rename a Sender Profile or update its description.
• Send feedback about the tools to the Sent team when you ask for it.

Authentication details

The Sent MCP server uses OAuth 2.1 with PKCE (RFC 7636) and Dynamic Client Registration (RFC 7591). Your agent registers itself automatically. No manual client ID setup required.

• Token expiry: None. Tokens are long-lived.
• Phone verification: Connecting requires a verified phone number on your Sent account, the same as the dashboard. An account that has not verified one is sent to verify it first, then returned to finish connecting.
• Revocation: Dashboard → API Keys → deactivate the key the connection uses. Deactivating a key that other tools share signs those tools out too. Claude connections always get their own key, named Claude connector YYYY-MM-DD.
• Scope: Tied to the organization or Sender Profile chosen during authorization. To grant access to a different one, re-authorize.

Related