Enable static request headers for Cowork custom connectors

[Ciaran411]

Problem Statement

Surface: Claude Cowork

The Add custom connector dialog exposes only OAuth Client ID and OAuth
Client Secret. It does not expose the Request headers section documented
for the static_headers beta.

My trusted personal remote MCP server is reachable and authenticates using
the x-brain-key request header. The same endpoint is working successfully
from Claude Code using header authentication.

Proposed Solution

Request:

1. Enable the static_headers beta for my account/Cowork surface.
2. Confirm whether x-brain-key is permitted by the request-header allowlist,
   or add it to the allowlist.

I do not want to place the credential in the URL, remove authentication, or
introduce an unnecessary proxy. It's early in the project and I'd rather not move to full OAuth yet if I can avoid it. Thanks in advance!

Alternatives Considered

No response

Area

OAuth / Authentication

Priority

Medium - Would be helpful

Additional Context

No response

[cre8tivemarketing]

Also hitting this. Trying to add a custom connector for 21st.dev's Magic MCP server, which authenticates via a static x-api-key header (already on your documented allowlist) — no OAuth support on their end at all. The "Add custom connector" dialog only shows OAuth Client ID/Secret in Advanced settings; no Request headers section is visible on my account. Would like the static_headers beta enabled if possible.

[andi-christ]

+1
Need this very soon to wire up an MCP and avoid an evening of OAuth config

[Ciaran411]

Following up to see if enabling the static_headers beta is possible?

[k290]

Also need this for google stitch's X-Goog-Api-Key