What is a sender ID and why do I need one?

A sender ID is the alphanumeric label (3-11 characters) that appears as the sender on the recipient's phone. Approved sender IDs help increase trust and open rates for your messages.

Can I receive replies to my SMS messages?

Yes! Use the `list_responses` tool to retrieve any incoming messages from your customers. This allows your agent to handle two-way communication workflows.

How do I ensure my SMS is delivered at a specific time?

When using the `send_sms` tool, provide a YYYY-MM-DD HH:MM:SS string in the `date` parameter. AvoSMS will queue the message and deliver it exactly at the requested time.

AvoSMS MCP Server for CrewAI 11 tools — connect in under 2 minutes

Name: AvoSMS
Availability: InStock
Author: Vinkius

docs.crewai.com/mcp/overview

Built by Vinkius GDPR 11 Tools Framework

Connect your CrewAI agents to AvoSMS through Vinkius, pass the Edge URL in the `mcps` parameter and every AvoSMS 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="AvoSMS Specialist",
    goal="Help users interact with AvoSMS effectively",
    backstory=(
        "You are an expert at leveraging AvoSMS 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 AvoSMS "
        "and summarize their capabilities."
    ),
    agent=agent,
    expected_output=(
        "A detailed summary of 11 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 AvoSMS MCP Server

Orchestrate your global mobile communication with AvoSMS, the high-performance messaging platform designed for scale. By connecting AvoSMS to your AI agent, you transform SMS outreach from a manual task into a natural conversation. Your agent can now send instant notifications, schedule future broadcasts, manage approved sender identities, and audit your contact lists without you ever touching a dashboard. Whether you're tracking customer responses or monitoring credit balances, your agent acts as a real-time mobile operations manager for your business.

When paired with CrewAI, AvoSMS becomes a first-class tool in your multi-agent workflows. Each agent in the crew can call AvoSMS 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

Precision Messaging — Send individual or scheduled SMS messages globally with full support for custom delivery timestamps.
Identity Control — Request, list, and manage approved Sender IDs (names) to ensure your brand is always recognized.
Contact Orchestration — Create and manage dedicated contact lists, adding recipients dynamically via natural language.
Response Auditing — Retrieve and list incoming SMS responses to maintain a two-way dialogue with your audience.
Account Health — Instantly check your remaining credit balance and verify account connectivity on the fly.

The AvoSMS MCP Server exposes 11 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 AvoSMS to CrewAI via MCP

Follow these steps to integrate the AvoSMS 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 11 tools from AvoSMS

Why Use CrewAI with the AvoSMS MCP Server

CrewAI Multi-Agent Orchestration Framework provides unique advantages when paired with AvoSMS 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

AvoSMS + CrewAI Use Cases

Practical scenarios where CrewAI combined with the AvoSMS MCP Server delivers measurable value.

Automated multi-step research: a reconnaissance agent queries AvoSMS 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 AvoSMS, analyzes trends over time, and generates executive briefings in markdown or PDF format

Multi-source enrichment pipelines: chain AvoSMS 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 AvoSMS against predefined policy rules, generates deviation reports, and routes findings to the appropriate team

AvoSMS MCP Tools for CrewAI (11)

These 11 tools become available when you connect AvoSMS to CrewAI via MCP:

add_contact

Add a contact to a list

create_list

Create a new contact list

create_sender

Request a new sender ID

delete_list

Delete a contact list

delete_sender

Delete a sender ID

get_account_check

Verify AvoSMS account connection

get_balance

Check remaining SMS credits balance

list_lists

List all contact lists

list_responses

List incoming SMS responses

list_senders

List all approved sender IDs

send_sms

Send an SMS message

Example Prompts for AvoSMS in CrewAI

Ready-to-use prompts you can give your CrewAI agent to start working with AvoSMS immediately.

"Send an SMS to +33600000000 saying 'Your order is ready for pickup!' using sender 'ShopAlert'."

"Check my AvoSMS credit balance and list recent replies."

"Add the phone number +123456789 to my 'VIP Customers' list."

Troubleshooting AvoSMS MCP Server with CrewAI

Common issues when connecting AvoSMS 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.

AvoSMS + CrewAI FAQ

Common questions about integrating AvoSMS 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.