n8n community node that extends the built-in MCP Server Trigger to expose HTTP request headers in workflow data. The stock MCP Server Trigger node isolates tool execution from the HTTP transport layer. Headers sent by the MCP client are not accessible in downstream workflow nodes. This means values like `job_id` or `session_token` must be passed as tool arguments via `$fromAI()`, which lets the LLM fabricate them.