在将 API 转换为 MCP 时,请考虑允许单个 MCP 绑定到多个后端服务。

Currently, an MCP can only bind to one backend service; however, an MCP may contain multiple tools, and there is no guarantee that the APIs corresponding to these tools all reside on the same backend service. Creating separate MCPs for each service would make skill invocation inconvenient and prevent the aggregation of tools based on the "one scenario, one MCP" logic.