When using Port as an MCP connector with external MCP servers, there is currently no way to pass user-specific information (such as the user's email or Port access token) to the remote MCP server.

Today, the only supported mechanism is configuring static headers on the MCP server entity. either hardcoded values or organization-level secrets. While this works well for shared/service-account authentication patterns, it does not support use cases where the external MCP server needs to identify or impersonate the individual user making the request (e.g., for audit logging, user-level authorization, or impersonation flows).

Requested behavior:

Allow MCP connector headers to optionally include dynamic user context, such as:

The currently authenticated user's email address

The currently authenticated user's Port access token