Service node deployment methods, systems, devices, equipment, and storage media

Abstract

This application discloses a service node deployment method, system, apparatus, device, and storage medium, which can improve the deployment and debugging efficiency of service nodes. The method includes: acquiring MCP Server configuration information and service resource resource configuration information; generating deployment parameters for running the MCP Server and service resources; sending the deployment parameters to a target server, so that the target server deploys the corresponding runtime environment of the MCP Server based on the deployment parameters; responding to debugging instructions for service resources, performing debugging operations based on the runtime environment, and obtaining debugging results; when the debugging results indicate that the service resources meet preset operating conditions, sending a service node construction request to the target server, so that the target server constructs an MCP Server node in a pending state and generates node metadata for the MCP Server node; receiving the node metadata sent by the target server, and registering the node metadata with the MCP Server management platform.

Description

Technical Field

[0001] This application relates to the field of service node deployment technology, and in particular to a service node deployment method, system, device, equipment and storage medium. Background Technology

[0002] In related technologies, the demand for models to call external tools, databases, and other service resources to complete complex tasks is constantly increasing. Traditional service resource access methods usually require developers to manually implement deployment, interface adaptation, and data format conversion in different system environments. This is not only complex and technically challenging, but also prone to problems such as inconsistent environments and mismatched interface parameters during service configuration, debugging, and updates, resulting in long deployment cycles, low efficiency, and poor operational stability. Summary of the Invention

[0003] This application provides a service node deployment method, system, apparatus, device, and storage medium, which can improve the deployment and debugging efficiency of service nodes. The above technical solution is as follows:

[0004] In a first aspect, embodiments of this application provide a service node deployment method, applied to a platform client device, including:

[0005] The MCP Server configuration page is displayed through the MCP Server management platform running on the platform client devices;

[0006] The MCP Server configuration information determined by the user and the resource configuration information of the service resources associated with the MCP Server configuration information are obtained through the MCP Server configuration page. The resource configuration information includes input mapping rules, output mapping rules and interface description information.

[0007] Deployment parameters for running the MCP Server and service resources are generated based on the MCP Server configuration information and resource configuration information.

[0008] The deployment parameters are sent to the target server so that the target server can deploy the corresponding runtime environment of the MCP Server based on the deployment parameters.

[0009] In response to debugging commands for service resources, debugging operations are performed based on the runtime environment to obtain debugging results;

[0010] If the debugging results indicate that the service resources meet the preset operating conditions, a service node construction request is sent to the target server so that the target server can construct an MCP Server node in a state of waiting to be called based on the service node construction request, and generate node metadata of the MCP Server node. The MCP Server node is used to host service resources and respond to the call request of the target model to execute the corresponding resource service task.

[0011] Receive node metadata sent by the target server and register the node metadata with the MCP Server management platform. The node metadata is used to identify the MCP Server node and provide call routes for the MCP Server node.

[0012] In one possible implementation, the user-defined MCP Server configuration information and the resource configuration information of the service resources associated with the MCP Server configuration information are obtained through the MCP Server configuration page, including:

[0013] Obtain initial MCP Server information through the MCP Server configuration page; perform validity verification on the initial MCP Server information and obtain the verification result; if the verification result indicates that the initial MCP Server information has passed the verification, generate MCP Server configuration information in the MCP Server management platform based on the initial MCP Server information; respond to the service resource registration instruction for the MCP Server configuration information and obtain the resource configuration information of the service resources associated with the MCP Server configuration information.

[0014] In one possible implementation, in response to a service resource registration instruction for MCP Server configuration information, resource configuration information of the service resource associated with the MCP Server configuration information is obtained, including:

[0015] In response to a service resource registration command targeting the MCP Server configuration information, a service resource registration context is generated. This context is used to define the interaction constraints between the service resource and the MCP Server configuration information. Within this context, the input mapping rule editing component, output mapping rule editing component, and interface description information entry component corresponding to the service resource are loaded. The user-defined input mapping rules are obtained through the input mapping rule editing component, the user-defined output mapping rules are obtained through the output mapping rule editing component, and the interface description information is obtained through the interface description information entry component. The input mapping rules, output mapping rules, and interface description information are then integrated to obtain the resource configuration information of the service resource associated with the MCP Server configuration information.

[0016] In one possible implementation, within the service resource registration context, the input mapping rule editing component, output mapping rule editing component, and interface description information entry component corresponding to the service resource are loaded, including:

[0017] Obtain the resource type of the service resource; determine the target configuration template identifier based on the resource type; obtain the resource configuration interface template that matches the service resource according to the target configuration template identifier; render the resource configuration interface template file into an interactive page, and display the input mapping rule editing component, output mapping rule editing component, and interface description information entry component corresponding to the service resource through the interactive page.

[0018] In one possible implementation, deployment parameters for running the MCP Server and its service resources are generated based on the MCP Server configuration information and resource configuration information, including:

[0019] The MCP Server configuration information is processed through structured parsing to obtain the MCP Server running parameter information; the resource configuration information is processed through rule-based parsing to generate interface configuration information compatible with the MCP Server's operating environment; and the MCP Server running parameter information and interface configuration information are associated and mapped to generate deployment parameters for running the MCP Server and service resources.

[0020] In one possible implementation, in response to a debugging command for a service resource, debugging operations are performed based on the runtime environment to obtain debugging results, including:

[0021] In response to debugging commands for service resources, a debugging page is displayed; sample input data is generated based on input mapping rules and displayed on the debugging page; after detecting a user's confirmation command for the sample input data, the sample input data is converted into a request format matching the MCP Server using input mapping rules, and a debug call request is sent to the target server so that the target server generates debug output data based on the debug call request in the runtime environment; the debug output data returned by the target server is obtained, and the debug output data is parsed and processed according to the output mapping rules to generate debugging results.

[0022] In one possible implementation, the method also includes:

[0023] If the debugging results indicate that the service resources do not meet the preset operating conditions, the following steps are taken: 1) Determine the abnormal operating configuration item corresponding to the MCPServer based on the debugging results; 2) Display the abnormal operating configuration item through the abnormal configuration modification page; 3) Obtain the first modification information determined for the abnormal operating configuration item; 4) Update the deployment parameters based on the first modification information to generate the updated deployment parameters; 5) Return to the execution step of sending the deployment parameters to the target server so that the target server can deploy the operating environment corresponding to the MCPServer based on the deployment parameters.

[0024] In one possible implementation, after registering the node metadata with the MCP Server management platform, the method also includes:

[0025] In response to a modification request for service resources, a service resource modification page is displayed; second modification information is obtained through the service resource modification page; deployment parameters are updated based on the second modification information to generate updated deployment parameters; based on the updated deployment parameters, the process returns to execute the steps of sending the deployment parameters to the target server so that the target server can deploy the runtime environment corresponding to the MCP Server based on the deployment parameters.

[0026] Secondly, embodiments of this application provide a service node deployment method, applied to a target server, including:

[0027] The platform client device receives deployment parameters sent by the platform client device. These deployment parameters are generated by the platform client device based on the MCPServer configuration information and resource configuration information, and are used to run the MCP Server and the service resources associated with the MCP Server configuration information. The MCP Server configuration information and resource configuration information are information obtained by the platform client device through the MCP Server configuration page. The MCP Server configuration page is a page displayed by the platform client device through the MCP Server management platform running on the platform client device.

[0028] Deploy the corresponding runtime environment for the MCP Server based on the deployment parameters;

[0029] The system receives a service node construction request from the platform client device, constructs an MCP Server node in a pending call state based on the service node construction request, and generates node metadata for the MCP Server node. The MCP Server node is used to host service resources and respond to the call request of the target model to execute the corresponding resource service task. The service node construction request is a request sent by the platform client device when the debugging result indicates that the service resource meets the preset operating conditions. The debugging result is the result obtained by the platform client device in response to the debugging instructions for the service resource based on the running environment for debugging operations.

[0030] The node metadata is sent to the platform client device so that the platform client device can register the node metadata with the MCP Server management platform running on the platform client device. The node metadata is used to identify the MCP Server node and provide call routes for the MCP Server node.

[0031] Thirdly, embodiments of this application provide a service node deployment system, including: a platform client device and a target server; wherein,

[0032] The platform client device is used to display the MCP Server configuration page through the MCP Server management platform running on the platform client device; obtain the user-defined MCP Server configuration information and the resource configuration information of the service resources associated with the MCP Server configuration information through the MCP Server configuration page, including input mapping rules, output mapping rules and interface description information; generate deployment parameters for running the MCP Server and service resources based on the MCP Server configuration information and resource configuration information; and send the deployment parameters to the target server.

[0033] The target server is used to receive deployment parameters sent by the platform client device, deploy the corresponding runtime environment of MCPServer based on the deployment parameters; and to receive service node construction requests sent by the platform client device, construct an MCP Server node in a pending call state based on the service node construction request, generate node metadata of the MCP Server node, and send the node metadata to the platform client device. The MCP Server node is used to host service resources and respond to the call requests of the target model to execute the corresponding resource service tasks.

[0034] The platform client device is also used to receive node metadata sent by the target server and register the node metadata with the MCP Server management platform. The node metadata is used to identify the MCP Server node and provide call routes for the MCP Server node.

[0035] Fourthly, embodiments of this application provide a service node deployment apparatus, applied to a platform client device, comprising:

[0036] The first display module is used to display the MCPServer configuration page through the MCPServer management platform running on the platform client device;

[0037] The first acquisition module is used to acquire the user-defined MCP Server configuration information and the resource configuration information of the service resources associated with the MCP Server configuration information through the MCP Server configuration page. The resource configuration information includes input mapping rules, output mapping rules and interface description information.

[0038] The generation module is used to generate deployment parameters for running the MCP Server and service resources based on the MCP Server configuration information and resource configuration information.

[0039] The first sending module is used to send deployment parameters to the target server so that the target server can deploy the corresponding runtime environment of MCP Server based on the deployment parameters;

[0040] The debugging module is used to respond to debugging commands for service resources, perform debugging operations based on the runtime environment, and obtain debugging results.

[0041] The second sending module is used to send a service node construction request to the target server when the debugging results indicate that the service resources meet the preset operating conditions. This allows the target server to construct an MCP Server node in a state of waiting to be called based on the service node construction request, and generate node metadata of the MCP Server node. The MCP Server node is used to carry service resources and respond to the calling request of the target model to execute the corresponding resource service task.

[0042] The registration module is used to receive node metadata sent by the target server and register the node metadata with the MCPServer management platform. The node metadata is used to identify the MCP Server node and provide call routes for the MCP Server node.

[0043] Fifthly, embodiments of this application provide a service node deployment apparatus, applied to a target server, comprising:

[0044] The receiving module is used to receive deployment parameters sent by the platform client device. The deployment parameters are the deployment parameters for running the MCP Server and the service resources associated with the MCP Server configuration information, generated by the platform client device based on the MCP Server configuration information and resource configuration information. The MCP Server configuration information and resource configuration information are the information obtained by the platform client device through the MCP Server configuration page. The MCP Server configuration page is the page displayed by the platform client device through the MCP Server management platform running on the platform client device.

[0045] The deployment module is used to deploy the runtime environment corresponding to the MCP Server based on the deployment parameters;

