Summary
Connects your MCP client to Speko's hosted voice AI routing platform for STT, TTS, and voice-to-voice provider failover. The package is primarily an installer wizard that configures Claude Code, Codex, OpenCode, and Cursor to talk directly to Speko's remote MCP endpoint at mcp.speko.ai. If your client can't handle remote MCP and needs a local stdio command, the bridge mode proxies stdio to HTTP but doesn't contain any tool logic itself. Auth is OAuth by default or API key via SPEKO_API_KEY for headless setups. Reach for this when you're building voice applications and want intelligent provider switching without managing fallback chains yourself.
Fastest browser for AI agents to run web automation tasks, always free.
Download Free life-time →
belt cli automatically finds the best tools and skills for your agent. image, video, music, tts...
one prompt install →
Free an open-source skills that make AI coding agents easier to understand, verify, and control.
Download for free →
Connect your Claude agent to live crypto prices and trading routes via 1inch
Get the MCP →
Notes, actions and memory. Without a meeting bot. First month 100% off.
Download for free →@spekoai/mcp
Configure coding agents to connect directly to Speko's hosted MCP server over
HTTP. Version 2 removes the local stdio bridge: modern clients connect to
https://mcp.speko.ai/mcp with OAuth browser sign-in or SPEKO_API_KEY.
Install
Run the setup wizard and choose OAuth for interactive use:
npx @spekoai/mcp@latest init
For automation, create a Platform API key in the Speko dashboard and choose API-key authentication.
The wizard detects Claude Code, Claude Desktop, Codex, OpenCode, Cursor, Windsurf, VS Code, Gemini CLI, Cline, and Zed. It writes each client's direct HTTP configuration and preserves existing JSON, JSONC, and TOML settings.
For scripted setup, pass every choice explicitly:
npx @spekoai/mcp@latest init --auth oauth --tools all --scope user --yes
SPEKO_API_KEY=sk_live_xxx npx @spekoai/mcp@latest init --auth api-key --tools claude,cursor,codex --scope project --yes
Use --dry-run to print the proposed edits without changing files. Run
npx @spekoai/mcp@latest --help for the complete option list.
Gateway key management
The gateway.keys.list, gateway.keys.create, and gateway.keys.revoke tools
require a Platform API key created by an organization owner or admin with
Manage Gateway API keys enabled. Other MCP tools work with an ordinary
unscoped Platform API key.
Speko MCP is stateless for both authentication modes. Better Auth owns the OAuth flow; the MCP service stores no clients, codes, refresh tokens, or local credential cache. Gateway key tools currently require API-key auth.
Featured
Fastest browser for AI agents to run web automation tasks, always free.
Download Free life-time →belt cli automatically finds the best tools and skills for your agent. image, video, music, tts...
one prompt install →Free an open-source skills that make AI coding agents easier to understand, verify, and control.
Download for free →Connect your Claude agent to live crypto prices and trading routes via 1inch
Get the MCP →Notes, actions and memory. Without a meeting bot. First month 100% off.
Download for free →Configuration
SPEKO_API_KEYsecretSpeko API key, forwarded to the hosted MCP server as a bearer token. Optional: omit to authenticate via OAuth instead.
Categories
Registryactive
Package@spekoai/mcp
TransportSTDIO, HTTP
AuthRequired
UpdatedJun 6, 2026
