Quickstart

Connect a vozo organization to an MCP client in a few minutes. You need access to Settings → Organization → MCP access and an organization API deployment.

1. Create a credential

Open organization settings in the vozo console and create an MCP credential with a recognizable name and expiry. Copy it when it is shown; vozo stores only its hash, so the secret cannot be viewed again. Credentials are organization-scoped, expire within 90 days, and can be revoked from the same settings page.

The credential inherits the creator’s provider-cost visibility and agent-creation access. Create it with the least access the workflow needs.

2. Add the MCP server

Configure your MCP client to use Streamable HTTP and the public API origin configured for your vozo deployment:

{
  "type": "http",
  "url": "https://<your-api-host>/mcp",
  "headers": {
    "Authorization": "Bearer vozo_mcp_<credential>"
  }
}

Replace the host and credential with the values for your deployment. Keep the credential in the client’s secret store; do not commit it to source control.

3. Try a read tool

Ask the connected client to list voice agents, summarize call costs for a date range, or report call timing. The MCP reference lists tools and their inputs.

4. Import an external agent (optional)

Connect ElevenLabs, Vapi, or Retell in vozo organization settings. Then use list_external_voice_agents to find an agent and import_external_voice_agent to create a vozo agent record from its supported configuration. The import does not publish the agent or place calls.

Local development

Set API_URL in the browser app to the public API origin so the console can manage credentials and clients can reach /mcp. Apply the database migrations before deploying the API:

pnpm --filter @workspace/db migrate

See the platform deployment configuration in platform/ for production-specific details.