[0046] The construction module is used to receive service node construction requests sent by the platform client device, and to construct an MCP Server node in a state of waiting to be called based on the service node construction request, as well as generate node metadata of the MCP Server node. The MCP Server node is used to carry service resources and respond to the call requests of the target model to execute the corresponding resource service tasks. The service node construction request is a request sent by the platform client device when the debugging result indicates that the service resource meets the preset running conditions. The debugging result is the result obtained by the platform client device in response to the debugging instructions for the service resource and the debugging operation based on the running environment.

[0047] The third sending module is used to send node metadata to the platform client device, so that the platform client device can register the node metadata with the MCP Server management platform running on the platform client device. The node metadata is used to identify the MCP Server node and provide call routes for the MCP Server node.

[0048] In a sixth aspect, embodiments of this application provide an electronic device, including: a processor and a memory; the memory stores a computer program, and the processor executes the computer program to implement the method steps provided in the first or second aspect of embodiments of this application.

[0049] In a seventh aspect, embodiments of this application provide a computer storage medium storing a plurality of instructions adapted for loading by a processor and executing the method steps provided in the first or second aspect of embodiments of this application.

[0050] The service node deployment method provided in this application embodiment displays an MCP Server configuration page through a platform client device using an MCP Server management platform; it obtains user-defined MCP Server configuration information and resource configuration information of service resources associated with the MCP Server configuration information through the MCP Server configuration page, including input mapping rules, output mapping rules, and interface description information; it generates deployment parameters for running the MCP Server and service resources based on the MCP Server configuration information and resource configuration information, and then sends the deployment parameters to the target server so that the target server deploys the corresponding runtime environment of the MCP Server based on the deployment parameters; in response to debugging instructions for service resources, it performs debugging operations based on the runtime environment to obtain debugging results; when the debugging results indicate that the service resources meet preset running conditions, it sends a service node construction request to the target server so that the target server constructs an MCP Server node in a pending call state based on the service node construction request, and generates node metadata for the MCP Server node. The MCP Server node is used to host service resources and respond to the call requests of the target model to execute the corresponding resource service tasks; it receives the node metadata sent by the target server and registers the node metadata with the MCP Server management platform. The node metadata is used to identify the MCP Server node and provide information for the MCP Server. Server node call routing enables automated configuration, deployment, and management of the MCP Server and its associated service resources. Through the MCP Server management platform on the platform's client devices, a visual low-code configuration platform is provided, allowing users to complete the entire process from configuration entry, parameter generation, environment deployment to debugging and verification, service node construction and registration within a unified interface. This reduces the complexity of manual configuration and improves service deployment and debugging efficiency. Furthermore, service nodes are only constructed into a call-ready state after meeting preset operating conditions, improving service stability and reliability. The registration of node metadata and the establishment of call routes enable the target model to quickly and accurately access service resources based on unified routing, enhancing the flexibility and scalability of service node calls. Attached Figure Description

[0051] To more clearly illustrate the technical solutions in the embodiments of this application, the accompanying drawings used in the embodiments will be briefly introduced below. Obviously, the drawings described below are only some embodiments of this application. For those skilled in the art, other drawings can be obtained based on these drawings without creative effort.

[0052] Figure 1A schematic diagram of an application environment for a service node deployment method provided as an exemplary embodiment of this application;

[0053] Figure 2 A flowchart illustrating a service node deployment method provided as an exemplary embodiment of this application;

[0054] Figure 3 A flowchart illustrating another service node deployment method provided as an exemplary embodiment of this application;

[0055] Figure 4 A schematic diagram of a service list page provided for an exemplary embodiment of this application;

[0056] Figure 5 A schematic diagram of an MCP Server configuration page provided for an exemplary embodiment of this application;

[0057] Figure 6 A schematic diagram of a resource configuration page provided for an exemplary embodiment of this application;

[0058] Figure 7 A flowchart illustrating another service node deployment method provided as an exemplary embodiment of this application;

[0059] Figure 8 A schematic diagram of a debugging page provided for an exemplary embodiment of this application;

[0060] Figure 9 A schematic diagram of the structure of a first service node deployment apparatus provided for an exemplary embodiment of this application;

[0061] Figure 10 A schematic diagram of the structure of a second service node deployment apparatus provided in an exemplary embodiment of this application;

[0062] Figure 11 A schematic diagram of the structure of an electronic device provided as an exemplary embodiment of this application;

[0063] Figure 12 This is a schematic diagram of the structure of another electronic device provided as an exemplary embodiment of this application. Detailed Implementation

[0064] In order to make the purpose, technical solutions and advantages of this application more clear, the following further describes this application in detail with reference to the accompanying drawings and embodiments. It should be understood that the specific embodiments described herein are only used to explain this application and are not intended to limit this application.

[0065] In the description of this application, it should be understood that the terms "first," "second," etc., are used for descriptive purposes only and should not be construed as indicating or implying relative importance. Those skilled in the art can understand the specific meaning of the above terms in this application based on the specific circumstances. Furthermore, in the description of this application, unless otherwise stated, "multiple" refers to two or more. "And / or" describes the relationship between related objects, indicating that three relationships can exist. For example, A and / or B can represent: A existing alone, A and B existing simultaneously, or B existing alone. The character " / " generally indicates that the preceding and following related objects are in an "or" relationship.

[0066] In order to more clearly describe the technical solutions of the embodiments of this application, some concepts in this application will be described in detail before the description in order to better understand the solution.

[0067] Model Context Protocol (MCP): A generic interface designed for the context information required by a model, defining a set of generic communication protocols, data formats, and rules.

[0068] Model Context Protocol Server (MCP Server) is a service that provides MCP for Artificial Intelligence (AI).

[0069] In related technologies, the need for models to call external tools, databases, and other service resources to complete complex tasks is constantly increasing. For example, when a target model (such as a large language model) on a food delivery platform needs to have the ability to query merchant information, obtain order status, and schedule delivery tasks, it is necessary to configure service resources corresponding to the above capabilities for the target model (such as "merchant information database", "order status query tool", "delivery scheduling service", etc.). Traditional service resource access methods usually require model developers to manually implement deployment, interface adaptation, and data format conversion in different system environments. This process is not only complex and technically challenging, but also prone to problems such as inconsistent environments and mismatched interface parameters when configuring, debugging, and updating service nodes, resulting in long deployment cycles, low efficiency, and poor operational stability.

[0070] Therefore, this application provides a service node deployment method, system, apparatus, device, and storage medium to solve the aforementioned technical problems of low service node deployment efficiency and debugging efficiency.

[0071] The service node deployment method provided in this application embodiment can be applied to, for example, Figure 1In the application environment shown, the platform client device 10, the target server 20, and the terminal device 30 communicate via a network.

[0072] The platform client device 10 can run an MCP Server management platform. The MCP Server management platform is a service management and configuration system running on the platform client device. It can be used to uniformly configure, deploy, debug and register the MCP Server and its associated service resources.

[0073] The target server 20 can be a computing device used to run the MCP Server and host service nodes, such as a cloud server, data center server, or a locally deployed high-performance server. It can build a runtime environment and execute resource service tasks based on deployment parameters sent by the platform client device. The target server 20 is the backend server corresponding to the service resources. The data storage system can store the data that the target server 20 needs to process, such as merchant information data. The data storage system can be integrated onto the target server 20 or placed on the cloud or other network servers.

[0074] Terminal device 30 can be a user-side device used to initiate service call requests, such as a personal computer, smartphone, tablet, or other smart terminal with network communication capabilities. It can be used to send task requests to service nodes deployed on the target server through the call interface and receive execution results. Specifically, terminal device 30 can run a target model, such as the target model (e.g., a large language model) on a food delivery platform, and can call external service resources to perform functions such as querying merchant information, obtaining order status, and scheduling delivery tasks.

[0075] In some possible embodiments, the platform client device 10 displays an MCP Server configuration page through the MCPServer management platform running on the platform client device 10; it obtains the user-determined MCPServer configuration information and the resource configuration information of the service resources associated with the MCP Server configuration information through the MCP Server configuration page, the resource configuration information including input mapping rules, output mapping rules, and interface description information; it generates deployment parameters for running the MCP Server and service resources based on the MCP Server configuration information and resource configuration information; it sends the deployment parameters to the target server 20 so that the target server 20 deploys the corresponding runtime environment of the MCP Server based on the deployment parameters; it performs debugging operations based on the runtime environment in response to debugging instructions for the service resources and obtains debugging results; when the debugging results indicate that the service resources meet the preset running conditions, it sends a service node construction request to the target server so that the target server 20 constructs an MCP Server node in a pending call state based on the service node construction request and generates node metadata of the MCP Server node, the MCP Server node is used to carry service resources and respond to the call requests of the target model (running on the terminal device 30) to execute the corresponding resource service tasks; it receives the node metadata sent by the target server 20 and registers the node metadata with the MCP. The server management platform uses node metadata to identify MCP server nodes and provides call routes for MCP server nodes.

[0076] Understandably, both the platform client device 10 and the terminal device 30 can be implemented as a single terminal device or a terminal cluster consisting of multiple terminals. The target server 20 can be implemented as a standalone server or a server cluster consisting of multiple servers.

[0077] In one embodiment, such as Figure 2 As shown, a service node deployment method is provided, which can be applied to... Figure 1 The following steps are used as an example to illustrate the application environment shown:

[0078] S201: Display the MCP Server configuration page through the MCP Server management platform running on the platform client device.

[0079] Among them, the platform client device can be a terminal for user use (such as personal computer, laptop, operation and maintenance workstation, etc.). The platform client device can run the MCP Server management platform. The MCP Server management platform is a service management and configuration system running on the platform client device. It can be used to uniformly configure, deploy, debug and register the MCP Server and its associated service resources.

[0080] Optionally, the above users can be administrator users (such as developers, configuration personnel, or platform operation and maintenance personnel of the MCP Server management platform).

[0081] Optionally, the MCP Server configuration page can be a graphical editing interface in the MCP Server management platform, which can be used to collect configuration parameters related to the MCP Server.

[0082] S202: Obtain the user-defined MCP Server configuration information and the resource configuration information of the service resources associated with the MCP Server configuration information through the MCP Server configuration page. The resource configuration information includes input mapping rules, output mapping rules, and interface description information.

[0083] Optionally, the MCP Server configuration information can be used to describe the identity and operating environment of the MCP Server itself.

[0084] Optionally, input mapping rules can be used to convert input information from the target model or terminal device into standardized request parameters that conform to the target interface call requirements. This includes renaming fields, converting value types, filling in default values, and injecting authentication information, ensuring the target interface can correctly receive and parse the request data. Output mapping rules can be used to format the raw response results returned by the target interface. This includes filtering and renaming response fields, simplifying complex nested structures, semantically converting enumerated values ​​or status codes, and performing necessary desensitization operations, generating concise, standardized output results that are easy for the target model to understand and use. Interface description information can be used to describe the basic call attributes of the target interface, including interface type, call address or identifier, request method, required parameters, authentication method, and example input and output parameters, providing a structured basis for input and output mapping. Through the above configuration, effective integration between the target model input and the interface call format can be achieved, ensuring that the interface call results are returned in a form that conforms to the model processing logic, thereby achieving efficient management and unified calling of service resources.

