Theme

MCP quickstart ​

Connect an MCP client to VoiceLab to generate speech, transcribe recordings, or isolate voices.

Hosted access ​

Request a gateway token from the VoiceLab MCP operator before connecting. The hosted server requires Authorization: Bearer <MCP_AUTH_TOKEN>. This is a separate credential from a VoiceLab API key.

The operator configures the upstream VoiceLab API key on the server. Tool calls use that account's permissions and credits. To use your own account, follow Self-hosted setup.

Connect Cursor ​

Add this entry to ~/.cursor/mcp.json or your project's .cursor/mcp.json:

json
{
  "mcpServers": {
    "voicelab": {
      "url": "https://mcp.voicelab.uz/mcp",
      "headers": {
        "Authorization": "Bearer ${env:VOICELAB_MCP_AUTH_TOKEN}"
      }
    }
  }
}

Set VOICELAB_MCP_AUTH_TOKEN in Cursor's environment and reload its MCP configuration. See Cursor's configuration reference.

Check the client's tool list, then ask for available voices:

text
List the available Uzbek voices in VoiceLab.

Then choose a voice and ask it to generate a short sample. Generation uses the operator's VoiceLab credits.

Verify the endpoint ​

Discovery does not require a token:

bash
curl -fS 'https://mcp.voicelab.uz/v1'

It returns transport, authentication, and endpoint metadata. To check the MCP handshake with your token:

bash
curl -fS 'https://mcp.voicelab.uz/mcp' \
  -H "Authorization: Bearer $VOICELAB_MCP_AUTH_TOKEN" \
  -H 'Accept: application/json, text/event-stream' \
  -H 'Content-Type: application/json' \
  -d '{"jsonrpc":"2.0","id":1,"method":"initialize","params":{"protocolVersion":"2024-11-05","capabilities":{},"clientInfo":{"name":"voicelab-check","version":"1.0"}}}'

Use an MCP client for the remaining initialization and tool calls. A one-shot curl process is not a stdio MCP server.

Next steps ​