mcp-trigger-context

Community MCP Trigger node with request context passthrough

Package Information

Released: 6 mo ago
Downloads: 23 weekly / 169 monthly
Latest Version: 0.3.1

Available Nodes

MCP Server Trigger (Request Context) icon
MCP Server Trigger (Request Context)
Expose n8n tools as an MCP Server endpoint and inject incoming request context as $json.mcpRequest

Documentation

n8n-nodes-mcp-trigger-context

Community MCP Trigger node for current n8n 2.x installations that forwards incoming MCP HTTP request context into tool execution input as mcpRequest.

Install

npm install @mmn-systems/n8n-nodes-mcp-trigger-context

Repository: https://github.com/max00346/n8n-nodes-mcp-trigger-context

What it solves

Built-in MCP trigger tool calls do not expose HTTP headers/query/path directly to tool parameter expressions.

This node injects:

  • $json.mcpRequest.headers
  • $json.mcpRequest.query
  • $json.mcpRequest.params
  • $json.mcpRequest.method
  • $json.mcpRequest.path

For MCP tool calls on current n8n 2.x, the same request context is also embedded into the internal mcpToolCall.arguments payload so queue-mode worker executions receive the same header/query/path context as direct executions.

Example

In a connected HTTP Request tool/node expression:

={{ $json.mcpRequest.headers.authorization }}

Notes

  • Targets current n8n 2.x MCP Trigger internals.
  • Requires n8n installations that include @n8n/n8n-nodes-langchain.

Troubleshooting

If n8n shows Class could not be found after upgrading:

  1. Remove the old package from Community Nodes in n8n.
  2. Stop n8n and delete the old install at ~/.n8n/nodes/node_modules/@mmn-systems/n8n-nodes-mcp-trigger-context.
  3. Start n8n and install a pinned version, for example @mmn-systems/n8n-nodes-mcp-trigger-context@0.1.6.

Discussion