Hi Michael Brugge,
This behavior is currently expected. The MCP Config Wizard shown in the documentation is still rolling out and isn’t enabled for all regions or tenants yet. When the feature flag isn’t active, selecting the MCP connector will only open the documentation page instead of launching the configuration wizard. This is why you’re not seeing the OAuth 2.0 Dynamic Discovery setup flow.
At the moment, the only available workaround is to add the MCP server manually using the Custom MCP Server option. However, you’re correct that the manual flow does not support OAuth 2.0 Dynamic Discovery, so the wizard is required for that scenario. If your tenant has not received the feature rollout, the wizard will not appear.
If this capability is required for your deployment, the recommended next step is to open a support ticket so your tenant can be checked for rollout status and feature enablement.
Relevant Documentation
- • Add an existing MCP server to your agent
- • Extend your agent with Model Context Protocol (MCP overview)
Thank you.
Karan Shewale.
If this response resolves your issue, please Accept the answer and, if helpful, click the “Upvote” button. Your feedback helps us improve and assist others more effectively.