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`.

AT&T Messaging MCP Server for CrewAI 9 tools — connect in under 2 minutes

Name: AT&T Messaging
Availability: InStock
Author: Vinkius

docs.crewai.com/mcp/overview

Built by Vinkius GDPR 9 Tools Framework

Connect your CrewAI agents to AT&T Messaging through Vinkius, pass the Edge URL in the `mcps` parameter and every AT&T Messaging tool is auto-discovered at runtime. No credentials to manage, no infrastructure to maintain.

Get MCP Server for AI Agents

ASK AI ABOUT THIS MCP SERVER

Open in ChatGPT Open in Claude Open in Perplexity

Vinkius supports streamable HTTP and SSE.

python

from crewai import Agent, Task, Crew

agent = Agent(
    role="AT&T Messaging Specialist",
    goal="Help users interact with AT&T Messaging effectively",
    backstory=(
        "You are an expert at leveraging AT&T Messaging tools "
        "for automation and data analysis."
    ),
    # Your Vinkius token. get it at cloud.vinkius.com
    mcps=["https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp"],
)

task = Task(
    description=(
        "Explore all available tools in AT&T Messaging "
        "and summarize their capabilities."
    ),
    agent=agent,
    expected_output=(
        "A detailed summary of 9 available tools "
        "and what they can do."
    ),
)

crew = Crew(agents=[agent], tasks=[task])
result = crew.kickoff()
print(result)

Fully ManagedVinkius Servers

60%Token savings

High SecurityEnterprise-grade

IAMAccess control

EU AI ActCompliant

DLPData protection

V8 IsolateSandboxed

Ed25519Audit chain

<40msKill switch

Stream every event to Splunk, Datadog, or your own webhook in real-time

* 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

About AT&T Messaging MCP Server

Connect your AT&T Messaging account to any AI agent and take full control of your SMS/MMS communication workflows through natural conversation.

When paired with CrewAI, AT&T Messaging becomes a first-class tool in your multi-agent workflows. Each agent in the crew can call AT&T Messaging tools autonomously, one agent queries data, another analyzes results, a third compiles reports, all orchestrated through Vinkius with zero configuration overhead.

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

The AT&T Messaging MCP Server exposes 9 tools through the Vinkius. Connect it to CrewAI in under two minutes — no API keys to rotate, no infrastructure to provision, no vendor lock-in. Your configuration, your data, your control.

How to Connect AT&T Messaging to CrewAI via MCP

Follow these steps to integrate the AT&T Messaging MCP Server with CrewAI.

Install CrewAI

Run pip install crewai

Replace the token

Replace [YOUR_TOKEN_HERE] with your Vinkius token from cloud.vinkius.com

Customize the agent

Adjust the role, goal, and backstory to fit your use case

Run the crew

Run python crew.py. CrewAI auto-discovers 9 tools from AT&T Messaging

Why Use CrewAI with the AT&T Messaging MCP Server

CrewAI Multi-Agent Orchestration Framework provides unique advantages when paired with AT&T Messaging through the Model Context Protocol.

Multi-agent collaboration lets you decompose complex workflows into specialized roles, one agent researches, another analyzes, a third generates reports, each with access to MCP tools

CrewAI's native MCP integration requires zero adapter code: pass Vinkius Edge URL directly in the `mcps` parameter and agents auto-discover every available tool at runtime

Built-in task delegation and shared memory mean agents can pass context between steps without manual state management, enabling multi-hop reasoning across tool calls

Sequential and hierarchical crew patterns map naturally to real-world workflows: enumerate subdomains → analyze DNS history → check WHOIS records → compile findings into actionable reports

AT&T Messaging + CrewAI Use Cases

Practical scenarios where CrewAI combined with the AT&T Messaging MCP Server delivers measurable value.

Automated multi-step research: a reconnaissance agent queries AT&T Messaging for raw data, then a second analyst agent cross-references findings and flags anomalies. all without human handoff

Scheduled intelligence reports: set up a crew that periodically queries AT&T Messaging, analyzes trends over time, and generates executive briefings in markdown or PDF format

Multi-source enrichment pipelines: chain AT&T Messaging tools with other MCP servers in the same crew, letting agents correlate data across multiple providers in a single workflow

Compliance and audit automation: a compliance agent queries AT&T Messaging against predefined policy rules, generates deviation reports, and routes findings to the appropriate team

AT&T Messaging MCP Tools for CrewAI (9)

These 9 tools become available when you connect AT&T Messaging to CrewAI via MCP:

create_shortcode

Returns provisioning status and activation timeline. Use for new marketing campaigns or service alerts. Provision a new messaging shortcode with a keyword

delete_shortcode

Use when retiring a campaign or transferring numbers. Decommission a messaging shortcode

get_inbound_messages

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

get_keyword_responses

Use to review campaign logic or verify opt-in/opt-out flows. Get configured auto-replies for shortcode keywords

get_message_status

Use to track campaign performance or debug failed sends. Check delivery status of a specific message

list_messages

Returns timestamps, sender, recipient, and content snippets. Use for auditing, compliance reporting, or reply tracking. List outbound or inbound messaging history

send_bulk_sms

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

send_mms

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

send_sms

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

Example Prompts for AT&T Messaging in CrewAI

Ready-to-use prompts you can give your CrewAI agent to start working with AT&T Messaging immediately.

"Send an SMS from shortcode 12345 to +12125551234 saying 'Your order #48291 has shipped! Track it at example.com/track'."

"Send a bulk SMS to all these numbers: +12125551001, +12125551002, +12125551003 with the message 'Flash Sale: 50% off everything for the next 2 hours!'."

"Show me all inbound messages from the last 24 hours and check if anyone sent STOP."

Troubleshooting AT&T Messaging MCP Server with CrewAI

Common issues when connecting AT&T Messaging to CrewAI through the Vinkius, and how to resolve them.

MCP tools not discovered

Ensure the Edge URL is correct. CrewAI connects lazily when the crew starts. check console output.

Agent not using tools

Make the task description specific. Instead of "do something", say "Use the available tools to list contacts".

Timeout errors

CrewAI has a 10s connection timeout by default. Ensure your network can reach the Edge URL.

Rate limiting or 429 errors

Vinkius enforces per-token rate limits. Check your subscription tier and request quota in the dashboard. Upgrade if you need higher throughput.

AT&T Messaging + CrewAI FAQ

Common questions about integrating AT&T Messaging MCP Server with CrewAI.

How does CrewAI discover and connect to MCP tools?

CrewAI connects to MCP servers lazily. when the crew starts, each agent resolves its MCP URLs and fetches the tool catalog via the standard tools/list method. This means tools are always fresh and reflect the server's current capabilities. No tool schemas need to be hardcoded.

Can different agents in the same crew use different MCP servers?

Yes. Each agent has its own mcps list, so you can assign specific servers to specific roles. For example, a reconnaissance agent might use a domain intelligence server while an analysis agent uses a vulnerability database server.

What happens when an MCP tool call fails during a crew run?

CrewAI wraps tool failures as context for the agent. The LLM receives the error message and can decide to retry with different parameters, fall back to a different tool, or mark the task as partially complete. This resilience is critical for production workflows.

Can CrewAI agents call multiple MCP tools in parallel?

CrewAI agents execute tool calls sequentially within a single reasoning step. However, you can run multiple agents in parallel using process=Process.parallel, each calling different MCP tools concurrently. This is ideal for workflows where separate data sources need to be queried simultaneously.

Can I run CrewAI crews on a schedule (cron)?

Yes. CrewAI crews are standard Python scripts, so you can invoke them via cron, Airflow, Celery, or any task scheduler. The crew.kickoff() method runs synchronously by default, making it straightforward to integrate into existing pipelines.