[0085] In one embodiment, the resource configuration information of a service resource may also include, but is not limited to, resource identifier, resource name, resource description information, and resource permissions. Taking a service resource as a tool as an example, the tool's resource configuration information may include tool name, tool identifier, tool description, and tool permissions. The resource identifier can be used to uniquely identify the service resource for precise location during configuration and invocation; the resource name can be used to intuitively name the service resource, facilitating user identification and management on the configuration page; the resource description can describe the functional characteristics, applicable scenarios, and usage restrictions corresponding to the service resource, allowing users to quickly understand the resource's purpose; and resource permissions can be used to limit the scope of entities accessing and invoking the service resource, such as differentiating the usage permissions of different levels of users, ensuring the security and compliance of the service resource. Through the above configuration information, unified management and flexible control of service resources can be achieved, thereby improving the controllability and security of service deployment and invocation.

[0086] In this embodiment, the MCP Server can be a runtime platform that hosts and manages service resources, providing a unified entry point and service execution environment for the target model. Service resources are the specific functional units scheduled and run by the MCP Server, such as merchant information query services, map route planning services, and order status query services. The MCP Server itself does not directly implement specific service functions, but rather provides callable service capabilities by loading, configuring, and managing these service resources. In other words, the MCP Server configuration information defines the overall operating parameters and deployment rules of the MCP Server, while the resource configuration information of the service resources defines the functional attributes and interface rules of each specific service resource. The MCP Server configuration information and resource configuration information can be in a management relationship: the MCP Server, as the platform, is responsible for hosting and scheduling, while the service resources, as managed objects, provide the actual functions. Effectively binding service resources to the MCP Server allows the target model to indirectly use the required resource services by calling the MCP Server node in subsequent processes.

[0087] S203: Generate deployment parameters for running the MCP Server and service resources based on the MCP Server configuration information and resource configuration information.

[0088] Deployment parameters refer to the configuration information and runtime parameters required for the successful operation of the MCP Server and its associated service resources on the target server. Deployment parameters not only determine how the MCP Server's runtime environment is initialized, but also how specific service resources are loaded, scheduled, and invoked.

[0089] For example, deployment parameters may include, but are not limited to, the following categories: MCP Server running parameters (such as running port number, communication protocol type, dependent middleware information, log configuration, etc.), resource loading parameters (used to describe the mounting location and startup method of service resources, such as resource path, container image address, startup script, etc.), input / output mapping rules, interface description binding information, and resource permission parameters (used to specify which users or target model instances can access the service resource and restrict the access scope).

[0090] In one embodiment, basic parameters describing the MCP Server's operating environment can be obtained based on the MCP Server configuration information. Subsequently, by combining the resource configuration information of the service resources associated with the MCP Server configuration information, the loading method, interface description information, input mapping rules, output mapping rules, and resource permission information of the service resources are determined. Finally, the MCP Server management platform in the platform client device parses and integrates the above information and formats it into a unified deployment parameter file or script. This is used by the target server to automatically complete the initialization of the MCP Server's operating environment, the mounting and loading of service resources, and route registration, thereby enabling the MCP Server and its associated service resources to run normally in the target server and provide services to the outside world.

[0091] S204: Send the deployment parameters to the target server so that the target server can deploy the corresponding runtime environment of MCPServer based on the deployment parameters.

[0092] In one embodiment, in response to a user's instruction to specify deployment parameters, the deployment parameters are sent to the target server, for example, via a secure network transmission protocol. The deployment parameters are encapsulated in a structured data format and parsed and executed by the target server's deployment engine, thereby completing the automated deployment of the MCP Server runtime environment and its service resources.

[0093] Optionally, the target server receives deployment parameters sent by the platform client device and deploys the runtime environment corresponding to the MCP Server based on these parameters. The runtime environment can be the basic execution environment used to run the MCP Server service and related service resources. The runtime environment may include, but is not limited to: operating system environment, container runtime, dependency libraries, network configuration, and interface adaptation modules corresponding to the service resources. The runtime environment enables the MCP Server and service resources to be executable, callable, and testable on the target server.

[0094] S205: In response to a debugging command for a service resource, perform debugging operations based on the runtime environment and obtain debugging results.

[0095] Debugging commands can be issued by users or platform client devices to verify whether service resources can function properly in the deployed runtime environment. Optionally, debugging commands can include service call requests, test parameters, simulated input data, etc., to trigger the execution of the corresponding service resources.

[0096] In one embodiment, debugging commands can be triggered by the user in the debugging interface of the MCP Server management platform, such as by clicking the "Debug" button or entering a test request.

[0097] In another embodiment, debugging instructions can also be automatically generated by the system, for example, by automatically initiating a set of predefined test cases after deployment.

[0098] Optionally, the debugging results can be feedback information returned by the runtime environment after completing the debugging operation, indicating whether the service resource meets the preset operating conditions. The debugging results may include success / failure flags, or detailed feedback such as specific logs, output data, and error messages. If the debugging results meet expectations (e.g., correct output, normal interface response), it indicates that the service resource meets the operating conditions and can proceed to the subsequent service node construction phase. If the debugging results are abnormal, the developers need to correct and redeploy based on the feedback.

[0099] S206: If the debugging results indicate that the service resources meet the preset operating conditions, a service node construction request is sent to the target server so that the target server can construct an MCPServer node in a state of waiting to be called based on the service node construction request, and generate node metadata of the MCP Server node. The MCP Server node is used to carry service resources and respond to the call request of the target model to execute the corresponding resource service task.

[0100] The preset operating conditions are the standards used to determine whether a service resource can be formally deployed and invoked. These preset operating conditions may include: functional correctness (output results are consistent with expectations), interface connectivity (matches input / output mapping rules), performance metrics (response time, throughput), and stability (consistent results across multiple executions). In essence, if a service resource meets the preset operating conditions, it means that the service resource has passed basic verification and can be formally constructed as a callable service node.

[0101] Optionally, a service node build request can be used to instruct the target server to encapsulate the verified service resources into runnable and callable independent service nodes. The service node build request may include: service resource identifier, deployment parameter references, runtime environment information, node build method, etc. The purpose of the service node build request is to trigger the target server to perform a formal build operation, thereby generating the corresponding MCP Server service node.

[0102] Optionally, an MCP Server node in the pending invocation state refers to a service node that has been built on the target server but has not yet been actually invoked by the target model. At this time, the MCP Server node has operational capabilities but is in a pending invocation state. Once the MCP Server node receives an invocation request from the target model, it can immediately start and execute the corresponding resource service task. Node metadata can be structured descriptive information generated by the target server when building the MCP Server node, and may include, but is not limited to: the unique identifier of the MCP Server node, the MCP Server node address (invocation route), supported service resource types, interface description information, and MCP Server node status information. The node metadata will be registered with the MCP Server management platform for subsequent node invocation and routing management.

[0103] In one embodiment, the target model can be an intelligent model running on a terminal device, such as a large language model or a vertical domain AI model. The target model needs to invoke MCP Server service nodes to implement extended functions. For example, a large model in a food delivery scenario needs to invoke a "merchant information query service node," "order status service node," or "delivery scheduling service node" to complete end-to-end service logic. A call request is an execution request issued by the target model to the MCP Server service node, which can contain specific task instructions and input data; for example, "get the order's delivery status" can be a call request. After receiving the call request, the MCP Server node can process it according to its resource configuration and return the result (e.g., order delivery status details).

[0104] Understandably, the corresponding resource service task is the actual task logic executed by the MCP Server node after receiving the call request. It corresponds one-to-one with the function of the service resource. For example, the resource service task corresponding to the query merchant information service is to execute a database query and return the merchant details; the resource service task corresponding to the get order status service is to call the order management system application programming interface (API) and return the order progress. After the task is executed, the task result can be fed back to the target model for subsequent intelligent response.

[0105] S207: Receive node metadata sent by the target server and register the node metadata with the MCP Server management platform. The node metadata is used to identify the MCP Server node and provide call routes for the MCP Server node.

[0106] Registering node metadata with the MCP Server management platform means writing the node metadata, such as the identifier, interface description, and running status of the MCP Server node returned by the target server, into the service management database of the MCP Server management platform to achieve unified management and scheduling of nodes.

[0107] In addition, the call routing information carried in the node metadata is used to establish an addressable access path for the MCP Server node, so that the target model or other services can accurately forward requests to the corresponding service nodes based on the call route, thereby ensuring stable access to service resources and task execution.

[0108] The service node deployment method provided in this application embodiment displays an MCP Server configuration page through a platform client device using an MCP Server management platform; it obtains user-defined MCP Server configuration information and resource configuration information of service resources associated with the MCP Server configuration information through the MCP Server configuration page, including input mapping rules, output mapping rules, and interface description information; it generates deployment parameters for running the MCP Server and service resources based on the MCP Server configuration information and resource configuration information, and then sends the deployment parameters to the target server so that the target server deploys the corresponding runtime environment of the MCP Server based on the deployment parameters; in response to debugging instructions for service resources, it performs debugging operations based on the runtime environment to obtain debugging results; when the debugging results indicate that the service resources meet preset running conditions, it sends a service node construction request to the target server so that the target server constructs an MCP Server node in a pending call state based on the service node construction request, and generates node metadata for the MCP Server node. The MCP Server node is used to host service resources and respond to the call requests of the target model to execute the corresponding resource service tasks; it receives the node metadata sent by the target server and registers the node metadata with the MCP Server management platform. The node metadata is used to identify the MCP Server node and provide information for the MCP Server. Server node call routing enables automated configuration, deployment, and management of the MCP Server and its associated service resources. Through the MCP Server management platform on the platform's client devices, a visual low-code configuration platform is provided, allowing users to complete the entire process from configuration entry, parameter generation, environment deployment to debugging and verification, service node construction and registration within a unified interface. This reduces the complexity of manual configuration and improves service deployment and debugging efficiency. Furthermore, service nodes are only constructed into a call-ready state after meeting preset operating conditions, improving service stability and reliability. The registration of node metadata and the establishment of call routes enable the target model to quickly and accurately access service resources based on unified routing, enhancing the flexibility and scalability of service node calls.

[0109] In one embodiment, such as Figure 3 As shown, another method for deploying service nodes is provided, which can be applied to... Figure 1 The following steps are illustrated using the platform client device 10 as an example:

[0110] S301: Displays the MCP Server configuration page through the MCP Server management platform running on the platform client device.

[0111] In some embodiments, in response to a user-triggered service creation command, the MCP Server configuration page can be displayed through the MCP Server management platform running on the platform client device. The service creation command can be triggered by the user on the service list page by triggering the new service control. The service list page can be used to display relevant information for various services.

[0112] Figure 4 A schematic diagram of a service list page provided for an exemplary embodiment of this application, such as... Figure 4The service list page 400 can display the existing MCP Servers in the MCP Server management platform to users. Specifically, the service list page 400 can display a first navigation bar 401, which includes category controls corresponding to labels such as "Managed by Me," "Visible to Me," "All Solutions," and "Solutions Without Permissions." This can be used to categorize and display MCP Servers, making it easy for administrators to quickly filter services based on their permission levels. Taking "All Solutions" as an example, the service list page 400 can also display existing MCP Server entries, such as Merchant MCP Server entry 402, Map MCP Server entry 403, MCP Server Test entry 404, and Tool Test entry 405. Among them, the service represented by Merchant MCP Server entry 402 can be used to carry merchant-related service resources, such as merchant information query, merchant qualification verification, and product listing and delisting management. When the target model needs to obtain or process merchant information, it can call this MCP Server node to complete the corresponding task. The service represented by Map MCP Server entry 403 can be used to host geographic location and map-related service resources, such as address resolution, route planning, distance calculation, and nearby business retrieval. This map MCP can support route scheduling and location information queries in scenarios such as food delivery and travel. The service represented by MCP Server Test entry 404 can be used to provide test service resources, such as verifying whether the deployment, configuration, and invocation of the MCP Server are running normally, facilitating functional and performance debugging before going live. The service represented by Tool Test entry 405 can be used to provide general tool-type service resources, such as data format conversion, message push, log collection and analysis, to support the verification of auxiliary function calls during development and debugging. Each service entry can be displayed in card form, and the card may include, but is not limited to, the service name, service identifier, service description information, and user permission information. The user permission information is used to indicate the type of permission that the current administrator user has for the service, such as "administrator permission" or "read-only permission". Administrator users can perform operations based on the above entries, such as clicking to enter the corresponding management interface to adjust the configuration parameters of the service, or triggering a deletion operation to remove services that are no longer needed.

