hugocasaandClaude Opus 5 0cd9306068 feat: add an instance setting to refuse a token in MCP URLs ...

MCP clients are commonly configured with the token in the URL
(`/api/mcp/w/{workspace}/mcp?token=...`). A URL-borne credential ends up in
browser history, proxy logs and referrers, so an instance can now turn that
channel off with the `mcp_disable_token_query_param` global setting and leave
the Authorization header as the only way in, which sends MCP clients through
the OAuth flow the endpoints already advertise.

The rejection is a middleware on both the workspaced and the gateway MCP
mounts, layered outside everything that reads a token and inside the
WWW-Authenticate layer, so the 401 carries the resource pointer a client needs
to start OAuth discovery.

Off by default. With it on, the token drawer and the home connect drawer stop
offering to mint a token for an MCP URL and hand over the bare URL instead.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>

2026-09-16 10:29:21 +02:00

..

src

feat: add an instance setting to refuse a token in MCP URLs

2026-09-16 10:29:21 +02:00

Cargo.toml

nit enterprise implies license feature

2026-07-02 06:01:22 +00:00