Speko MCP Server

What is Speko MCP Server?

The Speko MCP server at https://mcp.speko.ai/ is the public, read-only Speko Docs MCP: it lets an AI assistant search and read Speko's voice-AI API, SDK, adapter, quickstart and migration docs without signing in.

Speko describes itself as "the router for voice AI". It has a hosted Router that sends speech-to-text (STT), LLM and text-to-speech (TTS) traffic to providers through typed contracts, and an open customer-side Gateway for LiveKit and Pipecat. Speko also publishes model benchmarks across 17 languages. The docs endpoint listed here exists so coding agents can look up how to use all of that while they write code. For account work (agents, calls, phone numbers), Speko runs a separate, authenticated operational endpoint at https://mcp.speko.ai/mcp.

How to use Speko MCP Server?

The docs endpoint needs no account, API key or OAuth sign-in. Add it to your client as a remote Streamable HTTP server.

Claude Code

claude mcp add --transport http speko-docs https://mcp.speko.ai/

Claude Desktop and claude.ai

Open Settings > Connectors > Add custom connector, give it a name such as "Speko Docs", and paste https://mcp.speko.ai/ as the URL.

Cursor

Add an entry to ~/.cursor/mcp.json (or the project's .cursor/mcp.json):

{
  "mcpServers": {
    "speko-docs": {
      "url": "https://mcp.speko.ai/"
    }
  }
}

VS Code

Add the server to .vscode/mcp.json:

{
  "servers": {
    "speko-docs": {
      "type": "http",
      "url": "https://mcp.speko.ai/"
    }
  }
}

Connecting the full Speko toolset

To work with your Speko account instead of just the docs, connect the operational endpoint. Speko documents these commands:

npx @spekoai/mcp@latest init
claude mcp add --transport http speko https://mcp.speko.ai/mcp

That endpoint uses OAuth browser sign-in. For automation you can instead send a Speko Platform API key as Authorization: Bearer ${SPEKO_API_KEY}. Keys are created and revoked in the Speko Platform dashboard, not through MCP.

Key features of Speko MCP Server

• Public and read-only: the server's own instructions say it "never exposes account data or write tools and requires no authentication".
• Bundled documentation for Speko's voice-AI API, SDKs, adapters, quickstarts and migration guides, exposed as MCP resources.
• A docs index resource (spekoai://docs/index) that lists every bundled doc, plus one resource per doc at spekoai://docs/{slug}.
• Ranked search that returns slug, title, score and snippet, useful for looking up a field name after an API validation error.
• A setup tool that returns the operational endpoint, a guided installer command and copy-ready snippets for Claude Code, Codex, OpenCode and Cursor.
• A setup card UI resource for clients that render MCP Apps.

Speko MCP Server tools

The docs endpoint exposes two tools:

• Documentation search: docs.search searches the bundled Speko docs and returns slug, title, score and snippet for each hit. Open a hit by reading the spekoai://docs/{slug} resource.
• Client setup: setup.connect shows how to connect an MCP client to Speko. It returns the operational endpoint, the npx @spekoai/mcp@latest init installer, how sign-in works and a setup snippet per client.

The operational endpoint at /mcp is much larger. Speko's MCP guide says it provides 101 tools covering organizations, agents, sessions, calls, phone numbers, knowledge bases, evals, deployment, migration helpers and usage data.

Use cases of Speko MCP Server

• Look up SDK usage while coding a voice agent: "Search the Speko docs for how to use the Gateway STT plugin with LiveKit."
• Fix a request after an API error: "My Speko request failed validation on objective. Find the correct field shape."
• Plan a migration: "Find the Speko migration guide for moving an existing voice-agent config."
• Onboard a teammate's client: "How do I connect Speko to Cursor and Codex?" (the agent calls setup.connect).
• Give a coding agent safe, credential-free context about Speko before you decide to connect the account-level server.

Troubleshooting Speko MCP Server

• You need account actions, but only two tools appear: you are connected to the public docs endpoint (https://mcp.speko.ai/). Connect https://mcp.speko.ai/mcp and sign in to get the operational tools.
• 401 "Authentication required": this comes from the operational /mcp endpoint, which requires OAuth sign-in or a Bearer API key. The docs endpoint at the root URL needs neither.
• A tool returns "Unknown tool" on a directory host: Speko's narrower directory hosts (for example anthropic.speko.ai) withhold some tools, such as agent deployment and deletes, by design.