I’m trying to figure out what exactly should be included in the body of the MCP server when setting up an API node in Workflows. Could you provide some guidance or examples on how to structure this? i,e, Create specific values that get sent in the API request body https://cdn.discordapp.com/attachments/1377241659867140137/1377241660043431966/image.png?ex=68383fbf&is=6836ee3f&hm=f5353b62b8aad9673946a5b2df8da5bf2b5b9faa95d5782d7187cc201f55b3ed& https://cdn.discordapp.com/attachments/1377241659867140137/1377241660349747240/image.png?ex=68383fbf&is=6836ee3f&hm=f0f260e8fcbed29afd6b19772f1a7f4f64ec7b93b216f28139cb8d5444d26187&

To structure the body for an MCP server API node in Workflows, use a JSON object that specifies the tool/action and its arguments. For example, to create a call via MCP, your body might look like:

json
{
  "name": "create_call",
  "arguments": {
    "assistantId": "your-assistant-id",
    "phoneNumberId": "your-phone-number-id",
    "customer": {
      "phoneNumber": "+1234567890"
    }
  }
}

Replace the values with your actual assistant and phone number IDs. Adjust the structure based on the specific MCP tool/action you want to invoke. Tip: Always check the MCP server's documentation for the required fields for each action. Sources: - [Vapi MCP Server Documentation](https://docs.vapi.ai/sdk/mcp-server) - [Vapi MCP Tool Documentation](https://docs.vapi.ai/tools/mcp)

Message marked as helpful by @! AetherMind! 🎉

Hey FabulousRay, checking if you want to continue this thread over here or in email?