Skip to main content
@senddio/mcp-server · live

Let Claude send messages on your behalf in 30 seconds.

The Senddio MCP server gives Claude five safe, well-typed tools — for sending, checking status, listing recent messages, reading replies, and pulling stats. One command in your terminal, an agent-scoped key with limits you set, and Claude can do anything you can do with messaging on Senddio. Every action is audited under the agent's name in your dashboard.

Get an agent key See the 7 tools
● Free forever · No card · All 6 channels · AI credits
~/Library/Application Support/Claude/claude_desktop_config.json
MCP · stdio
{
  "mcpServers": {
    "senddio": {
      "command": "npx",
      "args": ["-y", "@senddio/mcp-server"],
      "env": {
        "SENDDIO_API_KEY": "sdo_mcp_…"
      }
    }
  }
}
How it works

Claude, on your account, with your permission.

The whole point of MCP is to let an agent do what you do — safely. Here's what that actually means in plain English. No protocol theory. No prompt engineering.

01
Step 01
You connect Claude to Senddio.
One command in your terminal. Claude Desktop reloads. The link between Claude and your sending account is now open.
02
Step 02
Claude learns to send.
Suddenly Claude knows how to email, SMS, ping Slack, reply on WhatsApp — the same things you can do, with the same care.
03
Step 03
You hand Claude its own key.
Not your dev key. A separate one, with the limits you set. Which channels it can touch. How much it can spend. When the key stops working.
04
Step 04
You stay in control.
Every message Claude sends shows up in your dashboard, labeled by name. You can audit, throttle, pause or revoke — without a deploy.

Every send labelled. Every key scoped. Every action reversible.

The shift

Stop hand-writing a custom tool every time you give Claude something new to do.

  • No more brittle prompts trying to make Claude send mail correctly.
  • No more custom tool definitions copy-pasted between projects.
  • No more agents using your production key by mistake.
  • No more “why did Claude just send 200 emails?” mornings.

Pre-built tools. Audited by agent. Always under your control.

Beyond the obvious

Whatever you would ask a teammate to send, you can ask Claude.

These are the kinds of things real teams already have Claude doing through Senddio. Your team will dream up more next month.

Apology email when an order is lateOvernight ticket summary, posted to Slack at 9amOn-call alert when an anomaly is detectedWeekly investor update drafted in your voiceWhatsApp replies in sixteen languagesFriday deploy digest sent to #engineeringWelcome SMS to a new sign-upAppointment booked and confirmed by chatSlack ping to finance when MRR crosses a milestoneFirst-line support response after hoursFeature release announced across every channelApology email when an order is lateOvernight ticket summary, posted to Slack at 9amOn-call alert when an anomaly is detectedWeekly investor update drafted in your voiceWhatsApp replies in sixteen languagesFriday deploy digest sent to #engineeringWelcome SMS to a new sign-upAppointment booked and confirmed by chatSlack ping to finance when MRR crosses a milestoneFirst-line support response after hoursFeature release announced across every channel
Quiet trial-user nudge on day sixPhone alert when a payment fails twiceDM to prospects who replied to the sequenceTelegram broadcast to your communityDaily standup wrapped into one email"Is the office open today?" replyDeal update pushed to your iOS appInbound Slack questions answered with KB contextMulti-channel product launch coordinated end to endContract reminder sent to legalDev paged the moment a build fails on mainQuiet trial-user nudge on day sixPhone alert when a payment fails twiceDM to prospects who replied to the sequenceTelegram broadcast to your communityDaily standup wrapped into one email"Is the office open today?" replyDeal update pushed to your iOS appInbound Slack questions answered with KB contextMulti-channel product launch coordinated end to endContract reminder sent to legalDev paged the moment a build fails on main
The thing your team will dream up next.
If you can describe it in one sentence, Claude can already send it.
Read the docs →
Under the hood

Claude calls the tool. Senddio sends it.

MCP runs the server as a local stdio process. Claude asks the model to invoke a tool, the server forwards an authenticated POST to /v1/send, the response flows back. Your agent key controls everything — channel scope, IP allowlist, expiry.

  • Local stdio process — no network ingress on your side
  • Strongly-typed tool schemas with Zod-style validation
  • Auto-retries on 5xx with exponential backoff
  • Agent-name baked into every send for clean audit
  • Works with Claude Desktop, Claude Code, and the SDK
Claude · in conversation
tool · senddio_send
User → "Ping #ops that build #2974 shipped."

Claude → calls send_message({
  channel: "slack",
  to:      ["C0123456789"],
  body:    "build #2974 → prod ✓"
})

← { id: "sdo_msg_…", status: "queued" }

Claude → "Queued. Check message status for delivery.
          Logs tagged agent=claude."
The toolbelt

Five tools, one envelope.

ToolDescriptionInputReturns
send_messageSend on a configured channel.{ channel, to: string[], body, from?, subject?, title? }Message ID and queued status
get_message_statusFetch status and events.{ message_id }Message summary and events
list_recent_messagesList message history.{ channel?, status?, since?, limit? }Messages and next cursor
list_inbound_messagesRead supported inbound replies.{ channel?, thread?, since?, limit? }Inbound messages and next cursor
get_delivery_statsAggregate delivery metrics.{ period: "24h" | "7d" | "30d", channel? }Totals, rates and channel breakdown
Suggested integration milestones

Your first 30 days with Claude on the wire.

01
Day 1
MCP server installed, Claude can send
02
Day 3
Agent-scoped key replacing your dev key
03
Week 1
Three tools in genuine production use
04
Day 30
Agents running unattended on real workloads
●Every milestone above ships on the Free plan. No card, no upgrade gate.
FAQ

Claude MCP — FAQ

MCP, the Model Context Protocol, is Anthropic's open standard for letting Claude desktop and IDE clients use external tools safely. Senddio ships a first-class MCP server so any Claude instance can send a message, check a status, or read inbound replies the moment you connect the config.

Yes, but it stays separate from yours. You create an agent-scoped key in the dashboard — with the channels it can use, the IP addresses it can call from, and an expiry date — and add it to the MCP server's environment. Every message Claude sends is labelled with the agent name, audited, and rate-limited on its own.

Yes. The server is published on npm as @senddio/mcp-server under a permissive licence, with the source available on GitHub. Review release notes and test your client configuration before upgrading.

Yes. MCP is a wire protocol, so any MCP-compatible client can load the Senddio server — Clients supporting local stdio MCP servers can load it. Hosted clients need an appropriate remote bridge. For ChatGPT and other OpenAI assistants, use our OpenAI tools package instead.

Agent sends count against your plan's allowance just like any human send — there is no premium for being an agent. Your dashboard splits agent traffic from human traffic so you can see exactly what your AI is doing and what it costs.

See also
OpenAI tools
Function-calling JSON schemas
AI features
Insights · templates · anomaly
Email channel
What the agent will send most

Your Claude is five minutes from sending real messages.

Free plan gives you 20 AI credits and full agent-scoped key features.

Get your agent key Read the docs
● 300 emails/day · All 6 channels · AI credits · No card