Adding custom headers to MCP client node

Feature Requests
1

The idea is: Add a headers option to the n8n MCP client configuration, so that custom headers can be sent in addition to existing authentication methods, not as a separate authentication type.

My use case: Some MCP servers require additional information passed via headers besides authentication. For example, in TFS Azure Search, the organization separation is handled by sending the organization name in a header. Currently, I do not see a clean way to add such headers to the MCP client node (other than doing a separate HTTP request).

I think it would be beneficial to add this because: Many MCP servers rely on custom headers for routing, authorization, or organization separation. Adding a headers option would make the MCP client more flexible and useful for developers who need to integrate with such systems, while still using the existing authentication methods.

Any resources to support this? I can only speak from experience working with MCP servers where handling authorization and organization separation via headers is a common requirement.

Are you willing to work on this? Definitely, if there is anyone willing to have a look together with me into this issue.

2

This is something that we also need.
As an example, we have a workspace_id in our use case, we do not want to add it as an argument to every one of the MCP tools we have implemented, we want to have it as a header.