The MCP tool returns a very large base64 string within the item’s JSON. This large payload goes through the n8n pipeline (cleanup, pairing, mappings, etc.), and in certain versions/paths ends up in a generic JS stack overflow (exactly this error), typical when handling very large structures/arguments or involving deep recursive traversals. This doesn’t seem to be a flaw in the MCP server itself, but rather in how the client/consumer handles the large response.
Convert the base64 to binary and purge the large JSON. Just after the MCP Client Tool, Convert to File → Move base64 string to file