What exactly is audioMCP.ai?
audioMCP.ai is a Model Context Protocol (MCP) server in the category of agentic voice infrastructure. It gives any AI agent the ability to build and deploy a production voice agent through MCP tool calls, making voice a callable primitive rather than a build project. The product handles telephony, speech-to-text (STT), text-to-speech (TTS), turn-taking, barge-in, and latency management. You retain control of conversation intent, prompts, tools, and business logic.
How is audioMCP.ai different from Vapi, Retell, or Bland?
Compared with other voice platforms, including Vapi, Retell, or Bland, the core difference is who does the building: with audioMCP.ai, the AI agent builds and deploys voice agents through tool calls rather than a human developer wiring the stack by hand. The difference is not a feature list. It is who does the work. If your stack already uses an MCP-compatible client or agent framework, audioMCP.ai drops in as a first-class tool and the agent handles provisioning and deployment directly. audioMCP.ai removes the build.
How does it work?
The process follows four MCP tool calls. First, the AI agent calls Provision, which allocates telephony and speech infrastructure instantly. Second, it calls Configure, setting voice, prompt, tools, and routing in plain language or structured parameters. Third, it calls Deploy, which takes the agent live on a phone number, in-app channel, or workflow trigger. Fourth, it calls Observe, which streams transcripts, call outcomes, and metadata back to the agent so it can act on what happened. Four calls from idea to live call.
Do I need to learn MCP to use this?
If your stack already uses an MCP-compatible client or agent framework, audioMCP.ai drops in as a first-class tool with low additional integration lift. The product is built specifically for teams already working inside the MCP ecosystem. Teams whose stacks do not use MCP-compatible clients or agent frameworks are outside the current scope of audioMCP.ai.
What calling capabilities does audioMCP.ai support?
audioMCP.ai supports both inbound and outbound calling. Inbound lines can be auto-provisioned with escalation rules for support use cases. Outbound calls can be triggered from a backend event with no human in the loop. The product also supports in-product voice, which lets a company embed a branded voice assistant scoped to its own data and tools. During any live call, the voice agent can invoke tools such as a calendar or CRM mid-conversation, not just follow a fixed script. Barge-in handling lets callers interrupt the agent naturally.
What does audioMCP.ai handle, and what do I stay responsible for?
audioMCP.ai owns telephony, STT, TTS, turn-taking, barge-in handling, scaling, and latency management. You own conversation intent, prompts, tools, and business logic. This division is the product's stated abstraction boundary. You own the conversation. audioMCP.ai runs the stack.
Can my agent legally place outbound calls?
audioMCP.ai is designed for outbound workflows, but production use requires consent, verification, rate limits, and customer compliance controls. Compliance responsibility is shared between audioMCP.ai and the customer, and it is not fully handled by the platform alone. The demo backend ships only with verification and rate limiting in place. Customers should review their own consent and compliance obligations before placing outbound calls in production.
How is audioMCP.ai priced?
Pricing is usage-based, billed per minute of call time. There are no seat costs. There are three tiers. The Developer tier, called launch access, includes API key access, MCP tool setup, and a sandbox demo flow for building and testing. The Scale tier is the all-inclusive pilot rate, covering telephony, STT, TTS, and infrastructure with no hidden fees, and includes production call scope, usage reporting, and observability hooks. The Enterprise tier offers custom volume pricing, SLA review, security review, and dedicated support. Enterprise pricing is custom and set through direct conversation.
Is audioMCP.ai production-ready right now?
audioMCP.ai is in a pre-launch, early access stage. The Developer tier provides sandbox access for building and testing. The live demo backend ships only after verification, rate limits, and sandboxing are confirmed. The site does not yet have customer logos, testimonials, or live production telemetry to share. The team is transparent about this. Security and privacy obligations related to voice data are identified in the Privacy and Terms documents.
How do I get started or talk to the team?
Developers can start by getting an API key, which gives access to the Developer tier for sandbox testing. Teams evaluating for production or enterprise use can book a technical demo or talk to an engineer directly. The entry point for self-serve is the API key. The entry point for higher-volume or compliance-sensitive deployments is a conversation with the engineering team.