Speko
Give your voice agent a single MCP surface that routes STT, TTS, and voice-to-voice calls with provider failover instead of hand-rolling three SDKs.
Overview
ai.speko/mcp is an MCP server for the Build phase that routes and fails over voice AI across STT, TTS, and V2V providers for agent-driven apps.
What is this MCP server?
- Routes speech-to-text, text-to-speech, and voice-to-voice (V2V) providers
- Built-in failover across STT/TTS/V2V backends
- Remote MCP at https://mcp.speko.ai/mcp (streamable-http)
- Optional @spekoai/mcp npm stdio package v1.0.9 with SPEKO_API_KEY or OAuth
- Open-source bridge repo: github.com/SpekoAI/mcp-bridge
- Registry version 1.0.9
- Remote URL: https://mcp.speko.ai/mcp
- npm package: @spekoai/mcp v1.0.9
What problem does it solve?
Building voice agents alone means juggling multiple speech APIs and manual failover every time a provider hiccups.
Who is it for?
Indie builders prototyping voice assistants, sales dialers, or realtime voice UX who want MCP-native provider orchestration.
Skip if: Text-only SaaS teams with no audio pipeline, or builders who need on-prem-only voice with zero hosted MCP remotes.
What do I get? / Deliverables
After registration, your agent talks to Speko MCP once and gets unified voice routing with failover instead of brittle per-vendor scripts.
- Unified MCP tools for voice provider selection and failover
- Hosted remote endpoint wired into the agent
- Reduced custom glue code across STT/TTS/V2V vendors
Recommended MCP Servers
Journey fit
Voice products are assembled in Build when you connect models, telephony, and realtime APIs—Speko is an integration MCP, not a launch or analytics tool. Official Speko bridge exposes streamable HTTP and npm stdio transport so agents configure routing and failover across voice providers from one place.
How it compares
Voice routing and failover MCP integration, not a local TTS model or a generic LLM chat skill.
Common Questions / FAQ
Who is ai.speko/mcp for?
Developers shipping voice AI features who want one MCP layer for STT, TTS, and V2V with provider failover.
When should I use Speko MCP?
During Build when you integrate realtime speech into an agent or product and need stable routing across commercial voice backends.
How do I add ai.speko/mcp to my agent?
Add remote https://mcp.speko.ai/mcp for streamable-http, or install @spekoai/mcp and set SPEKO_API_KEY (or use OAuth without the key on hosted remotes).