Notifications
Clear all
How To
9
Posts
4
Users
0
Reactions
6
Views
Topic starter
Hi, I'm testing the new MCP Server Trigger and MCP Client nodes with a straightforward workflow example. The setup involves an MCP Server Trigger with two Airtable tools: getContacts and createContact:
The primary workflow (which invokes the MCP Server Trigger) is a simple IA Agent utilizing an MCP client as its tool. While the MCP nodes appear to be functioning correctly, the 'IA Agent' is returning the following error: Provider returned error.
I suspect the issue stems from the response format that the MCP Client provides to the 'IA Agent', as I believe the 'IA Agent' is unable to interpret its structure (shown below):
Output MCP Client >> IA Agent
[[
{
"response": [
{
"type": "text",
"text": "[{{"records":[{"id":"rec8OnAOUgj9wEL9U","createdTime":"2025-03-31T07:45:32.000Z","fields":{"nombre":"Juan Pérez","email":"juan.perez@hotmail.com"}},{"id":"rec8sWXDfDzmpYS0h","createdTime":"2025-03-07T19:46:32.000Z","fields":{"nombre":"Álvaro García","email":"alvaro.garcia@ext.opp.es"}}]}}]]"
}
]
}
]
Information about my callin.io setup
- callin.io version: 1.88.0
- Running callin.io via: web localhost:5678
- Operating system: Windows 10
I appreciate your help!!
Thanks in advance!!
Posted : 17/04/2025 7:43 pm
I'm encountering the exact same issue. Similar to what the original author noted, it appears that MCP is returning a JSON format that isn't quite right. My suspicion is that it should look like this:
{
"response": "[{ 'json': 'schema_here' }]",
}
I tested this by connecting the Gmail tool directly to the AI Agent node, and it functioned correctly.
Posted : 18/04/2025 9:54 am
Topic starter
This is the error displayed in the console:
Could you please assist with this?
Posted : 20/04/2025 4:06 pm
I'm encountering the identical problem. Has a solution been found for this yet? Or is there a temporary fix available? During my testing, I found that I needed to run the step twice for it to function correctly, but then it would fail on the third attempt. It seems to work intermittently.
Posted : 15/05/2025 2:56 pm
The latest 1.93 release appears to have resolved this issue for me.
Posted : 15/05/2025 6:02 pm
Topic starter
Hi Robert,
Yes, the issue has been resolved.
Thank you!
Posted : 15/05/2025 6:27 pm
I just ran mine and the same issue appeared. It was resolved for approximately 2 hours.
Posted : 15/05/2025 7:03 pm
Posted : 15/05/2025 7:09 pm
It's possible the AI agent requires a system prompt. Also, perhaps adding a 'do nothing' node to the last node of the MCP trigger might yield better results.
Posted : 16/05/2025 11:41 pm