Skip to main content

​
What are MCP Tools?

MCP (Model Context Protocol) Tools allow your voice agents to interact with external APIs and services during conversations. This enables real-time data access and actions.

​
Available MCP Tools

Common MCP tools include:
  • get_appointment_slots - Fetch available appointment times
  • book_appointment - Book appointments
  • get_order_status - Check order status
  • create_support_ticket - Create support tickets
  • send_email - Send emails
  • update_crm - Update CRM records
  • Custom tools - Connect to any API

​
Configuration

1

Open Agent Configuration

Navigate to your agent’s configuration page
2

Access MCP Tools

Click on “Integrations & Tools” → “MCP Tools”
3

Add MCP Server

Configure your MCP server: - Server alias (e.g., “tooling”) - Server URL - Authentication (Bearer token or API key) - Transport type (HTTP or SSE)
4

Select Tools

Enter allowed tools (comma-separated): plaintext send_template_message, translate_text, get_messages
5

Save Configuration

Tools become available as alias-tool_name Example: tooling-send_template_message

​
Tool Configuration Format

{
  "mcp_tools": [
    {
      "server_alias": "tooling",
      "server_url": "https://api.example.com/mcp",
      "auth_type": "bearer",
      "auth_token": "your_token_here",
      "transport": "http",
      "allowed_tools": ["tool1", "tool2", "tool3"]
    }
  ]
}

​
Use Cases

​
Appointment Booking

Agent: "Let me check available slots for you."
→ Calls: get_appointment_slots(date="2025-01-20")
← Returns: ["10:00 AM", "2:00 PM", "4:00 PM"]
Agent: "I have slots at 10 AM, 2 PM, and 4 PM. Which works for you?"

​
Order Tracking

Agent: "Let me look up your order."
→ Calls: get_order_status(order_id="ORD123")
← Returns: {status: "shipped", tracking: "TRK456"}
Agent: "Your order has been shipped. Tracking number is TRK456."

​
Support Ticket Creation

Agent: "I'll create a support ticket for you."
→ Calls: create_support_ticket(issue="Login problem", priority="high")
← Returns: {ticket_id: "TKT789"}
Agent: "I've created ticket #TKT789. Our team will contact you soon."

​
Best Practices

Don’t add too many tools initially. Start with 2-3 critical tools and expand as needed.
Use clear server aliases like “booking” or “crm” instead of generic names.
Test each tool individually before deploying to production.
Ensure your agent can handle API failures and provide fallback responses.
Track API calls to avoid rate limits and unexpected costs.

​
Security

  • Store API keys securely
  • Use HTTPS endpoints only
  • Implement rate limiting
  • Validate all responses
  • Log API interactions
Never expose API keys in agent prompts or public configurations

​
Troubleshooting

  • Verify server URL is correct and accessible
  • Check authentication credentials
  • Ensure tool name is in allowed_tools list
  • Test API endpoint independently
  • Verify auth_type matches your API (bearer vs api_key) - Check token hasn’t expired - Ensure token has necessary permissions
  • Check API response time
  • Increase timeout if needed
  • Implement caching for frequently accessed data

​
Next Steps

WhatsApp Integration

Learn about WhatsApp tools integration