[0113] In addition, a search box 406 can be set in the service list page 400. The search box 406 is used to receive search information input by the user to quickly locate service items. The user can enter the service identifier (such as code), name, or description information in the search box 406, and the MCP Server management platform can perform a fuzzy match query on the service items displayed on the current page based on the search information. The query results will be triggered and displayed after the user completes the input and presses the Enter key, which makes it easier for users to quickly find the target MCP Server when there are many services, thus improving the efficiency of service retrieval and configuration.

[0114] Furthermore, the service list page 400 can also include a new service control 407. When the user triggers this control, a service creation command is initiated, and the MCP Server configuration page is displayed for creating and configuring new MCP Servers. This allows users to manage existing services and flexibly expand new ones. This MCP Server management platform significantly improves service management efficiency through intelligent categorization navigation, visual service cards, and a cluster of efficiency tools.

[0115] S302: Obtain initial information about the MCP Server through the MCP Server configuration page.

[0116] The initial information for the MCP Server allows users to configure basic descriptive parameters for the MCP Server they want to create or manage on the MCP Server configuration page. This information identifies and distinguishes different service instances and provides metadata support for subsequent service deployment and invocation. This initial information may include, but is not limited to: Service Name (a unique name to identify the MCP Server for easy user identification and management); Service Identifier (a unique identifier generated for the MCP Server or specified by the user, used for binding deployment parameters and invocation routes); Version Information (recording the MCP Server's version number to support version iteration and compatibility management); Service Description (a brief description of the MCP Server's functionality); Service Type (a configuration parameter representing the operating environment category of the created MCP Server, specifying the type of operating platform or deployment environment in which the MCP Server service will be installed and executed); and Service Permissions (limiting the scope of operations that different users can perform on the MCP Server and its service resources). Service permissions can include at least two categories: administrator permissions, which allow users with this permission to create, edit, modify, and maintain the MCP Server and its tools; read-only permissions, which allow users to view relevant configuration information and running status but not to modify them; running port number, which is the network port number used by the MCP Server to provide services to the outside world in the target operating environment; communication protocol type, which refers to the transmission protocol and format standard followed by the MCP Server when interacting with external systems or callers; middleware information, which refers to the third-party software components or basic services that the MCP Server depends on during operation, such as databases, message queues, caching services, and registry centers; log configuration, which refers to the parameter settings related to the MCP Server recording service status and running behavior during operation; and network access method, which refers to the definition of the network access mode and access path supported by the MCP Server when providing services to the outside world.

[0117] Figure 5 A schematic diagram of an MCP Server configuration page provided for an exemplary embodiment of this application, as shown below. Figure 5The MCP Server configuration page 500 may include a second navigation bar 501 for switching between different functional pages, such as the "Server Information" page and the "Tool Configuration" page. The MCP Server configuration page 500 may also include a basic information area 502, a service configuration area 503, and a permission configuration area 504. The basic information area 502 allows users to input or select information such as service identifier, service name, and service description; the service configuration area 503 allows users to input or select information such as service type; and the permission configuration area 504 allows users to input or select service permissions such as administrator or read-only member. Optionally, the service type can be any of the following: Time-Triggered Protocol (TPP), private TPP, and custom type, which can be used to indicate the runtime environment or target platform on which the MCP Server depends. Each service type can be associated with a unique TPP identifier to identify and distinguish different deployment instances, enabling the MCP Server to accurately load and run the corresponding service resources in the runtime environment. Among them, the public TPP can be used to indicate the shared runtime environment provided by the platform in advance. Users can quickly start the MCP Server based on the public TPP without deploying server resources separately, so as to realize the rapid verification and debugging of service resources. The private TPP is used to indicate the target platform deployed by the user in its own dedicated runtime environment based on the MCP Server solution. After deployment, it can provide the same tool registration and script conversion capabilities as the public TPP. It can also realize instance-level differentiation and management through a unique TPP identifier, thereby improving the independence of service operation and data security. The custom TPP is used to indicate that users can bind the MCP Server to a specific third-party runtime environment or external service resource by entering a custom Uniform Resource Locator (URL) and path information during the configuration process. This allows the MCP Server to be loaded and executed in the user-specified exclusive environment, thereby realizing flexible support for differentiated application scenarios.

[0118] On the MCP Server configuration page 500, users can complete steps such as setting the unique identifier of the MCP Server, selecting the operating environment, and assigning permissions. Users can also cancel the current operation using the cancel control 505 or submit the configuration results using the save control 506. This enables the MCP Server configuration page to obtain initial information about the MCP Server.

[0119] S303: Perform a validity check on the initial information of the MCP Server and obtain the verification result.

[0120] In one embodiment, the legitimacy verification may include at least one of the following verification methods: verifying the matching of the communication protocol type and the running port number, i.e., determining whether the communication protocol type and the running port number configured by the user in the initial information of the MCP Server conform to the preset matching rules, so as to avoid service startup anomalies caused by inconsistencies between the protocol and the port number; detecting the compatibility between the network access method and the preset security policy, i.e., checking whether the access method set by the user (such as intranet access, public network access, etc.) conforms to the security control policy stipulated by the platform, thereby ensuring the data transmission security and access compliance during the operation of the MCP Server; and confirming the uniqueness of the service identifier in the current platform, i.e., verifying whether the service identifier entered by the user conflicts with the identifiers already existing in the platform, so that each MCP Server instance can be distinguished and managed by a unique identifier. Through the above verification, service deployment failures or operational risks caused by configuration conflicts or non-compliant operations can be effectively avoided, thereby improving the stability and security of the system.

[0121] Optionally, the verification result can indicate that the initial information verification of the MCP Server has passed or failed. If the verification result indicates that the initial information verification of the MCP Server has failed, the specific error reason can be returned (such as "service identifier already exists" or "service type invalid").

[0122] For example, the initial information of the MCP Server can be deemed valid if it meets the following conditions, and a verification result indicating that the initial information of the MCP Server has passed verification can be generated: the communication protocol type and the running port number can be correctly matched, and the running port number is not occupied; the selected network access method conforms to the preset security policy, such as not violating firewall rules or using prohibited plaintext transmission methods; the server identifier is unique in the current configuration platform, that is, there is no identifier that is duplicated with other configured MCP Servers. Furthermore, if the initial information of the MCP Server does not meet any of the above conditions, it is determined that the initial information of the MCP Server does not meet the validity conditions, and a verification result indicating that the initial information of the MCP Server has failed verification can be generated.

[0123] S304: If the verification result indicates that the initial information of the MCP Server has passed the verification, generate the MCP Server configuration information in the MCP Server management platform based on the initial information of the MCP Server.

[0124] In one embodiment, the MCP Server management platform can structurally store and map the initial MCP Server information according to internally predefined configuration templates, forming a standardized set of configuration information to obtain the MCP Server configuration information, which is then stored in the MCP Server management platform. This MCP Server configuration information not only distinguishes different service instances but also serves as the foundational metadata for subsequent resource configuration, deployment parameter generation, and service node construction, thereby ensuring consistency and manageability of the MCP Server in the runtime environment.

[0125] In this embodiment, by obtaining initial MCP Server information from the MCP Server configuration page and performing legality verification and standardized generation within the management platform, each MCP Server possesses a clear and unique identifier, compliant access policies, and correct communication configurations during the creation phase. This effectively avoids service anomalies caused by configuration conflicts, security vulnerabilities, or improper parameters. Furthermore, the standardized MCP Server configuration information generated based on the initial information not only achieves standardized management of different service instances but also provides unified metadata support for subsequent resource configuration, deployment parameter generation, and service node construction, improving the system's scalability, stability, and operational efficiency.

[0126] S305: In response to a service resource registration instruction for MCP Server configuration information, a service resource registration context is generated. The service resource registration context is used to limit the interaction constraint parameters between the service resource and the MCP Server configuration information.

[0127] The service resource registration instruction can be an operation triggered by the user (such as clicking the register resource button), which means binding a specific service resource to a pre-configured MCP Server.

[0128] Optionally, the service resource registration context can be a "logical container" within the MCP Server management platform. This container defines the boundaries and constraints that must be followed during registration, such as allowed input / output data types, interface call methods, and authentication rules. Interaction constraint parameters can refer to the restrictions that service resources must comply with when interacting with the MCP Server, such as whether input / output data formats are compatible, call frequency limits, and security authentication methods.

[0129] For example, when a user issues a service resource registration command based on the target MCP Server configuration information in the MCP Server management platform, the platform can invoke its internal context environment generation module to construct a logical container that constrains service resource registration behavior based on the MCP Server configuration information. Specifically, it can first generate a context identifier uniquely corresponding to the service instance based on the service type and permission configuration in the MCP Server configuration information; then, according to a predefined configuration template, it binds the context identifier with the boundary conditions of input mapping rules, output mapping rules, and interface description information to form a service resource registration context environment. Furthermore, during the generation process, the MCP Server management platform can automatically load default constraint parameters corresponding to the target runtime environment, such as data format constraints (e.g., JSON), interface protocol constraints, authentication constraints, and call frequency limits, thereby ensuring that the subsequently bound service resources can meet compatibility, security, and stability requirements during operation. Thus, the automatic generation and configuration of the service resource registration context environment is achieved, enabling service resources to interact with the MCP Server within compliance boundaries.

[0130] S306: In the service resource registration context, load the input mapping rule editing component, output mapping rule editing component, and interface description information entry component corresponding to the service resource.

[0131] In one embodiment, after generating the service resource registration context environment, a resource configuration page can also be displayed. The resource configuration page may include a new resource control. If the user triggers the new resource control, the step S306 is executed in the service resource registration context environment to load the input mapping rule editing component, output mapping rule editing component and interface description information entry component corresponding to the service resource.

[0132] Figure 6 A schematic diagram of a resource configuration page provided for an exemplary embodiment of this application, such as... Figure 6The resource configuration page 600 may include a third navigation bar 601, which is used to switch between different functional pages, such as the "Server Information" page (i.e., the MCP Server configuration page) and the "Tool Configuration" page (i.e., the resource configuration page). Taking tool resources as an example, the resource configuration page 600 may include multiple tool status partitions, such as the online tool display area 602, the offline tool display area 603, and the offline tool display area 604. The online tool display area 602 displays tool resources that have been successfully registered and published, where users can perform version management, configuration updates, or offline operations. The offline tool display area 603 displays tool resources that have completed initial configuration but have not yet been published, where users can debug, supplement information, or publish. The offline tool display area 604 displays tool resources that have been taken offline, where users can republish or permanently delete offline tools as needed. Additionally, the resource configuration page 600 may include a new resource control 605. This control, upon user triggering, retrieves the basic resource information specified by the user and executes step S306. Specifically, it loads the input mapping rule editing component, output mapping rule editing component, and interface description information entry component corresponding to the service resource within the service resource registration context, thereby completing the registration and configuration process for the new resource. This allows users to manage and maintain resources in different states within a single page, supporting the addition, configuration, and publication of service resources, as well as their decommissioning and version evolution. This improves the operational efficiency and management controllability of service resources within the MCP Server.

