Use this flow to connect an MCP-capable client to the dedicated QuickVoice MCP service over Streamable HTTP.

Quickstart

1. Start the dedicated MCP HTTP service

bash

pnpm --filter quickvoice-mcp-server build
PORT=8787 MCP_ENDPOINT_PATH="/mcp" QUICKVOICE_API_BASE_URL="https://api.quickvoice.co/api/v1" pnpm --filter quickvoice-mcp-server start

The MCP service lives in apps/mcp-server. Keep apps/docs for this setup UI and API documentation.

The MCP service does not use a separate MCP-only token. Each client request sends a QuickVoice organization API key, and the MCP service forwards that key to the existing QuickVoice API permission layer.

2. Add the remote endpoint to your client

json

{
  "mcpServers": {
    "quickvoice": {
      "url": "https://mcp.quickvoice.co/mcp",
      "transport": "streamable-http",
      "headers": {
        "x-api-key": "YOUR_QUICKVOICE_API_KEY"
      }
    }
  }
}

3. Verify the connection

Run the MCP smoke script from the repository. It talks to the MCP endpoint, not the raw REST API.

bash

QUICKVOICE_API_KEY="YOUR_QUICKVOICE_API_KEY" MCP_URL="https://mcp.quickvoice.co/mcp" pnpm --filter quickvoice-mcp-server test:mcp