How do I find my SMSMobileAPI Key?

Log in to the [**SMS Mobile API web dashboard**](https://smsmobileapi.com/dashboard) or open the Android app and navigate to the Settings or Help section to find your unique API Key.

INSTANT PLUG AND PLAY

SMS Mobile API MCP Server for CrewAIGive CrewAI instant access to 11 tools to Get Account Info, Get Delivery Status, Get Device, and more

Name: SMS Mobile API
Availability: InStock
Author: Vinkius

Built by Vinkius GDPR 11 Tools Framework

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

Use with Your AI Agent

Ask AI about this App Connector for CrewAI

Open in ChatGPT Open in Claude Open in Perplexity

The SMS Mobile API app connector for CrewAI is a standout in the Industry Titans category — giving your AI agent 11 tools to work with, ready to go from day one.

Vinkius delivers Streamable HTTP and SSE to any MCP client

python

from crewai import Agent, Task, Crew

agent = Agent(
    role="SMS Mobile API Specialist",
    goal="Help users interact with SMS Mobile API effectively",
    backstory=(
        "You are an expert at leveraging SMS Mobile API 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 SMS Mobile API "
        "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 SMS Mobile API MCP Server

Connect your SMS Mobile API account to any AI agent to automate your mobile messaging and device orchestration. SMS Mobile API turns your Android phone into a powerful messaging gateway, and this integration allows you to send SMS, manage WhatsApp communications, and track missed calls through natural conversation.

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

Messaging Orchestration — Send instant SMS and WhatsApp messages using your own mobile number and data plan programmatically.
Device & Gateway Control — List and monitor your connected Android devices to ensure your messaging gateway is always online.
Incoming Communication Tracking — Retrieve received SMS messages and list missed calls to keep your conversational threads synchronized directly from the AI interface.
Multi-Port Support — Manage messaging across different device ports and gateways to maintain high delivery rates via natural language.
Operational Monitoring — Track message delivery status and monitor device connectivity to ensure reliable customer outreach.

The SMS Mobile API 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.

All 11 SMS Mobile API tools available for CrewAI

When CrewAI connects to SMS Mobile API through Vinkius, your AI agent gets direct access to every tool listed below — spanning android-gateway, whatsapp-automation, mobile-messaging, and more. Every call is secured with network, filesystem, subprocess, and code evaluation entitlements inside a sandboxed runtime. Beyond a simple connection, you get a full AI Gateway with real-time visibility into agent activity, enterprise governance, and optimized token usage.

get_account_info

Get account information and usage statistics

get_delivery_status

Get delivery status for a sent message

get_device

Get details for a specific connected device

get_received_sms

Get incoming SMS messages

list_connected_devices

List connected mobile gateways

list_contacts

List all saved contacts

list_missed_calls

List missed calls log

list_sent_messages

List all sent messages

send_mms

Send an MMS message with media attachment

send_sms

Send SMS from your phone

send_whatsapp

Send WhatsApp from your phone

Connect SMS Mobile API to CrewAI via MCP

Follow these steps to wire SMS Mobile API into CrewAI. The entire setup takes under two minutes — your credentials stay safe behind the Vinkius.

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 SMS Mobile API

Why Use CrewAI with the SMS Mobile API MCP Server

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

SMS Mobile API + CrewAI Use Cases

Practical scenarios where CrewAI combined with the SMS Mobile API MCP Server delivers measurable value.

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

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

Example Prompts for SMS Mobile API in CrewAI

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

"Send an SMS to +1234567890: 'Your order is ready for pickup!'."

"Send an SMS notification to all customers about our system maintenance window tonight."

"Show me all received SMS messages and missed calls from the last 48 hours."

Troubleshooting SMS Mobile API MCP Server with CrewAI

Common issues when connecting SMS Mobile API 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.

SMS Mobile API + CrewAI FAQ

Common questions about integrating SMS Mobile API 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.