You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I’m working on a case where I want to use an MCP server (specifically a custom MCP server). This server contains a group of tools, and each tool may accept different input arguments with different data types.
The issue I’m facing is that whenever I try to use a tool, Flowise always converts the input arguments into strings, which then causes errors.
For example, when using the Firecrawl MCP server and selecting the FIRECRAWL_CRAWL tool , I get the following error:
[{"type":"text","text":"Error: Request failed with status code 400.
Error: Bad Request - [
{"code":"invalid_type","expected":"number","received":"string","path":["maxDepth"],"message":"Expected number, received string"},
{"code":"invalid_type","expected":"number","received":"string","path":["limit"],"message":"Expected number, received string"},
{"code":"invalid_type","expected":"boolean","received":"string","path":["ignoreQueryParameters"],"message":"Expected boolean, received string"}
]"}]
Here are the screenshots of the Flow setup that produces this issue:
So my question is:
Is there a way to prevent Flowise from converting all arguments to strings, or to handle this type casting properly so the tools receive the correct types (number, boolean, etc.)?
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
I’m working on a case where I want to use an MCP server (specifically a custom MCP server). This server contains a group of tools, and each tool may accept different input arguments with different data types.
The issue I’m facing is that whenever I try to use a tool, Flowise always converts the input arguments into strings, which then causes errors.
For example, when using the Firecrawl MCP server and selecting the FIRECRAWL_CRAWL tool , I get the following error:
Here are the screenshots of the Flow setup that produces this issue:


So my question is:
Is there a way to prevent Flowise from converting all arguments to strings, or to handle this type casting properly so the tools receive the correct types (number, boolean, etc.)?
Beta Was this translation helpful? Give feedback.
All reactions