MCP details save failed: Registration method cannot be changed after OAuth setup is complete

vuong: > Now we want to submit another version 1.1.0 which use the server on /api/v1/chatgpt-app/1.1.0. We make some update to our oauth which now support CIMD. When we prepare submission, the oauth automatically resolve and lock to “CIMD”. > > I believe the error “MCP details save failed: Registration method cannot be changed after OAuth setup is complete.” is related to oauth changed to “CIMD”; but that field is not editable. Hi there! I’m not entirely sure I understand what you’re saying here, but I’m interpreting it as you’re trying to switch from DCR to CIMD. In that case, that’s something that we don’t allow because it would break the authorization credentials for existing users and require everyone to re-authenticate. If you have any thoughts as to why this shouldn’t be the case and/or how we should be supporting this switch, I’m definitely open to hearing suggestions.