Fix: MCP Server Trigger reading 'getWebhookName'?!?

[shahyashish]

In n8n trigger nodes, the webhook method receives its execution context (of type IWebhookFunctions) via the 'this' binding rather than as a function argument. By declaring the method with 'context: IWebhookFunctions' as a parameter, the context variable was left undefined when called by the n8n core, resulting in the reported TypeError. The fix updates the method signature to use 'this: IWebhookFunctions' and assigns it to a local 'context' variable to resolve the issue while maintaining compatibility with the rest of the method's logic.

Test: 1. Configure an MCP Server Trigger node in an n8n workflow.
2. Set a path (e.g. 'mcp-server') and Authentication to 'None'.
3. Activate the workflow.
4. Use a tool like 'curl' to make a GET request to the node's setup URL (e.g., http://localhost:5678/rest/oauth2-webhooks/mcp-server/sse).
5. Verify that the request no longer results in a 500 error and the n8n logs do not show the 'Cannot read properties of undefined (reading 'getWebhookName')' error.

[CLAassistant]

Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.
_{You have signed the CLA already but the status is still pending? Let us recheck it.}

[cubic-dev-ai]

No issues found across 1 file