<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:dc="http://purl.org/dc/elements/1.1/">
  <channel>
    <title>DEV Community: Kai Viertel</title>
    <description>The latest articles on DEV Community by Kai Viertel (@kai_viertel_bc7a934c17ef0).</description>
    <link>https://dev.to/kai_viertel_bc7a934c17ef0</link>
    <image>
      <url>https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F3843278%2Fe72d3d72-ddf6-41dc-857b-b7e6d878a4d0.png</url>
      <title>DEV Community: Kai Viertel</title>
      <link>https://dev.to/kai_viertel_bc7a934c17ef0</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/kai_viertel_bc7a934c17ef0"/>
    <language>en</language>
    <item>
      <title>One REST API for 8 messaging channels: now with MCP access for AI agents</title>
      <dc:creator>Kai Viertel</dc:creator>
      <pubDate>Thu, 23 Jul 2026 16:20:05 +0000</pubDate>
      <link>https://dev.to/sendseven/one-rest-api-for-8-messaging-channels-now-with-mcp-access-for-ai-agents-4lhg</link>
      <guid>https://dev.to/sendseven/one-rest-api-for-8-messaging-channels-now-with-mcp-access-for-ai-agents-4lhg</guid>
      <description>&lt;p&gt;Every messaging channel has its own API, its own SDK, its own webhook format. Wire up WhatsApp, then SMS, then email, then Instagram… and you've built four integrations that all behave differently.&lt;/p&gt;

&lt;p&gt;We built &lt;strong&gt;SendSeven&lt;/strong&gt; so you don't have to: &lt;strong&gt;one REST API for 8 channels&lt;/strong&gt; — WhatsApp, SMS, email, Instagram, Messenger, Live Chat, Telegram and Browser Push.&lt;/p&gt;

&lt;h2&gt;
  
  
  Send on any channel
&lt;/h2&gt;



&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight shell"&gt;&lt;code&gt;curl &lt;span class="nt"&gt;-X&lt;/span&gt; POST https://api.sendseven.com/api/v1/messages &lt;span class="se"&gt;\&lt;/span&gt;
  &lt;span class="nt"&gt;-H&lt;/span&gt; &lt;span class="s2"&gt;"Authorization: Bearer &lt;/span&gt;&lt;span class="nv"&gt;$SENDSEVEN_TOKEN&lt;/span&gt;&lt;span class="s2"&gt;"&lt;/span&gt; &lt;span class="se"&gt;\&lt;/span&gt;
  &lt;span class="nt"&gt;-H&lt;/span&gt; &lt;span class="s2"&gt;"Content-Type: application/json"&lt;/span&gt; &lt;span class="se"&gt;\&lt;/span&gt;
  &lt;span class="nt"&gt;-d&lt;/span&gt; &lt;span class="s1"&gt;'{
    "channel_id": "b1f2c3d4-…",
    "to": "+4915112345678",
    "message_type": "text",
    "text": "Hi Anna! Your order #4821 has shipped."
  }'&lt;/span&gt;
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;That &lt;code&gt;channel_id&lt;/code&gt; points at one channel you connected (here a WhatsApp number). Want to send over Telegram or SMS instead? &lt;strong&gt;Change that one field.&lt;/strong&gt; Every channel gets its own id — one endpoint, one payload shape, eight channels.&lt;/p&gt;

&lt;h2&gt;
  
  
  Two-way by default: webhooks
&lt;/h2&gt;

&lt;p&gt;Sending is half the story. Every inbound message and status change is pushed to your endpoint in real time:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;code&gt;message.received&lt;/code&gt; · &lt;code&gt;message.sent&lt;/code&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;code&gt;message.delivered&lt;/code&gt; · &lt;code&gt;message.read&lt;/code&gt; · &lt;code&gt;message.failed&lt;/code&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;code&gt;channel.created&lt;/code&gt; · &lt;code&gt;channel.updated&lt;/code&gt; (health &amp;amp; alerting)&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;So you build real conversations — auto-replies, routing, your own bot — not just fire-and-forget.&lt;/p&gt;

&lt;h2&gt;
  
  
  The fun part: hand it to an AI agent over MCP
&lt;/h2&gt;

&lt;p&gt;Here's what we most want you to try: SendSeven ships an &lt;strong&gt;MCP server&lt;/strong&gt; at &lt;code&gt;mcp.sendseven.com&lt;/code&gt;. Point any MCP-compatible client — &lt;strong&gt;Claude, Cursor, your own agent&lt;/strong&gt; — at it, authorize over OAuth, and your agent can send and handle messages across every channel as a first-class tool. EU-hosted.&lt;/p&gt;

&lt;blockquote&gt;
&lt;p&gt;"Message the customer on WhatsApp that their order shipped." → your agent just does it. No glue code.&lt;/p&gt;
&lt;/blockquote&gt;

&lt;h2&gt;
  
  
  Built for people who ship
&lt;/h2&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;OpenAPI 3.0&lt;/strong&gt; spec + real-time &lt;strong&gt;webhooks&lt;/strong&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Multi-tenant Tenants API&lt;/strong&gt; — isolated workspaces per customer, ideal for embedding SendSeven into your own product&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Zapier &amp;amp; n8n&lt;/strong&gt; when you'd rather not write code&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;EU-hosted (Frankfurt), GDPR-compliant, made in Germany&lt;/strong&gt;&lt;/li&gt;
&lt;li&gt;No per-seat fees, unlimited users, inbound is free&lt;/li&gt;
&lt;/ul&gt;

&lt;h2&gt;
  
  
  Try it
&lt;/h2&gt;

&lt;p&gt;&lt;strong&gt;API Only starts at €9/channel/month&lt;/strong&gt;, with a &lt;strong&gt;14-day free trial — 100 test messages, no credit card.&lt;/strong&gt; Grab a token and send your first cross-channel message in minutes:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;📚 Docs: &lt;a href="https://docs.sendseven.com" rel="noopener noreferrer"&gt;https://docs.sendseven.com&lt;/a&gt;
&lt;/li&gt;
&lt;li&gt;🤖 MCP server: &lt;a href="https://mcp.sendseven.com" rel="noopener noreferrer"&gt;https://mcp.sendseven.com&lt;/a&gt;
&lt;/li&gt;
&lt;li&gt;🚀 Start free: &lt;a href="https://sendseven.com" rel="noopener noreferrer"&gt;https://sendseven.com&lt;/a&gt;
&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;What would you wire an AI agent up to first? Tell us in the comments — we'd love to see what you build (or break).&lt;/p&gt;

</description>
      <category>webdev</category>
      <category>ai</category>
      <category>api</category>
      <category>mcp</category>
    </item>
  </channel>
</rss>
