Hello!
I’ve encountered an issue when working with the MCP Server Trigger node in n8n.
Problem description:
I am using the MCP Server Trigger node as the entry point for my workflow.
The MCP client (for example, Cursor) sends the sessionId only in the query string (e.g., /mcp/messages?sessionId=abc123).
It is not possible to modify the client to send the sessionId in the request body.
In the input data of the workflow, I only see the contents of the request body (such as the input field), but I do not see the sessionId from the query string.
The nginx logs confirm that the sessionId is present in the request.
Question:
Is there any way to access the sessionId from the query string in the workflow input when using the MCP Server Trigger node?
Are there any plans to add this functionality, similar to how the HTTP Trigger node automatically includes query string parameters in the input?
Are there any workarounds on the n8n side that would allow the workflow to access the sessionId without requiring changes to the client?