[Bug for MCP&API]: 自定义 MCP 功能是否支持标准 MCP oauth 协议？

Basic Information - Models Used

MiniMax Agent

Basic Information - Scenario Description

No response

Is this bug known and solvable?

• I have followed the GitHub READMEs for Minimax-MCP and Minimax-MCP-JS.
• I have checked the official Minimax documentation and existing GitHub issues，but found no solution.

Information about environment

Minimax Agent 网页版

Trace-ID in the request head

None

Description

Minimax Agent 的自定义 MCP 功能采用的是标准 MCP 协议吗？我开发了一个 MCP 服务（https://aigc.ximalaya.com/audiobooklm/mcp），采用了 MCP 协议的标准 oauth 并兼容了普通的 BearToken 方式，但想要在网页添加这个自定义 MCP 服务，但是显示：Failed to get oauth authorization url，我在网上没有找到任何有用的文档，也联系不上 Minimax 的技术服务支持（Lark 无人响应）

标准客户端应直接填写 MCP server URL：

https://aigc.ximalaya.com/audiobooklm/mcp

服务会自动暴露以下 discovery 地址：

https://aigc.ximalaya.com/.well-known/oauth-protected-resource/audiobooklm/mcp
https://aigc.ximalaya.com/.well-known/oauth-authorization-server/audiobooklm/oauth

OAuth 端点：

https://aigc.ximalaya.com/audiobooklm/oauth/authorize
https://aigc.ximalaya.com/audiobooklm/oauth/token
https://aigc.ximalaya.com/audiobooklm/oauth/introspect

<img width="1852" height="600" alt="Image" src="https://github.com/user-attachments/assets/c9468fee-259f-4a15-933b-8c83f2d28641" />

<img width="2212" height="1434" alt="Image" src="https://github.com/user-attachments/assets/be768b5d-1fae-4fd6-83b7-74508eca0105" />

Start by reading the linked Minimax-MCP and Minimax-MCP-JS READMEs and the official MiniMax documentation, then reproduce adding the provided MCP server URL in the MiniMax Agent web interface. Compare the OAuth discovery and endpoint behavior shown in the issue with what the custom MCP integration expects; done means documenting whether standard MCP OAuth is supported and identifying the cause of the authorization-URL failure.