# Speko [Health: Active]

**Category:** 🎙️ Speech-to-Text  
**Repository:** https://github.com/SpekoAI/mcp-bridge  
**GitHub Stars:** 0  
**Views:** 0  
**Installs:** 0  
**Upvotes:** 0  
**Directory Page:** https://allmcps.com/mcp/speko

## Description
Official Speko MCP server: build, run, and migrate voice agents (STT/TTS/V2V) for coding agents.

## Claude Desktop Quick Installation
Install path detected from listing signals. Uses `npx` (confidence: high):

```json
"mcpServers": {
  "speko": {
    "command": "npx",
    "args": ["-y","@spekoai/mcp@latest"]
  }
}
```

## Documentation & README

# @spekoai/mcp

Interactive installer and local stdio-to-remote bridge for Speko MCP. The
installer configures Speko's hosted remote MCP endpoint in coding tools that
support it. The `bridge` command is only for MCP clients that require a local
stdio command: it speaks stdio to the client, connects to Speko's hosted MCP
server over HTTP, and does not contain Speko tool logic of its own.

## Install

```bash
npx @spekoai/mcp@latest init
```

The package exposes the `spekoai-mcp` binary. Run `init` for a guided setup
wizard: it detects which coding agents are installed (Claude Code, Claude
Desktop, Codex, OpenCode, Cursor, Windsurf, VS Code, Gemini CLI, Cline, Zed)
and preselects them, then writes each agent's config in its own convention —
remote HTTP where the agent supports it, the local stdio `bridge` where it
does not. Agents with a global rules file (Codex, Gemini CLI, Windsurf, Cline,
VS Code) also get a short Speko usage guide in that convention.

For scripted setup, pass the choices explicitly (`--tools all` configures
every detected agent):

```bash
npx @spekoai/mcp@latest init --auth oauth --tools all --scope user --yes
npx @spekoai/mcp@latest init --auth oauth --tools claude,cursor,windsurf --scope user --yes
```

## Bridge

Most users should run `init`. Use `bridge` only when a client cannot connect to
remote MCP directly and asks for a local command-based MCP server.

```bash
npx @spekoai/mcp@latest bridge
```

For API-key auth in a headless bridge setup, provide `SPEKO_API_KEY` in the MCP
client environment. The bridge forwards it to the hosted MCP server as
`Authorization: Bearer ...`.

The `bridge` command adapts local stdio MCP to Speko's remote HTTP MCP endpoint.
Use direct remote MCP configuration instead when your client supports it.

Defaults:

- Endpoint: `https://mcp.speko.ai/mcp`

Environment variables:

- `SPEKO_API_KEY`: forward an API key as a bearer token.

CLI examples:

```bash
npx @spekoai/mcp@latest bridge
SPEKO_API_KEY=sk_live_xxx npx @spekoai/mcp@latest bridge
```

All remaining arguments are passed through to
[`mcp-remote`](https://www.npmjs.com/package/mcp-remote).

## Troubleshooting

Run:

```bash
npx @spekoai/mcp@latest bridge --help
```

When using `bridge`, OAuth state is handled by
[`mcp-remote`](https://www.npmjs.com/package/mcp-remote). It may create
a local OAuth cache directory, or use `MCP_REMOTE_CONFIG_DIR` to store local
OAuth credentials and debug logs. The `init` wizard does not write that
directory.

For connection or OAuth issues, pass `--debug` and inspect the log path printed
by [`mcp-remote`](https://www.npmjs.com/package/mcp-remote).