Bring Interoperability
to Mastra AI
Learn how to connect Mio to Mastra AI 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 Mio MCP Server?
Connect your Mio account to any AI agent and manage automated phone calls through natural conversation.
What you can do
- Outbound Calls — Start AI-powered phone calls with custom scripts and instructions
- Call Logs — Browse call history with status, duration, and outcomes
- Transcripts — Retrieve full text transcriptions of completed calls
- AI Summaries — Get AI-generated summaries and extracted data from calls
- Voice Selection — Choose from multiple neural voices for the AI agent
- Webhooks — Configure event notifications for call status changes
- Call Control — Terminate active calls in real time
- Account — Check credit balance and account information
How it works
1. Subscribe to this server
2. Enter your Mio API Key
3. Start making AI calls from Claude, Cursor, or any MCP-compatible client
Who is this for?
- Sales Teams — automate outbound prospecting calls with AI agents
- Customer Service — deploy AI voice agents for appointment confirmations
- Developers — build voice-first AI applications with call transcripts
Built-in capabilities (12)
Add new notification
Remove a webhook
Get user profile
Get specific call info
Get AI call summary
Get call text log
Check account funds
List AI voices
List all call logs
Get active webhooks
Start an AI phone call
Stop active call
Why Mastra AI?
Mastra's agent abstraction provides a clean separation between LLM logic and Mio tool infrastructure. Connect 12 tools through Vinkius and use Mastra's built-in workflow engine to chain tool calls with conditional logic, retries, and parallel execution. deployable to any Node.js host in one command.
- —
Mastra's agent abstraction provides a clean separation between LLM logic and tool infrastructure. add Mio without touching business code
- —
Built-in workflow engine chains MCP tool calls with conditional logic, retries, and parallel execution for complex automation
- —
TypeScript-native: full type inference for every Mio tool response with IDE autocomplete and compile-time checks
- —
One-command deployment to any Node.js host. Vercel, Railway, Fly.io, or your own infrastructure
Mio in Mastra AI
Mio and 3,400+ other MCP servers. One platform. One governance layer.
Teams that connect Mio to Mastra AI 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 Mio in Mastra AI
The Mio 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 Mastra AI 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
Mio for Mastra AI
Every tool call from Mastra AI to the Mio MCP Server is protected by DLP redaction, cryptographic audit chains, V8 sandbox isolation, kill switch, and financial circuit breakers.
Frequently asked questions
Can I start an automated AI phone call?
Yes. Provide a phone number, instructions for the AI agent, and optionally select a voice. Mio will call and follow the script autonomously.
How does Mio authentication work?
Mio requires an API Key sent via the X-API-Key header against api.mio.gg/api/v1.
Can I get transcripts and AI summaries?
Yes. After a call completes, retrieve the full text transcript and an AI-generated summary with extracted data points.
How does Mastra AI connect to MCP servers?
Create an MCPClient with the server URL and pass it to your agent. Mastra discovers all tools and makes them available with full TypeScript types.
Can Mastra agents use tools from multiple servers?
Yes. Pass multiple MCP clients to the agent constructor. Mastra merges all tool schemas and the agent can call any tool from any server.
Does Mastra support workflow orchestration?
Yes. Mastra has a built-in workflow engine that lets you chain MCP tool calls with branching logic, error handling, and parallel execution.
createMCPClient not exported
Install: npm install @mastra/mcp