Access HTTP Headers and URL Params in MCP Node

Feature Requests
1

##The idea
Enable the MCP server trigger node in n8n to access custom HTTP headers and URL/query/path parameters, similar to the Webhook node. This would allow passing secure contextual data into workflows.

##My use case:
I’m sending secure identifiers (like userId, transactionId, or databaseName) from an external app (built on OpenAI’s ResponsesAPI) to trigger an MCP-based workflow. I need this data to personalize and route AI behavior, but the MCP node currently doesn’t expose it.

##I think it would be beneficial to add this because:
It would allow more secure, context-rich workflows. Without access to headers or params, we can’t easily pass necessary metadata, making advanced integrations difficult or impossible with MCP.