MCP Endpoint

API reference for the FlowCaptain MCP (Model Context Protocol) endpoint for automatic tool discovery.

MCP Endpoint

FlowCaptain provides an MCP (Model Context Protocol) endpoint that lets voice bot platforms automatically discover and use all appointment tools.

Endpoint

POST /mcp

Headers

Authorization: Bearer sk_live_your_api_key
Accept: application/json, text/event-stream
Content-Type: application/json

The Accept header must include both application/json and text/event-stream. Voice bot platforms like Retell and VAPI send this automatically.

How It Works

MCP is a protocol that lets AI tools be discovered dynamically. Instead of configuring each endpoint manually, your voice bot connects to the MCP endpoint once and automatically sees all available tools:

  1. The platform sends an initialize request to discover capabilities
  2. It then sends a tools/list request to get all available tools
  3. When the voice bot needs to check availability or book an appointment, it sends a tools/call request

Available Tools

Tool NameDescription
check_availabilityCheck available time slots using natural language
book_appointmentBook an appointment with caller details
cancel_appointmentCancel an existing appointment
reschedule_appointmentReschedule an appointment to a new time

Testing with curl

curl -X POST https://api.flowcaptain.ai/mcp \
  -H "Authorization: Bearer sk_live_your_api_key" \
  -H "Accept: application/json, text/event-stream" \
  -H "Content-Type: application/json" \
  -d '{
    "jsonrpc": "2.0",
    "id": 1,
    "method": "initialize",
    "params": {
      "protocolVersion": "2024-11-05",
      "capabilities": {},
      "clientInfo": { "name": "test", "version": "1.0" }
    }
  }'

When to Use MCP vs REST

Use MCP when:

  • Your platform supports it (Retell MCP Nodes, VAPI)
  • You want automatic tool discovery
  • You want one integration point instead of four endpoints

Use REST when:

  • Your platform only supports HTTP calls
  • You need fine-grained control over individual requests
  • You're building a custom integration