n8n-mcp incorrectly passing escape character \n to code node

[jensenmkaplan]

Hello everyone,

As the title states I'm having issues with the mcp creating custom code nodes. When it generates a code node i notice that it's all commented out and "n"s are all over. I check the json of the workflow and I see that the mcp is not passing \n inside the string for "jsCode" : " ".

I'm on macOS, using the mcp with Cursor, and I'm self hosting n8n.

I've challenged cursor before and for one day I got it to correctly pass the escape character and it was creating code nodes correctly. However it seems to have lost its memory and is now incorrectly passing them once again.

Has anyone else run into this issue and have you been able to permanently fix this?

I'd consider this a significant issue seeing as code nodes are what makes n8n favorable to the other automation services.
The mcp has good logic for creating custom code, but it needs to be able to implement it correctly without me needing to copy and paste code every single time.

[jensenmkaplan]

This post is a known issue as found here

I've figured out that the issue is actually due to model limitations. When I had cursor set to automatically choose a model I ran into this issue with escapes. When I specified usingt Claude-4-Sonnett the code nodes are handled perfectly.

Hope this helps!

-Jensen