Menu
Use when the user wants to set up a voice agent or a Voice Gateway endpoint with WebRTC for browser-based voice interaction.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Use when adding custom logic inside a Cognigy tool branch with manage_flow_nodes — supported node types, config schemas, placement rules, and the tool-first workflow.
Use when the user wants to add xApps to a Cognigy flow — interactive HTML / Adaptive Card mini-apps rendered to the user, with the submitted data flowing back into the conversation. Covers the xApp flow nodes, the Init Session rule, and accessing xApp data.
Add a new MCP tool (or extend an existing one) in the NiCE Cognigy Plugin's MCP server
Use when the user wants to build, create, or set up a new Cognigy AI Agent from scratch — covers listing projects, ensuring an LLM exists, creating the agent, testing it, and refining persona/job fields.
Use when the user wants to add knowledge, RAG, or a knowledge store/source to a Cognigy agent — covers embedding vs Knowledge Search models, Knowledge AI settings, ingesting sources, and attaching knowledge as a tool.
Use when configuring or choosing an LLM for a Cognigy agent — valid provider names (openAI, anthropic, azureOpenAI, google, mistral), model strings, connection types, and credential resolution.
| name | voice-gateway-setup |
| description | Use when the user wants to set up a voice agent or a Voice Gateway endpoint with WebRTC for browser-based voice interaction. |
Deploy an AI Agent as a voice-enabled endpoint with WebRTC support. Users can talk to the agent directly in their browser.
list_resources { resourceType: "project" } to find one, or let create_ai_agent create one automatically.list_resources { resourceType: "flow", projectId } to find existing flows.setup_llm if not configured.{
"projectId": "<24-char hex>",
"flowId": "<flow referenceId>",
"name": "My Voice Agent"
}
This automatically:
voiceGateway2 endpointwebrtcDemoUrl the user can open in a browser{
"projectId": "<24-char hex>",
"flowId": "<flow referenceId>",
"name": "My Voice Agent",
"webrtcWidgetConfig": {
"label": "Support Agent",
"theme": "AI_PURPLE",
"transcription": { "enabled": true },
"tagline": "How can I help you today?",
"avatarLogoUrl": "https://example.com/avatar.png"
}
}
{
"endpointId": "<24-char hex>",
"webrtcWidgetConfig": {
"theme": "CLEAN_WHITE"
}
}
| Theme | Description |
|---|---|
DARK_MODE | Dark background (default) |
CLEAN_WHITE | Light/white background |
AI_PURPLE | Purple accent theme |
| Field | Purpose |
|---|---|
webrtcDemoUrl | Open in browser to talk to the agent — always show this to users |
_integration.wsEndpointUrl | WebSocket URL for programmatic/embedded use |
_integration.embeddingSnippet | HTML code to embed the voice widget on a website |
Copy the embeddingSnippet from the response into your HTML page. It loads the Cognigy WebRTC widget and connects to the voice endpoint automatically.
create_ai_agent → get flowId and projectIdsetup_llm → configure LLM for the projectmanage_voice_gateway { projectId, flowId } → get webrtcDemoUrl