User-Supplied Values For Connection Headers

HTTP headers on a remote MCP server can now be configured as user inputs rather than fixed literal values. When a header is set to expect user input, the person connecting to the server is prompted to provide the value at connection time - instead of the value being baked into shared configuration.

Why it matters

Some headers carry per-user secrets - API keys, personal access tokens, tenant identifiers - that shouldn't be shared across everyone using a server. Marking a header as user input keeps those values out of the shared setup and collects them from each user individually.

What changed

• The header editor in the server details view now lets you mark a header value as user input instead of a fixed literal.
• Headers configured this way are resolved per user when connecting, alongside the existing environment-variable resolution.
• Users are prompted to fill in the required header values before the connection is established.

Backward-compatible: Headers with fixed literal values continue to work exactly as before; user input is an opt-in per header.