For the complete documentation index, see llms.txt.
The VoxEngine MCP Client lets a VoxEngine scenario connect to Model Context Protocol servers and call their tools from a live voice workflow.
Use it when your voice agent needs access to tools exposed through an MCP server, such as CRM lookups, scheduling systems, internal databases, or automation platforms. VoxEngine keeps the realtime call and voice orchestration inside your scenario while the MCP server provides the external tool layer.
To call MCP tools from a VoxEngine scenario:
Modules.MCP module.MCP.Client with MCP.createClient(...).mcpServerConnectionConfig object with the MCP server endpoint and transport.MCP.ServerEvents.ConnectorInformation, then call mcpClient.listTools({}).mcpClient.callTool(...).MCP.ServerEvents.ToolResult and MCP.ServerEvents.MCPError in your business logic.See the MCP API Reference for the full list of client parameters, methods, and events.
http or sse transport.MCP.createClient(...) accepts mcpServerConnectionConfig, which describes the MCP server connection:
The MCP client supports http and sse transports. Use the transport expected by your MCP server.
This example answers an inbound call, connects to an MCP server, lists available tools, calls a demo roll tool, and logs the result. It expects MCP_SERVER_URL and MCP_SERVER_TOKEN secrets.