[0133] Optionally, the input mapping rule editing component can be a configuration tool for defining the correspondence between external call requests and service resource input parameters. This component can be presented as a visual form or rule editing interface, where users can specify how fields in the caller's request message are mapped to the input parameters required by the service resource. Through this component, users can flexibly edit field correspondences, data type conversion rules, default value filling methods, etc., ensuring that data from external call requests is correctly transmitted to the service resource. The output mapping rule editing component can be a configuration tool for defining the correspondence between service resource output results and caller response data. This output mapping rule editing component allows users to specify how the raw results returned after service resource execution are mapped to a standardized response structure. This output mapping rule editing component also supports filtering, formatting, or trimming output data to ensure that the results received by the caller conform to the interface contract and usage habits. The interface description information entry component can be a tool for inputting and managing descriptive information about service resource interfaces. This interface description information entry component is mainly used to supplement unstructured but crucial interface metadata for the caller, such as interface function descriptions, the meaning of input and output parameters, value ranges, calling methods, authentication methods, error code descriptions, etc. The explanatory information entered through this component can automatically generate interface documentation or configuration files, making it easier for callers to understand and correctly use service resources. Simultaneously, this explanatory information can also be used for automated validation (such as detecting missing caller parameters or type mismatches) and debugging assistance.

[0134] In one embodiment, the aforementioned basic resource information may include resource identifier, resource name, resource description information, resource permission information, queries per second (QPS) rate limiting information, and remote procedure call (RPC) information. The QPS rate limiting information can be used to configure the maximum request rate of the tool, such as 100 QPS. The RPC information can be used to define the remote call method of the tool, and may include the following categories: High-speed Service Framework (HSF) type RPC, Hypertext Transfer Protocol (HTTP) type RPC, TPP type RPC, and Solution type RPC, etc.

[0135] In one embodiment, within the service resource registration context, loading the input mapping rule editing component, output mapping rule editing component, and interface description information entry component corresponding to the service resource includes: obtaining the resource type of the service resource; determining the target configuration template identifier based on the resource type; obtaining the resource configuration interface template matching the service resource according to the target configuration template identifier; rendering the resource configuration interface template file into an interactive page; and displaying the input mapping rule editing component, output mapping rule editing component, and interface description information entry component corresponding to the service resource through the interactive page.

[0136] For example, firstly, the resource type of the service resource to be registered can be obtained; then, a target configuration template identifier is determined based on the resource type, which is used to uniquely indicate the configuration template that matches the resource type; next, the corresponding resource configuration interface template is obtained according to the target configuration template identifier. The resource configuration interface template is a predefined interface description file used to define the page layout, parameter items, and component calling logic required in the service resource configuration process; finally, the resource configuration interface template is rendered into an interactive page, and an input mapping rule editing component, an output mapping rule editing component, and an interface description information entry component are displayed on the page. Users can complete the interactive configuration of service resource input rules, output rules, and interface descriptions through the interactive page, thereby realizing the standardized registration and management of service resources.

[0137] In this embodiment, by automatically matching and calling the corresponding configuration template according to the resource type of different service resources when loading the service resource configuration interface, a unified interactive page is generated. This effectively avoids the tedious operation of users manually selecting or repeatedly configuring, and improves the automation and standardization of service resource registration. Furthermore, through the templated interface generation mechanism, the display and configuration process of input mapping rules, output mapping rules, and interface description information are consistent and compatible, thereby reducing the configuration error rate and improving the reliability and maintainability of the interaction between service resources and the MCP Server.

[0138] S307: Obtain user-defined input mapping rules through the input mapping rule editing component, obtain user-defined output mapping rules through the output mapping rule editing component, and obtain interface description information through the interface description information entry component.

[0139] In other words, a visual or configurable editing component is first provided in the service resource registration context, so that users can complete the configuration of service resource input rules, output rules and interface descriptions through the input mapping rule editing component, the output mapping rule editing component and the interface description information entry component, respectively.

[0140] S308: Integrate and process the input mapping rules, output mapping rules, and interface description information to obtain the resource configuration information of the service resources associated with the MCPServer configuration information.

[0141] Optionally, the input mapping rules are first converted into a standardized parameter mapping table to clarify the correspondence between external call parameters and the internal execution parameters of the MCP Server. Then, the output mapping rules are converted into a result mapping table to uniformly encapsulate and format the raw output results of service resources, ensuring that the input and output mapping rules conform to the platform's data return specifications. Finally, the interface description information is structured according to a predefined document template to obtain an interface description document including elements such as interface name, calling protocol, request parameter description, return parameter description, and exception code definition. After completing the above integration process, resource configuration information associated with the MCP Server configuration information can be generated. This resource configuration information may include basic tool information, technical constraints on input and output, and semantic descriptions of the interface descriptions, serving as the basis for subsequent deployment parameter generation, runtime environment construction, and service call routing configuration.

[0142] In one embodiment, integrating input mapping rules, output mapping rules, and interface description information may include: converting model input parameters into standardized inputs required by the external service interface according to the field mapping rules defined in the input mapping rules; and extracting and transforming complex JSON data returned by the external interface according to the output mapping rules, retaining only the necessary key fields to form a simplified output result. For example, for JSON data containing a large amount of shop information returned by the external interface, the "shop name" and "shop address" fields can be extracted using a script to generate a concise and clear output result, which is then associated and stored with the MCP Server as configuration content for service resources.

[0143] In this embodiment, by introducing a service resource registration context environment during the service resource registration process, and loading an input mapping rule editing component, an output mapping rule editing component, and an interface description information entry component within this environment, precise binding and standardized configuration between service resources and MCP Server configuration information can be achieved. This solution not only ensures accurate mapping between external call parameters and internal execution parameters, and consistency between the original output of the service resource and the caller's response, but also improves the compatibility, security, and stability of service calls through structured entry of interface description information, thereby enhancing the operational efficiency and controllability of the entire MCP Server operating environment.

[0144] S309: Generate deployment parameters for running the MCP Server and service resources based on the MCP Server configuration information and resource configuration information.

[0145] For details, please refer to S203 above; it will not be repeated here.

[0146] S310: Send the deployment parameters to the target server so that the target server can deploy the corresponding runtime environment of MCPServer based on the deployment parameters.

[0147] For details, please refer to S204 above; it will not be repeated here.

[0148] S311: In response to a debug command for a service resource, perform debug operations based on the runtime environment and obtain debug results.

[0149] For details, please refer to S205 above; it will not be repeated here.

[0150] S312: If the debugging results indicate that the service resources meet the preset operating conditions, a service node construction request is sent to the target server so that the target server can construct an MCPServer node in a state of waiting to be called based on the service node construction request, and generate node metadata of the MCP Server node. The MCP Server node is used to carry service resources and respond to the call request of the target model to execute the corresponding resource service task.

[0151] For details, please refer to S206 above; it will not be repeated here.

[0152] S313: Receive node metadata sent by the target server and register the node metadata with the MCP Server management platform. The node metadata is used to identify the MCP Server node and provide call routes for the MCP Server node.

[0153] For details, please refer to S207 above; it will not be repeated here.

[0154] In this embodiment, by automating the entire process of service node configuration, verification, registration to deployment, the legitimacy and uniqueness of service information can be improved, the standardized binding and flexible expansion of service resources can be supported, and the security and compatibility of interface calls can be improved, thereby enhancing the efficiency and reliability of service deployment.

[0155] In one embodiment, such as Figure 7 As shown, another method for deploying service nodes is provided, which can be applied to... Figure 1 The following steps are illustrated using the platform client device 10 as an example:

[0156] S701: Displays the MCP Server configuration page through the MCP Server management platform running on the platform client device.

[0157] For details, please refer to S201 above; it will not be repeated here.

[0158] S702: Obtain the user-defined MCP Server configuration information and the resource configuration information of the service resources associated with the MCP Server configuration information through the MCP Server configuration page. The resource configuration information includes input mapping rules, output mapping rules and interface description information.

[0159] For details, please refer to S202 above; it will not be repeated here.

[0160] S703: Generates deployment parameters for running the MCP Server and service resources based on MCP Server configuration information and resource configuration information.

[0161] For details, please refer to S203 above; it will not be repeated here.

[0162] S704: Send the deployment parameters to the target server so that the target server can deploy the corresponding runtime environment of MCPServer based on the deployment parameters.

[0163] For details, please refer to S204 above; it will not be repeated here.

[0164] S705: In response to a debug command for a service resource, display the debug page.

[0165] The debug page is an interactive interface provided by the MCP Server management platform after service resource configuration. It verifies the correctness of the configuration and the availability of functionality. On this page, users can intuitively see the input / output rules of the service resources, interface descriptions, and real-time debug results. The debug page allows users to input test parameters, execute calls, view return results, and troubleshoot anomalies, ensuring that the service resource configuration meets expectations before release.

[0166] Optionally, the sample input data can be test data automatically generated based on user-configured input mapping rules, used to simulate external call requests in the debugging page. The content of the sample input data follows the input parameter format and data type requirements of the service resource, such as field names, data types, and default values. By displaying sample input data, users can quickly verify whether the input parameter mapping is correct without manually constructing complex test requests, thereby improving debugging efficiency and accuracy.

[0167] Figure 8A schematic diagram of a debugging page provided for an exemplary embodiment of this application, such as... Figure 8 The debugging page 800 may include a sample page function description area 801, a sample generation control 802, a data fill control 803, a sample data display area 804, an input data area 805, a debugging execution control 806, a debugging result display area 807, a result copy control 808, and a call chain view control 809. The sample page function description area 801 displays the functions and usage instructions of the debugging page 800, prompting users to perform tool debugging operations on this page and guiding them to understand how to input and test data. The sample generation control 802 automatically generates sample input data that meets the required format according to input mapping rules, allowing users to quickly obtain standardized input references. The data fill control 803 directly fills the generated sample input data into the input data area, reducing manual input operations and improving debugging efficiency. The sample data display area 804 displays sample input data generated by the system, allowing users to clearly see the format, parameter names, and sample values ​​of the input data. The input data area 805 allows users to input or modify data parameters required for debugging; this area supports data formats such as JSON. The debug control 806 triggers a debug call request after the user confirms the input data. The input data is then converted into a request format matching the MCP Server via mapping rules and sent to the target server to obtain debug results. The debug result display area 807 displays the debug output data returned by the target server. Users can visually view the results parsed by the output mapping rules to verify whether the service resources are operating as expected. The copy result control 808 allows users to copy debug results with a single click, facilitating subsequent archiving, comparison, or reuse in other systems, improving debugging efficiency and operability. The view call chain control 809 displays the call chain information, such as the request sending path, parameter mapping process, and response receiving path, helping users troubleshoot problems and verify the integrity and correctness of requests and responses.

[0168] S706: Generate sample input data based on input mapping rules and display the sample input data on the debug page.

