Bring Cloud Telephony
to CrewAI
Learn how to connect TextGrid to CrewAI and start using 12 AI agent tools in minutes. Fully managed, enterprise secure, and ready to use without writing a single line of code.
What is the TextGrid MCP Server?
Connect your TextGrid account to any AI agent and simplify how you manage your cloud telephony, global messaging, and communication logs through natural conversation.
What you can do
- Global Messaging — Send instant SMS and MMS messages to recipients worldwide with full status tracking.
- Voice Call Control — Initiate outbound voice calls and retrieve a complete history of inbound and outbound communication.
- Phone Number Management — List your active numbers and search for new available phone numbers across different countries.
- Usage & Cost Tracking — Retrieve detailed usage statistics and records to monitor your communication budget.
- Account Oversight — Fetch account metadata, API keys, and physical addresses for regulatory compliance.
- Operational Monitoring — Check API health and verify connectivity directly from the agent.
How it works
1. Subscribe to this server
2. Enter your TextGrid Account SID and Auth Token (found in your account dashboard)
3. Start managing your cloud communications from Claude, Cursor, or any MCP client
Who is this for?
- Developers & DevOps — quickly test SMS delivery and initiate voice calls via simple AI commands.
- Customer Support Teams — retrieve message histories and verify delivery statuses directly from the workspace.
- Operations Managers — monitor usage costs and manage phone number inventory via the AI assistant.
Built-in capabilities (12)
Verify Textgrid API status
Get account profile and balance
Get details for a specific message
Retrieve usage and cost records
Start a new voice call
List addresses for regulatory compliance
List your active phone numbers
List account API keys
List sent and received SMS messages
List voice call history
Search for new phone numbers
Send a new SMS or MMS
Why CrewAI?
When paired with CrewAI, TextGrid becomes a first-class tool in your multi-agent workflows. Each agent in the crew can call TextGrid tools autonomously, one agent queries data, another analyzes results, a third compiles reports, all orchestrated through Vinkius with zero configuration overhead.
- —
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
mcpsparameter 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
TextGrid in CrewAI
TextGrid and 3,400+ other MCP servers. One platform. One governance layer.
Teams that connect TextGrid to CrewAI through Vinkius don't need to source, host, or maintain individual MCP servers. Every tool call runs inside a hardened runtime with credential isolation, DLP, and a signed audit chain.
Raw MCP | Vinkius | |
|---|---|---|
| Server catalog | Find and host yourself | 3,400+ managed |
| Infrastructure | Self-hosted | Sandboxed V8 isolates |
| Credential handling | Plaintext in config | Vault + runtime injection |
| Data loss prevention | None | Configurable DLP policies |
| Kill switch | None | Global instant shutdown |
| Financial circuit breakers | None | Per-server limits + alerts |
| Audit trail | None | Ed25519 signed logs |
| SIEM log streaming | None | Splunk, Datadog, Webhook |
| Honeytokens | None | Canary alerts on leak |
| Custom domains | Not applicable | DNS challenge verified |
| GDPR compliance | Manual effort | Automated purge + export |
Why teams choose Vinkius for TextGrid in CrewAI
The TextGrid 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. All 12 tools execute in hardened sandboxes optimized for native MCP execution.
Your AI agents in CrewAI 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, zero maintenance.
* 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
How Vinkius secures
TextGrid for CrewAI
Every tool call from CrewAI to the TextGrid MCP Server is protected by DLP redaction, cryptographic audit chains, V8 sandbox isolation, kill switch, and financial circuit breakers.
Frequently asked questions
Can I check the delivery status of a specific message via AI?
Yes! Use the get_message_details tool and provide the Message SID. Your agent will retrieve the real-time delivery status (e.g., sent, delivered, failed) and other metadata.
How do I find a new available phone number in the US?
Run the search_available_numbers query and set the countryCode parameter to 'US'. The agent will return a list of phone numbers available for purchase in that region.
Is it possible to see the costs associated with my messaging usage?
Absolutely. Use the get_usage_statistics tool to retrieve detailed usage records and associated costs for your SMS and voice services directly from TextGrid.
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.
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.