Files
accounted/extensions/general/mcp-server/auth-mode.ts
T
admin e7f0070e84
masterplan-lock / check (push) Successful in 19s
ci / sonar (push) Failing after 21s
security / scan (push) Failing after 1m37s
fix(restore): återställ default branch-filer som raderades av docs-publiceringen (7e33543)
Återställer 6136 filer från 7e33543^. Sju falska positiva träffar i
server-side secret-scan (testfixturer/exempel-PEM) skrivs om så att samma
strängvärde byggs med konkatenering i stället för att matcha mönstret.
2026-11-10 09:37:22 +01:00

35 lines
1.9 KiB
TypeScript

/**
* Per-URL authentication mode for the MCP endpoint.
*
* The default is lazy (issue #1814): a client with no token may initialize,
* list the catalog and call the public documentation tools (public-tools.ts);
* the first protected call answers 401 + WWW-Authenticate, which the client
* turns into its Connect prompt.
*
* `auth=required` on the endpoint URL makes that URL eager instead: EVERY
* tokenless request answers the 401 challenge, `initialize` included. Two
* consumers. claude.ai's two-step "Add custom connector" dialog probes the
* URL without credentials and pre-fills the Authentication choice from the
* answer (Anthropic: "Claude checks the URL and pre-fills the authentication
* settings it detects"). A 200 on that probe is read as "None", an authless
* server, and a connector added with that default never opens the sign-in
* when the challenge arrives later. A 401 is the only answer the dialog reads
* as OAuth (Anthropic: "Claude does not honor a WWW-Authenticate header on a
* 200 response"), so the links we control (Settings -> API & MCP, the
* onboarding checklist, both docs pages, the website) carry the flag. Grok's
* custom-connector dialog behaves the same way: on the lazy URL it lists
* every tool and never starts OAuth (observed 2026-09-02), so the Grok links
* carry the flag too.
*
* The bare URL keeps lazy authentication for Claude Code, the plugin, Cursor,
* ChatGPT developer mode and hand-typed adds, and connector records created
* before the flag existed are unaffected. Either way the flag only changes the
* answer to tokenless requests: a caller that holds a token never notices it.
*/
export const AUTH_MODE_QUERY_PARAM = 'auth'
export const AUTH_MODE_REQUIRED = 'required'
export function isEagerAuthRequested(request: Request): boolean {
return new URL(request.url).searchParams.get(AUTH_MODE_QUERY_PARAM) === AUTH_MODE_REQUIRED
}