Document MCP preset servers and fixed OAuth callback port range#11428
Conversation
retran
force-pushed
the
av-mcp-presets-oauth-port
branch
from
144019a to
12bc0ac
Compare
| ##### Callback URL {#callback-url} | ||
|
|
||
| The OAuth callback URL format is `http://localhost:{port}/mcp/oauth/callback`. The port is assigned by Studio Pro's built-in web server. You can find the actual port within the callback URL that Studio Pro generates when you add the server. | ||
| The OAuth callback URL format is `http://localhost:{port}/mcp/oauth/callback`. Studio Pro uses a fixed port from the range **44380–44384** — one port per running Studio Pro instance. You can find the exact port in the callback URL that Studio Pro shows when you add the server. |
There was a problem hiding this comment.
Adding a server comes after registering the app. The callback URL is required while registering the app. How does the user access to this callback URL?
There was a problem hiding this comment.
It is already fixed, doc has list of callback urls.
|
@retran Is this for 11.12? |
| Use `--mcp-oauth-ports` to override the port range (for example, `--mcp-oauth-ports=44380-44384` or `--mcp-oauth-ports=44380,39321`). | ||
|
|
||
| {{% alert color="warning" %}} | ||
| A custom port range breaks compatibility with the [OAuth Client ID Metadata Document (SEP-991)](https://modelcontextprotocol.io/seps/991-enable-url-based-client-registration-using-oauth-c) — MCP servers that validate the callback URL against this document will reject the authorization. |
There was a problem hiding this comment.
Does this mean that users can't use custom ports when there's a validation at server's end and no other way around it?
There was a problem hiding this comment.
Yes, exactly. For servers that enforce SEP-991 validation, custom ports will always be rejected — the metadata document is hosted by Mendix and lists only 44380–44384 as valid callback URLs, so there's no workaround from the user side. The --mcp-oauth-ports flag is only useful for servers that don't enforce this validation, such as internal or self-hosted servers. I've updated the docs to make this clear.
retran
force-pushed
the
av-mcp-presets-oauth-port
branch
2 times, most recently
from
f2e709b to
b58203f
Compare
|
@quinntracy Yes. |
|
@retran thank you. Please let me know when the review is done so I can take a look. |
|
@retran do we also want to explain what the new "Mendix Identity" option entails? |
retran
force-pushed
the
av-mcp-presets-oauth-port
branch
from
97f367f to
f7c987c
Compare
@KONRADS098 Fixed. |
|
@quinntracy I think review is done. |
|
|
||
| Studio Pro adds the **Mendix Marketplace** connection automatically when you open the MCP Client panel. It authenticates with your Mendix ID — no extra credentials needed. All Marketplace tools are enabled by default. | ||
|
|
||
| Mendix manages this connection. You cannot remove it, but you can disable it with the checkbox on its card. |
There was a problem hiding this comment.
Hi @retran Do we have checkbox on the card? This is not clear
There was a problem hiding this comment.
Hi! Yes, we have. I tried to make text clearer.
retran
force-pushed
the
av-mcp-presets-oauth-port
branch
from
6a84e02 to
c19bd4b
Compare
5 participants
Summary
--web-server-portlanguage with fixed port range 44380–44384; documents--mcp-oauth-portsoverride flag with link to SEP-991 compatibility warning