When converting APIs to MCP, consider allowing a single MCP to bind to multiple backend services.

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 a "one scenario, one MCP" logic.

API转为MCP的时候，可以考虑一个MCP支持绑定多个后端服务： 现在一个MCP只能绑定一个后端服务，但是一个MCP下面可能包含多个Tools，并不能保证这个MCP下的Tools对应的API都在同一个后端服务下面，如果分开创建多个MCP，那么skill调用的时候很不方便，也不能按照一个场景一个MCP的逻辑来聚合Tools。