[0169] Specifically, standardized request parameters that meet the target interface call requirements and are required by the target service resource can be extracted based on the input mapping rules. These parameters include parameter name, data type, whether they are required, default value, and value range. Then, based on the attributes of the parameter information, corresponding example values ​​are generated according to a preset data generation strategy. For example, for string parameters, random characters or preset string examples can be generated; for numeric parameters, integers or floating-point numbers within a range can be generated; and for enumerated parameters, an example value from an enumeration set can be generated. If a default value exists in the input mapping rules, it can be used as the example value. Finally, all parameter information and example values ​​are combined to construct a data structure that meets the input format requirements and output in the example data display area of ​​the debugging page, allowing users to intuitively view and quickly obtain compliant test input data.

[0170] S707: After detecting the user's confirmation instruction for the sample input data, the sample input data is converted into a request format that matches the MCP Server according to the input mapping rules, and a debug call request is sent to the target server so that the target server can generate debug output data based on the debug call request in the runtime environment.

[0171] In one embodiment, upon detecting a user's confirmation instruction for sample input data, the sample input data is first mapped and normalized according to preset input mapping rules. This includes mapping the calling side field names to the target field names required by the service resources, performing data type casting and formatting on the input values, filling missing but required parameters with default values ​​or renaming the fields, and generating derived fields based on expressions or scripts in the rules, while simultaneously verifying the data format, value range, etc. Subsequently, based on the protocol requirements of the target service, the mapped data is assembled into a request format matching the MCP Server. For example, in an HTTP scenario, a standard message containing method type, message header, and message body is generated; in an RPC scenario, an interface method call sequence and parameter signature are generated; and in a TPP scenario, routing information and authentication tickets are encapsulated. After message assembly, the system also injects authentication information, routing identifiers, and flow control parameters into the request context and generates a link tracing identifier for debugging. Finally, the request is sent to the target server's runtime environment through the corresponding transmission channel or software development kit.

[0172] S708: Obtain the debug output data returned by the target server, and parse and process the debug output data according to the output mapping rules to generate debug results.

[0173] In one embodiment, after the target server returns debug output data, the platform client device first receives the debug output data and processes it according to preset output mapping rules. Specifically, this includes: mapping the original output fields to standardized field names, performing necessary data type conversions, filtering out the content to be displayed, and filtering out irrelevant or sensitive information. Subsequently, the processed data is encapsulated into a unified format to generate the final debug result, which is then displayed on the debug page, allowing users to intuitively verify whether the output of the service resources meets expectations.

[0174] S709: When the debugging results indicate that the service resources meet the preset operating conditions, a service node construction request is sent to the target server so that the target server can construct an MCPServer node in a state of waiting to be called based on the service node construction request, and generate node metadata of the MCP Server node. The MCP Server node is used to carry service resources and respond to the call request of the target model to execute the corresponding resource service task.

[0175] For details, please refer to S206 above; it will not be repeated here.

[0176] S710: Receives node metadata sent by the target server and registers the node metadata with the MCP Server management platform. The node metadata is used to identify the MCP Server node and provide call routes for the MCP Server node.

[0177] For details, please refer to S207 above; it will not be repeated here.

[0178] In another embodiment, when the debugging results indicate that the service resources do not meet the preset operating conditions, the method further includes: determining the abnormal operation configuration item corresponding to the MCP Server based on the debugging results; displaying the abnormal operation configuration item through the abnormal configuration modification page; obtaining the first modification information determined for the abnormal operation configuration item; updating the deployment parameters based on the first modification information to generate updated deployment parameters; and returning to the execution step of sending the deployment parameters to the target server based on the updated deployment parameters, so that the target server deploys the operating environment corresponding to the MCP Server based on the deployment parameters.

[0179] Among them, runtime configuration anomalies can be configuration problems that do not conform to the preset running conditions, discovered based on the debugging results during service resource debugging. These runtime configuration anomalies may include, but are not limited to: inconsistent input / output data types, missing or incorrect interface authentication methods, unreasonable QPS rate limiting threshold settings, incompatible RPC protocols, etc., and are used to identify specific configuration defects that cause the service resource to fail to run as expected.

[0180] Optionally, the abnormal configuration modification page can be an interactive interface provided by the MCP Server management platform. When a runtime configuration anomaly is detected, the page will visually display the anomaly's content and provide corresponding modification entry points. Users can view the cause of the anomaly on this page and correct the configuration parameters to ensure the runtime environment meets preset conditions. The first modification information is the repair content or adjustment plan determined by the user on the abnormal configuration modification page for the runtime configuration anomaly. This first modification information may include modified values ​​of configuration parameters, replaced authentication methods, adjusted rate limiting thresholds, corrected input / output mapping rules, etc., and updated deployment parameters can be generated based on this first modification information.

[0181] In one embodiment, updating the deployment parameters based on the first modification information to generate updated deployment parameters can be achieved by: updating the field mapping configuration when the modification information involves input mapping rules; updating the result parsing rules when it involves output mapping rules; updating the interface parameters or authentication methods when it involves interface description information; and updating parameters such as call frequency and timeout policy when it involves performance or operating conditions. This ensures that the updated deployment parameters accurately reflect the user's modifications.

[0182] In this embodiment, by automatically identifying abnormal configuration items after debugging failure and visually displaying the problem points on the abnormal configuration modification page, users can quickly locate and correct errors. Furthermore, by automatically generating updated deployment parameters based on the user's initial modification information, a closed-loop repair of configuration problems is achieved. This process not only reduces the cost of manual troubleshooting and repeated deployments for users but also enables service resources to recover to a state that meets preset operating conditions in a shorter time, thereby significantly improving the efficiency and reliability of MCP Server deployment and debugging.

[0183] S711: In response to a modification request for a service resource, display the service resource modification page.

[0184] Among them, a modification request can refer to an instruction / event used to trigger changes to the configuration information of existing service resources. It can be initiated by the user or the system and is used to access the service resource modification page.

[0185] Optionally, the Service Resource Modification Page is an interactive interface provided by the MCP Server management platform for users to modify parameters, rules, or attributes after the service resource has been initially configured and deployed. This page can be presented as a visual form or configuration item list, intuitively displaying the current service resource's configuration information. Users can directly modify input / output mapping rules, interface descriptions, access control, rate limiting policies, and other content on this page. Its purpose is to provide users with a centralized configuration entry point, avoiding manual editing of underlying configuration files, reducing error rates, and improving the efficiency of configuration updates.

[0186] S712: Obtain the second modification information through the service resource modification page.

[0187] Optionally, the second modification information refers to the changes that the user inputs or confirms on the service resource page. The second modification information includes, but is not limited to: adjustments to input / output data mapping rules, such as changing field names or data types; updates to interface descriptions, such as adding new parameter descriptions or modifying the calling method; updates to permission-related parameters, such as changing the authentication method or modifying the permission code; and adjustments to runtime parameters, such as call frequency limits and timeout thresholds.

[0188] S713: Update the deployment parameters based on the second modification information to generate updated deployment parameters.

[0189] In other words, the second modification information is a collection of changes made by the user to the current configuration of the service resources. The second modification information will be collected and used to update the deployment parameters, thereby driving the target server to generate a new operating environment.

[0190] S714: Based on the updated deployment parameters, return the execution of the step of sending the deployment parameters to the target server so that the target server can deploy the runtime environment corresponding to the MCP Server based on the deployment parameters.

[0191] In this embodiment, by introducing service resource modification requests and service resource modification pages, users can conveniently adjust service resource configurations in a centralized and visual interactive interface without directly manipulating the underlying configuration files, thus reducing the risk of human configuration errors. By collecting second modification information and generating updated deployment parameters accordingly, dynamic updates and rapid iterations of the operating environment can be achieved, thereby improving configuration maintenance efficiency and system flexibility.

[0192] Furthermore, in response to debugging instructions for service resources, debugging operations are performed based on the new operating environment to obtain debugging results. If the debugging results indicate that the service resources meet preset operating conditions, a service node construction request is sent to the target server. This allows the target server to construct an MCPServer node in a pending-call state based on the service node construction request and generate node metadata for the MCP Server node. The MCP Server node is used to host service resources and respond to call requests from the target model to execute corresponding resource service tasks. Additionally, the system receives the node metadata sent by the target server and registers the node metadata with the MCP Server management platform. The node metadata identifies the MCP Server node and provides call routes for the MCP Server node. This completes a closed-loop process from service resource configuration adjustment and dynamic updates of the operating environment to debugging verification and service node construction.

[0193] In this embodiment, when a modification request is received, the system enters the service resource modification page to collect second modification information and incrementally updates the deployment parameters accordingly (generating a new version and retaining history to support rollback / comparison). Subsequently, the updated deployment parameters are distributed to the target server, and hot update / canary deployment of the runtime environment is completed. The system automatically triggers regression debugging and generates debugging results: if the preset running conditions are not met, abnormal running configuration items are automatically extracted based on the results and backfilled to the modification page, driving the next round of modification, update, and debugging until the requirements are met; if the preset running conditions are met, an MCP Server node in a pending call state is constructed, node metadata is generated and registered to the management platform, and the call route takes effect immediately. This cyclical mechanism transforms configuration changes, environment updates, effect verification, problem localization, further changes, and solidification into a repeatable engineering process, significantly shortening the online iteration cycle, reducing human configuration errors, and improving the stability and maintainability of service resource deployment.

[0194] Furthermore, in one embodiment, after the platform client device receives the node metadata sent by the target server and registers the node metadata with the MCP Server management platform, the terminal device (running the target model) can perform invocation operations based on the registered node metadata.

[0195] Specifically, the node metadata contains unique identification information for the MCP Server node and call routing information. During execution, when the target model in the terminal device detects a need to call external service resources, it determines the call route based on the node metadata returned by the MCP Server management platform. The terminal user can select the target MCP Server to be enabled (such as a map MCP Server or a general knowledge details MCP Server) during the service agent configuration phase of the terminal device, and further select specific service resources under the target MCP Server (such as a knowledge base document list tool or a tool to obtain basic store information). After configuration, when the target model running on the terminal device generates a call request, it can match the registered node metadata based on the input context, confirm the corresponding MCP Server node, and, through the call routing information in the node metadata, direct the call request to the target MCP Server runtime environment. Upon arrival of the route, the MCP Server triggers the corresponding service resource execution logic (such as querying the knowledge base, calling the map interface, or obtaining store information). Subsequently, the service resource execution result is returned to the terminal device through the MCP Server, and the terminal device injects the result into the inference context of the target model to generate the final output response.

[0196] It is understandable that the aforementioned end users can be individual users, such as ordinary users using a smart application (map query, knowledge Q&A); they can also be enterprise operation and maintenance personnel or administrators, such as maintenance personnel who configure the MCPServer operating environment and call tools within the enterprise; and they can also be system callers, such as target models running on terminal devices, such as customer service robots, recommendation systems, search engines, etc.

[0197] In this embodiment, the terminal device does not need to directly perceive the physical deployment location or underlying configuration of service resources such as tools. It only needs to rely on the registered node metadata to achieve dynamic and scalable tool invocation. This not only improves the flexibility and maintainability of invocation, but also enables the model to quickly adapt to different service resources according to the configuration, effectively improving the efficiency of model inference.

[0198] It should be understood that although the steps in the flowcharts of the embodiments described above are shown sequentially according to the arrows, these steps are not necessarily executed in the order indicated by the arrows. Unless explicitly stated herein, there is no strict order restriction on the execution of these steps, and they can be executed in other orders. Moreover, at least some steps in the flowcharts of the embodiments described above may include multiple steps or multiple stages. These steps or stages are not necessarily completed at the same time, but can be executed at different times. The execution order of these steps or stages is not necessarily sequential, but can be performed alternately or in turn with other steps or at least some of the steps or stages of other steps.

[0199] Based on the above-mentioned service node deployment method, such as Figure 9 As shown, this application embodiment also provides a first service node deployment device 900 for implementing the above-described service node deployment method applied to platform client devices. The first service node deployment device 900 includes:

[0200] The first display module 901 is used to display the MCP Server configuration page through the MCP Server management platform running on the platform client device;

[0201] The first acquisition module 902 is used to acquire the MCP Server configuration information determined by the user and the resource configuration information of the service resources associated with the MCP Server configuration information through the MCP Server configuration page. The resource configuration information includes input mapping rules, output mapping rules and interface description information.

[0202] The generation module 903 is used to generate deployment parameters for running the MCPServer and service resources based on the MCP Server configuration information and resource configuration information.

[0203] The first sending module 904 is used to send deployment parameters to the target server so that the target server can deploy the corresponding runtime environment of the MCP Server based on the deployment parameters;

[0204] The debugging module 905 is used to respond to debugging commands for service resources, perform debugging operations based on the runtime environment, and obtain debugging results.

[0205] The second sending module 906 is used to send a service node construction request to the target server when the debugging results indicate that the service resources meet the preset operating conditions, so that the target server can construct an MCP Server node in a state of waiting to be called based on the service node construction request, and generate node metadata of the MCP Server node. The MCP Server node is used to carry service resources and respond to the calling request of the target model to execute the corresponding resource service task.

[0206] The registration module 907 is used to receive node metadata sent by the target server and register the node metadata with the MCP Server management platform. The node metadata is used to identify the MCP Server node and provide call routes for the MCP Server node.

[0207] In one embodiment, the first acquisition module 902 is specifically configured to: acquire MCP Server initial information through the MCP Server configuration page; perform a validity check on the MCP Server initial information and obtain a verification result; if the verification result indicates that the MCP Server initial information has passed the verification, generate MCP Server configuration information in the MCP Server management platform based on the MCP Server initial information; and in response to a service resource registration instruction for the MCP Server configuration information, acquire resource configuration information of the service resources associated with the MCP Server configuration information.

[0208] In one embodiment, the first acquisition module 902 is specifically configured to: generate a service resource registration context environment in response to a service resource registration instruction for MCP Server configuration information, wherein the service resource registration context environment is used to limit the interaction constraint parameters between the service resource and the MCP Server configuration information; in the service resource registration context environment, load the input mapping rule editing component, the output mapping rule editing component, and the interface description information entry component corresponding to the service resource; obtain the user-determined input mapping rule through the input mapping rule editing component, obtain the user-determined output mapping rule through the output mapping rule editing component, and obtain the interface description information through the interface description information entry component; integrate and process the input mapping rule, the output mapping rule, and the interface description information to obtain the resource configuration information of the service resource associated with the MCP Server configuration information.

[0209] In one embodiment, the first acquisition module 902 is specifically used for: acquiring the resource type of the service resource; determining the target configuration template identifier based on the resource type; acquiring the resource configuration interface template that matches the service resource according to the target configuration template identifier; rendering the resource configuration interface template file into an interactive page, and displaying the input mapping rule editing component, output mapping rule editing component, and interface description information entry component corresponding to the service resource through the interactive page.

[0210] In one embodiment, the generation module 903 is specifically used for: performing structured parsing processing on the MCP Server configuration information to obtain MCP Server running parameter information; performing rule-based parsing processing on the resource configuration information to generate interface configuration information compatible with the MCP Server's operating environment; and performing association mapping processing on the MCP Server running parameter information and the interface configuration information to generate deployment parameters for running the MCP Server and service resources.

[0211] In one embodiment, the debugging module 905 is specifically configured to: display a debugging page in response to a debugging instruction for a service resource; generate sample input data based on input mapping rules and display the sample input data on the debugging page; after detecting a user's confirmation instruction for the sample input data, convert the sample input data into a request format matching the MCPServer using input mapping rules, and initiate a debugging call request to the target server so that the target server generates debugging output data based on the debugging call request in the runtime environment; obtain the debugging output data returned by the target server, and parse and process the debugging output data according to the output mapping rules to generate debugging results.

[0212] In one embodiment, the first service node deployment device 900 further includes: a determination module, configured to determine the runtime configuration anomaly item corresponding to the MCP Server based on the debugging results when the debugging results indicate that the service resources do not meet the preset operating conditions; a second display module, configured to display the runtime configuration anomaly item through an anomaly configuration modification page; a second acquisition module, configured to acquire first modification information determined for the runtime configuration anomaly item; a first update module, configured to update the deployment parameters based on the first modification information to generate updated deployment parameters; and a first loop module, configured to return to the step of sending the deployment parameters to the target server based on the updated deployment parameters so that the target server deploys the runtime environment corresponding to the MCP Server based on the deployment parameters.

[0213] In one embodiment, the first service node deployment device 900 further includes: a third display module, configured to display a service resource modification page in response to a modification request for the service resource; a third acquisition module, configured to acquire second modification information through the service resource modification page; a second update module, configured to update the deployment parameters based on the second modification information to generate updated deployment parameters; and a second loop module, configured to return to the step of sending the deployment parameters to the target server based on the updated deployment parameters, so that the target server deploys the runtime environment corresponding to the MCP Server based on the deployment parameters.

[0214] Based on the above-mentioned service node deployment method, such as Figure 10 As shown in the embodiments of this application, a second service node deployment apparatus 1000 is also provided for implementing the above-described service node deployment method applied to a target server. The second service node deployment apparatus 1000 includes:

[0215] The receiving module 1001 is used to receive deployment parameters sent by the platform client device. The deployment parameters are deployment parameters generated by the platform client device based on the MCP Server configuration information and resource configuration information for running the MCP Server and the service resources associated with the MCP Server configuration information. The MCP Server configuration information and resource configuration information are information obtained by the platform client device through the MCP Server configuration page. The MCP Server configuration page is a page displayed by the platform client device through the MCP Server management platform running on the platform client device.

[0216] Deployment module 1002 is used to deploy the runtime environment corresponding to the MCP Server based on deployment parameters;

[0217] The construction module 1003 is used to receive the service node construction request sent by the platform client device, and construct the MCP Server node in the state of waiting to be called based on the service node construction request, and generate the node metadata of the MCP Server node. The MCP Server node is used to carry service resources and respond to the call request of the target model to execute the corresponding resource service task. The service node construction request is a request sent by the platform client device when the debugging result indicates that the service resource meets the preset running conditions. The debugging result is the result obtained by the platform client device in response to the debugging instructions for the service resource based on the running environment for debugging operations.

[0218] The third sending module 1004 is used to send node metadata to the platform client device, so that the platform client device can register the node metadata with the MCP Server management platform running on the platform client device. The node metadata is used to identify the MCP Server node and provide call routes for the MCP Server node.

[0219] Each module in the first service node deployment device 900 and the second service node deployment device 1000 can be implemented entirely or partially through software, hardware, or a combination thereof. These modules can be embedded in or independent of the processor in a computer device in hardware form, or stored in the memory of a computer device in software form, so that the processor can call and execute the operations corresponding to each module.

[0220] This application also provides an electronic device, which can be a server, and its internal structure diagram can be as follows: Figure 11 As shown. Please see below. Figure 11 This electronic device includes a processor, memory, input / output (I / O) interfaces, and a communication interface. The processor, memory, and I / O interfaces are connected via a system bus, and the communication interface is also connected to the system bus via the I / O interfaces. The processor provides computing and control capabilities. The memory includes non-volatile storage media and internal memory. The non-volatile storage media stores the operating system, computer programs, and a database. The internal memory provides the environment for the operating system and computer programs stored in the non-volatile storage media. The database stores MCP Server configuration information and resource configuration information of service resources associated with the MCP Server configuration information. The I / O interfaces are used for exchanging information between the processor and external devices. The communication interface is used for communicating with external terminals via a network connection. The processor executes computer programs to implement a service node deployment method.

[0221] It is worth noting that this electronic device can also be a terminal, and its internal structure diagram can be as follows: Figure 12 As shown. Please see below. Figure 12The electronic device includes a processor, memory, input / output interface, communication interface, display unit, and input device. The processor, memory, and input / output interface are connected via a system bus, and the communication interface, display unit, and input device are also connected to the system bus via the input / output interface. The processor provides computing and control capabilities. The memory includes non-volatile storage media and internal memory. The non-volatile storage media stores the operating system and computer programs. The internal memory provides an environment for the operation of the operating system and computer programs stored in the non-volatile storage media. The input / output interface is used for exchanging information between the processor and external devices. The communication interface is used for wired or wireless communication with external terminals; wireless communication can be achieved through Wi-Fi, mobile cellular networks, NFC (Near Field Communication), or other technologies. When the computer program is executed by the processor, it implements a service node deployment method. The display unit is used to form a visually visible image and can be a display screen, projection device, or virtual reality imaging device. The display screen can be an LCD screen or an e-ink screen. The input device of the electronic device can be a touch layer covering the display screen, or buttons, trackballs, or touchpads set on the casing of the electronic device, or external keyboards, touchpads, or mice, etc.

[0222] This application also provides a computer storage medium storing instructions that, when run on a computer or processor, cause the computer or processor to perform one or more steps in the above embodiments. If the constituent modules of the above-described electronic device are implemented as software functional units and sold or used as independent products, they can be stored in the above-described computer-readable storage medium.

[0223] In the above embodiments, implementation can be achieved entirely or partially through software, hardware, firmware, or any combination thereof. When implemented using software, it can be implemented entirely or partially as a computer program product. The computer program product includes one or more computer instructions. When the computer program instructions are loaded and executed on a computer, all or part of the processes or functions described in the embodiments of this application are generated. The computer can be a general-purpose computer, a special-purpose computer, a computer network, or other programmable device. The computer instructions can be stored in a computer storage medium or transmitted through the computer storage medium. The computer instructions can be transmitted from one website, computer, server, or data center to another website, computer, server, or data center via wired (e.g., coaxial cable, fiber optic, Digital Subscriber Line (DSL)) or wireless (e.g., infrared, wireless, microwave, etc.) means. The computer storage medium can be any available medium that a computer can access or a data storage device such as a server or data center that integrates one or more available media. The available media may be magnetic media (e.g., floppy disks, hard disks, magnetic tapes), optical media (e.g., digital versatile discs (DVDs)), or semiconductor media (e.g., solid-state drives (SSDs)).

[0224] Those skilled in the art will understand that all or part of the processes in the methods of the above embodiments can be implemented by a computer program instructing related hardware. This program can be stored in a computer-readable storage medium, and when executed, it can include the processes of the embodiments of the methods described above. The aforementioned storage medium includes various media capable of storing program code, such as ROM, RAM, magnetic disks, or optical disks. Unless otherwise specified, the technical features of this embodiment and its implementation can be combined arbitrarily.

[0225] The embodiments described above are merely preferred embodiments of this application and are not intended to limit the scope of this application. Any modifications and improvements made to the technical solutions of this application by those skilled in the art without departing from the spirit of this application shall fall within the protection scope defined by the claims.

[0226] It should be noted that the technical solution of this application can be applied to the transaction and delivery services of instant e-commerce platforms, such as Taobao Flash Sale, Taoxianda, Ele.me takeaway, and retail. All information and data involved in the embodiments of this application are authorized by the user or fully authorized by all parties, and the collection, use, and processing of related data must comply with the relevant laws, regulations, and standards of the relevant countries and regions. For example, the "MCP Server configuration information" and "resource configuration information" mentioned in this specification were obtained under fully authorized conditions.

[0227] The foregoing has described specific embodiments of this application. Other embodiments are within the scope of the appended claims. In some cases, the actions or steps recited in the claims may be performed in a different order than that shown in the embodiments and may still achieve the desired results. Furthermore, the processes depicted in the drawings do not necessarily require the specific or sequential order shown to achieve the desired results. In some embodiments, multitasking and parallel processing are also possible or may be advantageous.

Claims

1. A service node deployment method, characterized in that, Applied to platform client devices, the method includes: The MCP Server configuration page is displayed through the MCP Server management platform running on the platform client devices; The user-defined MCP Server configuration information and the resource configuration information of the service resources associated with the MCP Server configuration information are obtained through the MCP Server configuration page. The resource configuration information includes input mapping rules, output mapping rules, and interface description information. Based on the MCP Server configuration information and the resource configuration information, deployment parameters for running the MCP Server and the service resources are generated; The deployment parameters are sent to the target server so that the target server deploys the runtime environment corresponding to the MCP Server based on the deployment parameters. In response to the debugging command for the service resource, a debugging operation is performed based on the operating environment to obtain the debugging result; If the debugging results indicate that the service resource meets the preset operating conditions, a service node construction request is sent to the target server so that the target server can construct an MCP Server node in a pending call state based on the service node construction request and generate node metadata of the MCP Server node. The MCP Server node is used to carry the service resource and respond to the call request of the target model to execute the corresponding resource service task. The system receives node metadata sent by the target server and registers the node metadata with the MCP Server management platform. The node metadata is used to identify the MCP Server node and provide call routes for the MCP Server node.

2. The method as described in claim 1, characterized in that, The step of obtaining the user-defined MCP Server configuration information and the resource configuration information of the service resources associated with the MCP Server configuration information through the MCP Server configuration page includes: Obtain initial MCP Server information through the MCP Server configuration page; The initial information of the MCP Server is validated to obtain the validation result; If the verification result indicates that the initial information of the MCP Server has passed the verification, the MCP Server configuration information is generated in the MCP Server management platform based on the initial information of the MCP Server. In response to a service resource registration instruction for the MCP Server configuration information, resource configuration information of the service resources associated with the MCP Server configuration information is obtained.

3. The method as described in claim 2, characterized in that, The step of obtaining resource configuration information of the service resources associated with the MCP Server configuration information in response to a service resource registration instruction for the MCP Server configuration information includes: In response to a service resource registration instruction for the MCP Server configuration information, a service resource registration context is generated, wherein the service resource registration context is used to limit the interaction constraint parameters between the service resource and the MCP Server configuration information; In the service resource registration context, the input mapping rule editing component, output mapping rule editing component, and interface description information entry component corresponding to the service resource are loaded. The input mapping rule is obtained through the input mapping rule editing component, the output mapping rule is obtained through the output mapping rule editing component, and the interface description information is obtained through the interface description information input component. The input mapping rules, the output mapping rules, and the interface description information are integrated and processed to obtain the resource configuration information of the service resources associated with the MCP Server configuration information.

4. The method as described in claim 3, characterized in that, In the service resource registration context, loading the input mapping rule editing component, output mapping rule editing component, and interface description information input component corresponding to the service resource includes: Obtain the resource type of the service resource; The target configuration template identifier is determined based on the resource type; Obtain the resource configuration interface template that matches the service resources based on the target configuration template identifier; The resource configuration interface template file is rendered into an interactive page, and the input mapping rule editing component, output mapping rule editing component, and interface description information entry component corresponding to the service resource are displayed through the interactive page.

5. The method as described in claim 2, characterized in that, The step of generating deployment parameters for running the MCP Server and the service resources based on the MCP Server configuration information and the resource configuration information includes: The MCP Server configuration information is processed by structured parsing to obtain the MCP Server operating parameter information; The resource configuration information is processed by rule-based parsing to generate interface configuration information compatible with the operating environment of the MCP Server; The MCP Server running parameter information and the interface configuration information are associated and mapped to generate deployment parameters for running the MCP Server and the service resources.

6. The method as described in claim 1, characterized in that, The step of responding to a debugging command for the service resource, performing a debugging operation based on the operating environment, and obtaining debugging results includes: In response to a debugging command for the service resource, a debugging page is displayed; Example input data is generated based on the input mapping rules, and the example input data is displayed on the debug page. After detecting the user's confirmation instruction for the sample input data, the sample input data is converted into a request format that matches the MCP Server through the input mapping rule, and a debug call request is sent to the target server so that the target server generates debug output data based on the debug call request in the runtime environment; Obtain the debug output data returned by the target server, and parse and process the debug output data according to the output mapping rules to generate debug results.

7. The method as described in claim 1, characterized in that, The method further includes: If the debugging results indicate that the service resources do not meet the preset operating conditions, the corresponding operating configuration exceptions of the MCP Server are determined based on the debugging results. The abnormal runtime configuration items are displayed on the abnormal configuration modification page; Obtain the first modification information determined for the aforementioned runtime configuration anomaly item; The deployment parameters are updated based on the first modification information to generate updated deployment parameters; Based on the updated deployment parameters, the step of sending the deployment parameters to the target server, so that the target server deploys the runtime environment corresponding to the MCP Server based on the deployment parameters, is returned.

8. The method as described in claim 1, characterized in that, After registering the node metadata with the MCPServer management platform, the method further includes: In response to a modification request for the service resource, a service resource modification page is displayed; The second modification information is obtained through the service resource modification page; The deployment parameters are updated based on the second modification information to generate updated deployment parameters; Based on the updated deployment parameters, the step of sending the deployment parameters to the target server, so that the target server deploys the runtime environment corresponding to the MCP Server based on the deployment parameters, is returned.

9. A service node deployment method, characterized in that, Applied to a target server, the method includes: The platform client device receives deployment parameters sent by the platform client device. These deployment parameters are generated by the platform client device based on MCPServer configuration information and resource configuration information, and are used to run the MCP Server and the service resources associated with the MCP Server configuration information. The MCP Server configuration information and the resource configuration information are information obtained by the platform client device through the MCP Server configuration page, which is a page displayed by the platform client device through the MCP Server management platform running on the platform client device. Deploy the runtime environment corresponding to the MCP Server based on the deployment parameters; The system receives a service node construction request sent by the platform client device, constructs an MCP Server node in a pending call state based on the service node construction request, and generates node metadata for the MCP Server node. The MCP Server node is used to carry the service resource and respond to the call request of the target model to execute the corresponding resource service task. The service node construction request is a request sent by the platform client device when the debugging result indicates that the service resource meets the preset operating conditions. The debugging result is the result obtained by the platform client device in response to the debugging instruction for the service resource based on the operating environment for debugging operation. The node metadata is sent to the platform client device so that the platform client device registers the node metadata with the MCP Server management platform running on the platform client device. The node metadata is used to identify the MCP Server node and provide call routes for the MCP Server node.

10. A service node deployment system, characterized in that, The service node deployment system includes: platform client devices and target servers; wherein... The platform client device is used to display an MCP Server configuration page through the MCP Server management platform running on the platform client device; obtain user-defined MCP Server configuration information and resource configuration information of service resources associated with the MCP Server configuration information through the MCP Server configuration page, wherein the resource configuration information includes input mapping rules, output mapping rules, and interface description information; generate deployment parameters for running the MCP Server and the service resources based on the MCP Server configuration information and the resource configuration information; and send the deployment parameters to the target server. The target server is configured to receive deployment parameters sent by the platform client device, deploy the runtime environment corresponding to the MCP Server based on the deployment parameters, and receive a service node construction request sent by the platform client device, construct an MCP Server node in a pending call state based on the service node construction request, generate node metadata of the MCP Server node, and send the node metadata to the platform client device. The MCP Server node is used to carry the service resources and respond to the call request of the target model to execute the corresponding resource service tasks. The platform client device is also used to receive node metadata sent by the target server and register the node metadata with the MCP Server management platform. The node metadata is used to identify the MCP Server node and provide call routes for the MCP Server node.

11. A service node deployment device, characterized in that, Applied to platform client devices, the device includes: The first display module is used to display the MCPServer configuration page through the MCPServer management platform running on the platform client device; The first acquisition module is used to acquire the user-determined MCP Server configuration information and the resource configuration information of the service resources associated with the MCP Server configuration information through the MCP Server configuration page. The resource configuration information includes input mapping rules, output mapping rules and interface description information. The generation module is used to generate deployment parameters for running the MCP Server and the service resources based on the MCP Server configuration information and the resource configuration information; The first sending module is used to send the deployment parameters to the target server, so that the target server deploys the runtime environment corresponding to the MCP Server based on the deployment parameters; The debugging module is used to respond to debugging commands for the service resources, perform debugging operations based on the operating environment, and obtain debugging results. The second sending module is used to send a service node construction request to the target server when the debugging result indicates that the service resource meets the preset operating conditions, so that the target server constructs an MCP Server node in a state of waiting to be called based on the service node construction request, and generates node metadata of the MCP Server node. The MCP Server node is used to carry the service resource and respond to the calling request of the target model to execute the corresponding resource service task. The registration module is used to receive node metadata sent by the target server and register the node metadata with the MCP Server management platform. The node metadata is used to identify the MCP Server node and provide call routes for the MCP Server node.

12. A service node deployment device, characterized in that, Applied to a target server, the apparatus includes: The receiving module is used to receive deployment parameters sent by the platform client device. The deployment parameters are deployment parameters generated by the platform client device based on the MCP Server configuration information and resource configuration information for running the MCP Server and the service resources associated with the MCP Server configuration information. The MCP Server configuration information and the resource configuration information are information obtained by the platform client device through the MCP Server configuration page. The MCP Server configuration page is a page displayed by the platform client device through the MCP Server management platform running on the platform client device. The deployment module is used to deploy the runtime environment corresponding to the MCP Server based on the deployment parameters; The construction module is used to receive a service node construction request sent by the platform client device, construct an MCP Server node in a pending call state based on the service node construction request, and generate node metadata of the MCP Server node. The MCP Server node is used to carry the service resource and respond to the call request of the target model to execute the corresponding resource service task. The service node construction request is a request sent by the platform client device when the debugging result indicates that the service resource meets the preset operating conditions. The debugging result is the result obtained by the platform client device in response to the debugging instruction for the service resource based on the operating environment for debugging operation. The third sending module is used to send the node metadata to the platform client device, so that the platform client device registers the node metadata with the MCP Server management platform running on the platform client device. The node metadata is used to identify the MCP Server node and provide call routes for the MCP Server node.

13. An electronic device, characterized in that, include: A processor and a memory; the memory stores a computer program, and the processor executes the computer program to implement the method steps of any one of claims 1-9.

14. A computer storage medium, characterized in that, The computer storage medium stores a plurality of instructions adapted for loading by a processor and executing the method steps as claimed in any one of claims 1-9.

Images