I happily jumped onto the MCP bandwagon in FME 2026.2. Then I found a small but nagging inconvenience.
Unlike the HTTPCaller, I can not set the Connection Timeout on the MCP-Caller. It appears to have a timeout of 30 seconds.
Although this should be enough in most cases, it is significantly shorter than the default job-timeout of 1 minute when creating a MCP server on Flow.
This annoys me, and is also inconvenient while developing a MCP tool which might not be as optimal yet as it should be later in the development cycle.
Thanks,
Martin
