Issue Station
Sign In
Tools hereToolbox

n8n - 💡(How to fix) Fix MCP Server Trigger reading 'getWebhookName'?!?

Official PRs (…)
ON THIS PAGE

Recommended Tools

×6

Utilities matched from this issue’s tags and category — try them while you read without losing context.

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

Helpful · Quick feedback

Loading…

Error Message

Describe the problem/error/question

What is the error message (if any)?

  • error: all

Code Example

(Select the nodes on your canvas and use the keyboard shortcuts CMD+C/CTRL+C and CMD+V/CTRL+V to copy and paste the workflow.)
⚠️ WARNING ⚠️ If you have sensitive data in your workflow (like API keys), please remove it before sharing.
RAW_BUFFERClick to expand / collapse
<!-- Please follow the template below. Skip the questions that are not relevant to you. -->

Describe the problem/error/question

Can not use MCP Server Trigger

Dont know were the issue is. reinstall n8n multiple times 2.15.1, 2.16.1, 2.17.2

What is the error message (if any)?

{ "errorMessage": "Cannot read properties of undefined (reading 'getWebhookName')", "errorDetails": {}, "n8nDetails": { "n8nVersion": "2.15.1 (Self Hosted)", "binaryDataMode": "filesystem", "stackTrace": [ "TypeError: Cannot read properties of undefined (reading 'getWebhookName')", " at WebhookContext.webhook (/root/n8n2.0/node_modules/@n8n/n8n-nodes-langchain/nodes/mcp/McpTrigger/McpTrigger.node.ts:141:31)", " at WebhookService.runWebhook (/root/n8n2.0/node_modules/n8n/src/webhooks/webhook.service.ts:464:31)", " at Object.executeWebhook (/root/n8n2.0/node_modules/n8n/src/webhooks/webhook-helpers.ts:526:60)" ] } }

Please share your workflow/screenshots/recording

(Select the nodes on your canvas and use the keyboard shortcuts CMD+C/CTRL+C and CMD+V/CTRL+V to copy and paste the workflow.)
⚠️ WARNING ⚠️ If you have sensitive data in your workflow (like API keys), please remove it before sharing.

Share the output returned by the last node

<!-- If you need help with data transformations, please also share your expected output. -->

Debug info

core

  • n8nVersion: 2.15.1
  • platform: npm
  • nodeJsVersion: 22.22.2
  • nodeEnv: undefined
  • database: sqlite
  • executionMode: regular
  • concurrency: -1
  • license: enterprise (production)

storage

  • success: all
  • error: all
  • progress: false
  • manual: true
  • binaryMode: filesystem

pruning

  • enabled: true
  • maxAge: 336 hours
  • maxCount: 5000 executions

client

  • userAgent: mozilla/5.0 (x11; linux x86_64; rv:140.0) gecko/20100101 firefox/140.0
  • isTouchDevice: false

Generated at: 2026-04-20T15:35:41.366Z

extent analysis

TL;DR

The issue is likely due to a compatibility problem with the MCP Server Trigger node in n8n version 2.15.1, causing a "Cannot read properties of undefined" error.

Guidance

  • Check the MCP Server Trigger node configuration to ensure it is properly set up and compatible with the current n8n version.
  • Verify that the getWebhookName property is defined and accessible in the WebhookContext.
  • Try updating to a newer version of n8n, such as 2.17.2, to see if the issue persists.
  • Review the stack trace to identify the exact line of code causing the error and investigate potential fixes.

Example

No code snippet is provided as the issue is related to a specific node configuration and version compatibility.

Notes

The issue may be specific to the MCP Server Trigger node or the n8n version being used. Further investigation is needed to determine the root cause.

Recommendation

Apply workaround: Try updating to a newer version of n8n, such as 2.17.2, to see if the issue persists, as the error may be resolved in a later version.

Vote matrix · Quick signals

Works
Did the solution work? Tap to confirm.
Easy Fix
Was it a quick fix?
Time Saver
Did it save you time?
Blocking
Was it severely blocking?
Common Issue
Are others likely hitting this too?
Flaky / Intermittent
Is it intermittent?
Verified / Reproducible
Can you reproduce it reliably?
Loading…
#api#chain error#conversation history#tool integration#LLM response

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING