Repository navigation
docs(self-host): MCP_URL also turns on OAuth issuer identification - #264
giladresisi wants to merge 1 commit into
Conversation
MCP_URL is now read by the backend too: when set to a valid URL it turns on RFC 9207 issuer identification for the MCP OAuth server, which Codex CLI needs when the frontend and backend differ in domain or port. The row explains what value to use, that a second hostname proxying to the same backend breaks issuer validation, that an invalid value is ignored and reported at startup, and that leaving it unset keeps it off. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
|
No actionable comments were generated in the recent review. Walkthrough
Merge Risk:
|
This page describes behavior that ships with that PR. Merging earlier would document an
MCP_URLeffect the released backend does not have yet.What kind of change does this PR introduce?
Documentation (self-host configuration reference). Rewrites the
MCP_URLrow inself-host/configuration/reference.mdx: the value is the public URL of the MCP server includinghttps://(the backend URL in a standard install); set on the backend too, it turns on OAuth issuer identification (RFC 9207), which Codex CLI needs whenFRONTEND_URLandNEXT_PUBLIC_BACKEND_URLdiffer in domain or port; it must not be a second hostname proxying to the same backend; an invalid value is ignored and reported at startup; leaving it unset keeps the feature off. No other row or page changes.Why was this change needed?
Companion to gitroomhq/postiz-app#2092, where
MCP_URLstops being frontend-only: the backend uses it to advertise RFC 9207 issuer identification and to build theissparameter on authorization redirects. Self-hosters who already setMCP_URLfor the frontend get the feature turned on, so the row has to say what the value must be and what breaks it.Other information:
The behavior described here was verified against a local install of that PR: a valid
MCP_URLenables issuer identification and Codex CLI signs in; a value without a scheme is reported at startup as "MCP_URL is not a valid URL" and leaves the feature off; withMCP_URLunset nothing changes.QA
MCP_URLunder "Public API & MCP"https://, to use the backend URL in a standard install, that Codex CLI needs it only when the frontend and backend differ in domain or port, that a second hostname proxying to the same backend breaks the sign-in, that an invalid value is ignored and reported at startup, and that leaving it unset keeps it offChecklist:
🤖 Generated with Claude Code
Summary by CodeRabbit
MCP_URLaffects the displayed endpoint and OAuth issuer identification, including guidance for standard installs and setups with different frontend and backend addresses.