API docs
Powered by MCP Protocol

Connect QuickVoice MCP with your AI tools.

Manage agents, launch guarded call workflows, inspect logs, and review widget activity from clients like Cursor, Claude, Codex, and Windsurf.

Connect to MCP Server View API reference
33 tools26 resourcesStreamable HTTP

Works with

Connect the clients your team already uses

QuickVoice MCP uses Streamable HTTP, so the same server endpoint can be configured across compatible AI clients.

Cursor

AI code editor

Windsurf

AI code editor

Claude Desktop

Desktop MCP client

Claude Code

CLI assistant

Codex

OpenAI coding agent

VS Code

Editor clients

GitHub Copilot

IDE assistant

JetBrains

IDE clients

OpenHands

Development agent

Other MCP clients

Streamable HTTP

What is QuickVoice MCP?

A controlled bridge between AI clients and QuickVoice operations

The MCP server wraps existing verified QuickVoice APIs so assistants can help operate the product without scraping the console UI.

Manage agents

Create, inspect, and update QuickVoice AI voice agents from an MCP-capable assistant.

Launch calls

Start preview sessions and outbound calls through guarded MCP tools.

Review call logs

Read call status, recordings, transcripts, duration, and routing context.

Website widget

Inspect widget configuration and sessions without switching away from your AI tool.

Secure access

Use bearer-token authentication at the MCP edge before requests touch QuickVoice APIs.

Tool registry

Expose only verified APIs and keep excluded routes visible for product review.

Recommended architecture

Keep MCP separate from the docs app

QuickVoice docs can explain and configure MCP, but the deployed MCP endpoint should stay in the dedicated Node service so machine traffic, auth, logs, and scaling remain isolated from the public documentation site.

Machine-facing backend

apps/mcp-server

Owns the Streamable HTTP MCP endpoint, bearer-token gate, tool/resource registry, validation, and upstream QuickVoice API calls.

Human-facing documentation

apps/docs

Owns the MCP setup UI, client configuration guides, API reference, safety notes, troubleshooting, and product documentation.

Source of truth APIs

apps/server

Existing QuickVoice REST routes stay the operational contract. MCP remains a thin wrapper instead of duplicating business logic.

Deployment shape

docs.quickvoice.co        → apps/docs        → pages, setup UI, API reference
mcp.quickvoice.co/mcp    → apps/mcp-server  → Streamable HTTP MCP endpoint
api.quickvoice.co/api/v1 → apps/server      → verified QuickVoice REST APIs

MCP client setup guide

Generate your QuickVoice MCP config

Enter your QuickVoice API key and MCP endpoint to produce a config block. Values stay in this browser tab and are not sent anywhere.

Connection details

Use an organization-scoped API key with the permissions your MCP client needs.

Core configuration block

Copy this into your MCP client.

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

Client guides

Setup steps for popular MCP clients

Use the generated config block above, then follow the client-specific steps below.

Add to Cursor MCP settings

  1. Open Cursor settings.
  2. Find MCP servers.
  3. Paste the QuickVoice configuration block.
  4. Restart the MCP connection.

Verify

List my QuickVoice agents using MCP.

Example config

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

FAQ

Frequently asked questions

Answers for teams connecting QuickVoice MCP to their AI development and operations workflows.

QuickVoice MCP is a Streamable HTTP server that lets MCP-capable AI clients call verified QuickVoice APIs as tools and read QuickVoice data as resources.

Need help connecting QuickVoice MCP?

Use the troubleshooting guide first, then contact support if your client cannot complete the MCP handshake.

Troubleshooting Contact support