Live at mcp.sent.dm

Sent for AI agents.

The Model Context Protocol server for Sent. Every messaging primitive you ship today over REST — send, lookup, contacts, templates, analytics — is reachable from any MCP-capable agent. Same identity, same audit trail, same compliance gates.

18 tools 3 channels — SMS · WhatsApp · RCS OAuth 2.1 + PKCE · DCR

Install

Paste one of these into your MCP client. The first call opens a Sent consent page where you pick an organization, sender profile, and API key. No refresh tokens — revoke any time from the dashboard.

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

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

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

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

Claude Desktop and Cursor read from ~/Library/Application Support/Claude/claude_desktop_config.json and ~/.cursor/mcp.json respectively. VS Code reads from .vscode/mcp.json in the workspace.

Tool catalog

Each tool maps to a Sent REST capability with the same input shape and the same compliance gates (10DLC, opt-in, the-shield). Drift between MCP and REST is a bug.

Messaging

messages.sendSMS, WhatsApp, or RCS via the v3 pipeline
messages.getsingle-message lookup by id
messages.activities.listlifecycle timeline (queued → delivered)

Contacts

contacts.listpaginated, search + channel filter
contacts.getsingle contact by id
contacts.create_manybulk-add by E.164 number
contacts.deletesoft delete
contacts.message_summaryaggregates + per-channel success

Templates

templates.listpaginated; status / category filters
templates.get
templates.get_by_name
templates.deletesoft delete

Lookup & analytics

numbers.lookupcarrier, line type, ported, country
dashboard.messages_senthourly counts for last 24h
dashboard.deliverabilitydelivered / total ratio
dashboard.contactstotal contact count

Account

account.getid, type, name, parent org, created
balance.getread-only; agents cannot credit
onboarding.statuslatest conversion-flow status

How authentication works

Your client registers itself with Sent over RFC 7591 Dynamic Client Registration.
It opens an OAuth 2.1 authorization request with PKCE (S256).
Sent redirects you to app.sent.dm/mcp-authorization — pick an organization or sender profile and either reuse an existing API key or mint a fresh one.
The access token your client receives is the API key value — the same identity that authenticates your REST calls.

No refresh tokens. No expiry. Revocation = deactivate the key in the dashboard.