AT&T Messaging MCP Server
CPaaS Messaging -- Send SMS/MMS, manage shortcodes, track delivery status, and run bulk campaigns via AT&T Messaging API.
Ask AI about this MCP Server
Vinkius supports streamable HTTP and SSE.

* Every MCP server runs on Vinkius-managed infrastructure inside AWS - a purpose-built runtime with per-request V8 isolates, Ed25519 signed audit chains, and sub-40ms cold starts optimized for native MCP execution. See our infrastructure
What is the AT&T Messaging MCP Server?
The AT&T Messaging MCP Server gives AI agents like Claude, ChatGPT, and Cursor direct access to AT&T Messaging via 9 tools. CPaaS Messaging -- Send SMS/MMS, manage shortcodes, track delivery status, and run bulk campaigns via AT&T Messaging API. Powered by the Vinkius - no API keys, no infrastructure, connect in under 2 minutes.
Built-in capabilities (9)
Tools for your AI Agents to operate AT&T Messaging
Ask your AI agent "Send an SMS from shortcode 12345 to +12125551234 saying 'Your order #48291 has shipped! Track it at example.com/track'." and get the answer without opening a single dashboard. With 9 tools connected to real AT&T Messaging data, your agents reason over live information, cross-reference it with other MCP servers, and deliver insights you would spend hours assembling manually.
Works with Claude, ChatGPT, Cursor, and any MCP-compatible client. Powered by the Vinkius - your credentials never touch the AI model, every request is auditable. Connect in under two minutes.
Why teams choose Vinkius
One subscription gives you access to thousands of MCP servers - and you can deploy your own to the Vinkius Edge. Your AI agents only access the data you authorize, with DLP that blocks sensitive information from ever reaching the model, kill switch for instant shutdown, and up to 60% token savings. Enterprise-grade infrastructure and security, zero maintenance.
Build your own MCP Server with our secure development framework →Vinkius works with every AI agent you already use
…and any MCP-compatible client


















AT&T Messaging MCP Server capabilities
9 toolsReturns provisioning status and activation timeline. Use for new marketing campaigns or service alerts. Provision a new messaging shortcode with a keyword
Use when retiring a campaign or transferring numbers. Decommission a messaging shortcode
Returns sender number, keyword matched, message body, and timestamp. Use for monitoring customer engagement or processing STOP/START commands. Retrieve recent inbound SMS/MMS from customers
Use to review campaign logic or verify opt-in/opt-out flows. Get configured auto-replies for shortcode keywords
Use to track campaign performance or debug failed sends. Check delivery status of a specific message
Returns timestamps, sender, recipient, and content snippets. Use for auditing, compliance reporting, or reply tracking. List outbound or inbound messaging history
164 numbers. Returns job ID and per-recipient status array. Use for mass alerts, emergency broadcasts, or promotional campaigns. Send SMS to multiple recipients in one request
Requires sender, recipient, message text, and media URL. Use for rich marketing campaigns, product images, or visual alerts. Send an MMS message with media attachment
Requires sender ID, recipient E.164 number, and message body. Returns message ID and delivery status. Use this for transactional alerts, OTPs, or customer notifications. Send a single SMS message to a phone number
What the AT&T Messaging MCP Server unlocks
Connect your AT&T Messaging account to any AI agent and take full control of your SMS/MMS communication workflows through natural conversation.
What you can do
- SMS Messaging -- Send transactional alerts, OTPs, and customer notifications from registered shortcodes with delivery tracking
- MMS Messaging -- Attach images, videos, or audio to enrich marketing campaigns and visual alerts
- Bulk Send -- Broadcast the same message to hundreds of recipients in one request with per-recipient status tracking
- Delivery Status -- Check real-time delivery state (sent, delivered, failed, read) for any message by its ID
- Message History -- Query outbound and inbound message logs for auditing, compliance reporting, or reply tracking
- Inbound Messages -- Retrieve customer replies, opt-outs, and keyword-triggered auto-responses
- Shortcode Management -- Provision new shortcodes with keywords for campaign routing, or decommission retired numbers
- Keyword Responses -- Review configured auto-reply logic for shortcode keywords to verify opt-in/opt-out flows
How it works
1. Subscribe to this server
2. Enter your AT&T Messaging API Key and API Secret
3. Start sending messages and managing campaigns from Claude, Cursor, or any MCP-compatible client
No more bouncing between the AT&T Messaging dashboard and your CRM. Your AI agent becomes your messaging command center.
Who is this for?
- Marketing Teams -- launch SMS/MMS campaigns, monitor keyword engagement, and manage shortcodes for different brands
- DevOps Engineers -- trigger mass alert broadcasts, track delivery rates, and debug failed sends
- Customer Support -- review inbound customer messages, process STOP/START commands, and send order updates
- Compliance Officers -- audit full message history with timestamps, directions, and content snippets
Frequently asked questions about the AT&T Messaging MCP Server
What sender IDs can I use to send SMS messages?
You must use a registered AT&T shortcode or dedicated long code as the sender ID. Unregistered or random numbers will be rejected by the carrier. You can provision new shortcodes with keywords using the create_shortcode tool, or check your existing ones through the messaging dashboard. Each shortcode can be configured with multiple keyword auto-responses.
Can I send MMS with images and what formats are supported?
Yes. The send_mms tool accepts a publicly accessible media URL. Supported formats include JPEG, PNG, GIF for images, MP4 for video, and common audio formats. The media URL must be reachable by AT&T's servers -- local or private URLs will fail. Maximum file size limits apply per carrier specifications, typically up to 1MB for images and 3.5MB for video.
How do I handle customer opt-out requests like STOP?
AT&T Messaging automatically processes standard opt-out keywords (STOP, CANCEL, UNSUBSCRIBE, QUIT). When a customer sends one of these, they are added to your suppression list and will no longer receive messages from that shortcode. You can monitor inbound messages with get_inbound_messages to track opt-out activity and verify your keyword configuration with get_keyword_responses.
More in this category
You might also like
Connect AT&T Messaging with your favorite client
Step-by-step setup guides for every MCP-compatible client and framework:
Anthropic's native desktop app for Claude with built-in MCP support.
AI-first code editor with integrated LLM-powered coding assistance.
GitHub Copilot in VS Code with Agent mode and MCP support.
Purpose-built IDE for agentic AI coding workflows.
Autonomous AI coding agent that runs inside VS Code.
Anthropic's agentic CLI for terminal-first development.
Python SDK for building production-grade OpenAI agent workflows.
Google's framework for building production AI agents.
Type-safe agent development for Python with first-class MCP support.
TypeScript toolkit for building AI-powered web applications.
TypeScript-native agent framework for modern web stacks.
Python framework for orchestrating collaborative AI agent crews.
Leading Python framework for composable LLM applications.
Data-aware AI agent framework for structured and unstructured sources.
Microsoft's framework for multi-agent collaborative conversations.
Give your AI agents the power of AT&T Messaging MCP Server
Production-grade AT&T Messaging MCP Server. Verified, monitored, and maintained by Vinkius. Ready for your AI agents — connect and start using immediately.






