Service node deployment method, system, device and equipment and storage medium

Abstract

The invention discloses a service node deployment method, system and device, equipment and a storage medium, and can improve the deployment and debugging efficiency of service nodes. The method comprises the following steps: acquiring MCP Server configuration information and resource configuration information of service resources; generating deployment parameters used for operating the MCP Server and the service resources; sending the deployment parameters to a target server, so that the target server deploys an operation environment corresponding to the MCP Server based on the deployment parameters; in response to a debugging instruction for the service resources, performing debugging operation based on the running environment to obtain a debugging result; under the condition that the debugging result indicates that the service resource meets the preset operation condition, a service node construction request is sent to a target server, so that the target server constructs an MCP Server node in a to-be-called state, and node metadata of the MCP Server node is generated; and receiving the node metadata sent by the target server, and registering the node metadata in the MCP Server management platform.

Description

Technical Field

[0001] The present application relates to the technical field of service node deployment, and in particular to a service node deployment method, system, device, equipment, and storage medium. Background Art

[0002] In related technologies, there's an increasing demand for models to call on external tools, databases, and other service resources to complete complex tasks. Traditional service resource access methods typically require developers to manually implement deployment, interface adaptation, and data format conversion across different system environments. This not only creates complex processes and high technical barriers, but also easily leads to inconsistent environments and mismatched interface parameters during service configuration, debugging, and updates. This results in long deployment cycles, low efficiency, and poor operational stability. Summary of the Invention

[0003] The embodiments of the present application provide a service node deployment method, system, apparatus, device, and storage medium that can improve the deployment and debugging efficiency of service nodes. The above technical solutions are as follows: In a first aspect, an embodiment of the present application provides a service node deployment method, which is applied to a platform client device, including: 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. The resource configuration information includes 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; Send the deployment parameters to the target server so that the target server deploys the corresponding operating environment of the MCP Server based on the deployment parameters; In response to a debugging instruction for a service resource, performing a debugging operation based on the operating environment to obtain a debugging result; If the debugging result indicates 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 builds an MCP Server node in a waiting-to-be-called state based on the service node construction request and generates 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; Receive node metadata sent by the target server and register the node metadata in the MCP Server management platform. The node metadata is used to identify the MCP Server node and provide call routing for the MCP Server node.

[0004] In one possible implementation, obtaining 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 includes: Obtaining MCP Server initial information through the MCP Server configuration page; performing a validity check on the MCP Server initial information to obtain a verification result; if the verification result indicates that the MCP Server initial information has passed the verification, generating MCP Server configuration information in the MCP Server management platform based on the MCP Server initial information; and obtaining resource configuration information of service resources associated with the MCP Server configuration information in response to a service resource registration instruction for the MCP Server configuration information.

[0005] In one possible implementation, in response to a service resource registration instruction for MCP Server configuration information, obtaining resource configuration information of service resources associated with the MCP Server configuration information includes: 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 define interaction constraint parameters between the service resource and the MCP Server configuration information. An input mapping rule editing component, an output mapping rule editing component, and an interface description information entry component corresponding to the service resource are loaded into the service resource registration context. The input mapping rule editing component obtains a user-defined input mapping rule, the output mapping rule editing component obtains a user-defined output mapping rule, and the interface description information entry component obtains interface description information. The input mapping rule, output mapping rule, and interface description information are integrated to obtain resource configuration information of the service resource associated with the MCP Server configuration information.

[0006] In a possible implementation, in a 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: 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 based on 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.

[0007] In one possible implementation, deployment parameters for running the MCP server and serving resources are generated based on the MCP server configuration information and resource configuration information, including: Perform structured parsing of the MCP Server configuration information to obtain MCP Server operating parameter information; perform rule-based parsing of the resource configuration information to generate interface configuration information compatible with the MCP Server operating environment; perform correlation mapping between the MCP Server operating parameter information and the interface configuration information to generate deployment parameters for running the MCP Server and serving resources.

[0008] In one possible implementation, in response to a debugging instruction for a service resource, performing a debugging operation based on an operating environment to obtain a debugging result includes: In response to a debugging instruction for a service resource, a debugging page is displayed; sample input data is generated based on the input mapping rules and displayed on the debugging page; after detecting a user confirmation instruction for the sample input data, the sample input data is converted into a request format that matches the MCP Server using the input mapping rules, and a debugging call request is initiated to the target server, so that the target server generates debugging output data based on the debugging call request in the running environment; the debugging output data returned by the target server is obtained, and the debugging output data is parsed and processed according to the output mapping rules to generate a debugging result.

[0009] In one possible implementation, the method further includes: If the debugging result indicates that the service resource does not meet the preset operating conditions, an abnormal operation configuration item corresponding to the MCP Server is determined based on the debugging result; the abnormal operation configuration item is displayed on the abnormal configuration modification page; first modification information determined for the abnormal operation configuration item is obtained; deployment parameters are updated based on the first modification information to generate updated deployment parameters; and based on the updated deployment parameters, the step of sending the deployment parameters to the target server is returned to execute, so that the target server deploys the operating environment corresponding to the MCP Server based on the deployment parameters.

[0010] In one possible implementation, after registering the node metadata on the MCP Server management platform, the method further includes: In response to a modification request for a service resource, 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; and based on the updated deployment parameters, the step of sending the deployment parameters to a target server is returned to execute, so that the target server deploys an operating environment corresponding to the MCP Server based on the deployment parameters.

[0011] In a second aspect, an embodiment of the present application provides a service node deployment method, which is applied to a target server and includes: Receive deployment parameters sent by the platform client device. 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. Deploy the corresponding operating environment of MCP Server based on the deployment parameters; Receive a service node construction request sent by a platform client device, and build an MCP Server 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 the call request of the target model to perform 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 of the platform client device performing debugging operations based on the operating environment in response to the debugging instruction for the service resource; 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 a call route for the MCP Server node.

[0012] In a third aspect, an embodiment of the present application provides a service node deployment system, comprising: a platform client device and a target server; wherein, The platform client device is configured to display the MCP Server configuration page through the MCP Server management platform running on the platform client device; obtain 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 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; The target server is configured to receive deployment parameters sent by the platform client device and deploy the operating environment corresponding to the MCP Server based on the deployment parameters; and receive a service node construction request sent by the platform client device, and construct an MCP Server node in a pending call state based on the service node construction request, generate node metadata for 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 target model's call request to execute the corresponding resource service task. The platform client device is also used to receive node metadata sent by the target server and register the node metadata in the MCP Server management platform. The node metadata is used to identify the MCP Server node and provide a call route for the MCP Server node.

[0013] In a fourth aspect, an embodiment of the present application provides a service node deployment device, which is applied to a platform client device, including: The first display module is used to display the MCP Server configuration page through the MCP Server management platform running on the platform client device; A first acquisition module is configured to acquire, through the MCP Server configuration page, MCP Server configuration information determined by the user and resource configuration information of service resources associated with the MCP Server configuration information, wherein the resource configuration information includes input mapping rules, output mapping rules, and interface description information; A 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; A first sending module is configured to send the deployment parameters to the target server, so that the target server deploys the operating environment corresponding to the MCP Server based on the deployment parameters; A debugging module, configured to respond to debugging instructions for service resources, perform debugging operations based on the operating environment, and obtain debugging results; The second sending module is configured to send a service node construction request to the target server if 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 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 call requests from the target model to execute corresponding resource service tasks. The registration module is used to receive the node metadata sent by the target server and register the node metadata in the MCPServer management platform. The node metadata is used to identify the MCP Server node and provide a call route for the MCP Server node.

[0014] In a fifth aspect, an embodiment of the present application provides a service node deployment device, which is applied to a target server and includes: A receiving module, configured to receive deployment parameters sent by a platform client device. The deployment parameters are 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. The deployment module is used to deploy the corresponding operating environment of the MCP Server based on the deployment parameters; A construction module is configured to receive a service node construction request sent by a platform client device, construct an MCP Server 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. The service node construction request is a request sent by the platform client device when a debugging result indicates that the service resource meets preset operating conditions. The debugging result is the result of the platform client device performing debugging operations based on the operating environment in response to the debugging instruction for the service resource. 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 run by the platform client device. The node metadata is used to identify the MCP Server node and provide a call route for the MCP Server node.

[0015] In a sixth aspect, an embodiment of the present application provides an electronic device comprising: a processor and a memory; the memory stores a computer program, and when the processor executes the computer program, the method steps provided in the first aspect or the second aspect of the embodiment of the present application are implemented.

[0016] In the seventh aspect, an embodiment of the present application provides a computer storage medium, which stores multiple instructions, and the instructions are suitable for being loaded by a processor and executing the method steps provided in the first aspect or the second aspect of the embodiment of the present application.

[0017] The service node deployment method provided in the embodiment of the present application uses the MCP Server management platform to display an MCP Server configuration page through a platform client device; obtains 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 including input mapping rules, output mapping rules, and interface description information; generates deployment parameters for running the MCP Server and the service resources based on the MCP Server configuration information and the resource configuration information, and then sends the deployment parameters to the target server so that the target server deploys the operating environment corresponding to the MCP Server based on the deployment parameters; responds to the debugging instruction for the service resource, performs a debugging operation based on the operating environment, and obtains a debugging result; if the debugging result indicates that the service resource meets the preset operating conditions, sends a service node construction request to the target server so that the target server constructs an MCP Server node in a waiting-to-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 the service resources and respond to the call request of the target model to perform the corresponding resource service task; 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 the MCP Server node with the MCP Server management platform. The call route of the Server node. In this way, the automated configuration, deployment and management of the MCP Server and its associated service resources can be realized. Through the MCP Server management platform in the platform client device, a visual low-code configuration platform is provided for users, allowing users to complete the entire process from configuration entry, parameter generation, environment deployment to debugging verification, service node construction and registration in a unified interface, reducing the complexity of manual configuration and improving the efficiency of service deployment and debugging. At the same time, the service node is built into a waiting-to-call state only after the preset operating conditions are met, which improves the stability and reliability of the service. The registration of node metadata and the establishment of call routes enable the target model to quickly and accurately access service resources based on a unified route, improving the flexibility and scalability of service node calls. BRIEF DESCRIPTION OF THE DRAWINGS

[0018] In order to more clearly illustrate the technical solutions in the embodiments of the present application, the following briefly introduces the drawings required for use in the embodiments. Obviously, the drawings described below are only some embodiments of the present application. For ordinary technicians in this field, other drawings can be obtained based on these drawings without creative work.

[0019] Figure 1A schematic diagram of an application environment of a service node deployment method provided by an exemplary embodiment of the present application; Figure 2 A flowchart of a service node deployment method provided by an exemplary embodiment of the present application; Figure 3 A flowchart of another service node deployment method provided by an exemplary embodiment of the present application; Figure 4 A schematic diagram of a service list page provided by an exemplary embodiment of the present application; Figure 5 A schematic diagram of an MCP Server configuration page provided by an exemplary embodiment of the present application; Figure 6 A schematic diagram of a resource configuration page provided for an exemplary embodiment of the present application; Figure 7 A flowchart of another service node deployment method provided by an exemplary embodiment of the present application; Figure 8 A schematic diagram of a debugging page provided by an exemplary embodiment of the present application; Figure 9 A schematic structural diagram of a first service node deployment device provided by an exemplary embodiment of the present application; Figure 10 A schematic structural diagram of a second service node deployment device provided by an exemplary embodiment of the present application; Figure 11 A schematic structural diagram of an electronic device provided as an exemplary embodiment of the present application; Figure 12 A schematic structural diagram of another electronic device provided as an exemplary embodiment of the present application. DETAILED DESCRIPTION

[0020] 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.

[0021] 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 understood as indicating or implying relative importance. For those of ordinary skill in the art, the specific meanings of the above terms in this application can be understood according to specific circumstances. In addition, in the description of this application, unless otherwise specified, "multiple" refers to two or more. "And / or" describes the association relationship of associated objects, indicating that three relationships may exist. For example, A and / or B can represent: A exists alone, A and B exist at the same time, and B exists alone. The character " / " generally indicates that the previous and subsequent associated objects are in an "or" relationship.

[0022] In order to more clearly describe the technical solution of the embodiment of the present application, some concepts in the present application are described in detail before the description to facilitate a better understanding of the solution.

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

[0024] The Model Context Protocol Server (MCP Server) is a service that provides artificial intelligence (AI) MCP.

[0025] In related technologies, there is an increasing demand for models to call external tools, databases, and other service resources to complete complex tasks. For example, when the target model (such as a large language model) carried by 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 the target model with service resources corresponding to the above capabilities (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 has high technical barriers, but also prone to environmental inconsistencies and interface parameter mismatches during the configuration, debugging, and updating of service nodes, resulting in long deployment cycles, low efficiency, and poor operational stability.

[0026] Therefore, the present application provides a service node deployment method, system, apparatus, device and storage medium to solve the above-mentioned technical problems of low service node deployment efficiency and debugging efficiency.

[0027] The service node deployment method provided in the embodiment of the present application can be applied to Figure 1In the application environment shown, the platform client device 10, the target server 20 and the terminal device 30 communicate with each other through a network.

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

[0029] 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 locally deployed high-performance server. It can build an operating 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 data that the target server 20 needs to process, such as merchant information. The data storage system can be integrated with the target server 20 or located in the cloud or on other network servers.

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

[0031] In some possible embodiments, the platform client device 10 displays an MCP Server configuration page through an MCP Server management platform running on the platform client device 10; obtains user-determined MCP Server configuration information and resource configuration information of 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; generates deployment parameters for running the MCP Server and service resources based on the MCP Server configuration information and resource configuration information; sends the deployment parameters to the target server 20 so that the target server 20 deploys the operating environment corresponding to the MCP Server based on the deployment parameters; responds to debugging instructions for the service resources, performs debugging operations based on the operating environment, and obtains debugging results; if the debugging results indicate that the service resources meet preset operating conditions, 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 host service resources and respond to call requests from the target model (running on the terminal device 30) to perform corresponding resource service tasks; receives the node metadata sent by the target server 20, and registers the node metadata in the MCP Server management platform, node metadata is used to identify MCP Server nodes and provide call routing for MCP Server nodes.

[0032] It is understandable that the platform client device 10 and the terminal device 30 can be implemented by a single terminal device or a terminal cluster consisting of multiple terminals. The target server 20 can be implemented by an independent server or a server cluster consisting of multiple servers.

[0033] In one embodiment, Figure 2 As shown, a service node deployment method is provided, which is applied to Figure 1 The following steps are described using the application environment shown as an example: S201: Displaying an MCP Server configuration page through the MCP Server management platform running on the platform client device.

[0034] The platform client device can be a terminal for user use (such as a 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.

[0035] Optionally, the above user may be an administrator user (such as a developer, configuration personnel, or platform operation and maintenance personnel of the MCP Server management platform).

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

[0037] S202: 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.

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

[0039] Optionally, the input mapping rules can be used to convert the input information of the target model or terminal device side into standardized request parameters that meet the requirements of the target interface call, such as renaming the fields, converting the value types, filling the default values ​​and injecting authentication information, so that the target interface can correctly receive and parse the request data. The output mapping rules can be used to format the original response results returned by the target interface, such as filtering and renaming the response fields, simplifying the complex nested structures, semantically converting the enumeration values ​​or status codes, and performing necessary desensitization operations, thereby generating concise, standardized and easy-to-understand and use output results for the target model. The interface description information can be used to describe the basic call properties of the target interface, including the interface type, call address or identifier, request method, required parameters, authentication method, and example input and output parameters, etc., to provide a structured call basis for input mapping and output mapping. Through the above configuration, it is possible to achieve effective docking between the target model input and the interface call format, and enable the interface call results to be returned in a form that conforms to the model processing logic, thereby achieving efficient management and unified calling of service resources.

[0040] In one embodiment, the resource configuration information of the service resource may also include, but is not limited to, resource identification, resource name, resource description information, and resource permissions. Taking the service resource as a tool as an example, the resource configuration information of the tool may include the tool name, tool identification, tool description, and tool permissions. Among them, the resource identification can be used to uniquely identify the service resource so that it can be accurately located during the configuration and calling process; the resource name can be used to intuitively name the service resource, which is convenient for users to identify and manage in the configuration page; the resource description can be used to explain the functional characteristics, applicable scenarios, and usage restrictions corresponding to the service resource so that users can quickly understand the purpose of the resource; resource permissions can be used to limit the scope of subjects who can access and call the service resource, such as distinguishing the usage permissions of users at different levels to ensure the security and compliance of service resources. 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 calling.

[0041] In an embodiment of the present application, the MCP Server can be an operating platform that carries and manages service resources, and its role is to provide a unified calling entry point and service execution environment for the target model. Service resources are specific functional units scheduled and run by the MCP Server, such as merchant information query service, map path planning service, order status query service, etc. The MCP Server itself does not directly implement specific service functions, but can provide callable service capabilities to the outside world by loading, configuring and managing these service resources. In other words, the MCP Server configuration information is used to define the overall operating parameters and deployment rules of the MCP Server, while the resource configuration information of the service resources is used to define the functional attributes and interface rules of each specific service resource. The MCP Server configuration information and the resource configuration information can be a management relationship: the MCP Server is responsible for carrying and scheduling as a platform, and the service resources are managed objects that provide actual functions. By effectively binding the service resources to the MCP Server, the target model can indirectly use the required resource services by calling the MCP Server node in the subsequent process.

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

[0043] Deployment parameters refer to the configuration information and operating parameters required to successfully run the MCP Server and its associated service resources on the target server. Deployment parameters not only determine how the MCP Server's operating environment is initialized, but also how specific service resources are loaded, scheduled, and invoked.

[0044] For example, deployment parameters may include, but are not limited to, the following: MCP Server operating parameters (such as operating 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 resources and limit the access scope).

[0045] In one embodiment, basic parameters describing the MCP Server operating environment can be obtained based on the MCP Server configuration information. Subsequently, the loading method, interface description information, input mapping rules, output mapping rules, and resource permission information of the service resources associated with the MCP Server configuration information 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 for the target server to automatically complete the initialization of the MCP Server operating environment, the mounting and loading of service resources, and the routing registration, thereby enabling the MCP Server and its associated service resources to operate normally on the target server and provide external services.

[0046] S204: Send the deployment parameters to the target server, so that the target server deploys the operating environment corresponding to the MCPServer based on the deployment parameters.

[0047] In one embodiment, in response to a user's instruction to determine 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 deployment engine of the target server, thereby completing the automated deployment of the MCP Server operating environment and its service resources.

[0048] Optionally, the target server receives deployment parameters sent by the platform client device and deploys the corresponding runtime environment of the MCP Server based on the deployment parameters. The runtime environment can be the basic execution environment for running the MCP Server service and associated service resources. The runtime environment may include, but is not limited to, an operating system environment, a container runtime, dependency libraries, network configuration, and interface adapter modules corresponding to the service resources. The runtime environment ensures that the MCP Server and its service resources are executable, callable, and testable on the target server.

[0049] S205: In response to the debugging instruction for the service resource, a debugging operation is performed based on the operating environment to obtain a debugging result.

[0050] Debugging instructions can be issued by users or platform client devices to verify whether service resources can function normally in the deployed operating environment. Debugging instructions can also include service call requests, test parameters, simulated input data, etc., used to trigger the execution of corresponding service resources.

[0051] In one embodiment, the debugging instruction may be triggered by a user in the debugging interface of the MCP Server management platform, for example, by clicking a "debug" button or inputting a test request.

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

[0053] Optionally, the debugging result can be feedback from the runtime environment after the debugging operation completes, indicating whether the service resource meets the preset operating conditions. The debugging result can include a success / failure indicator, as well as detailed feedback such as specific logs, output data, and error messages. If the debugging result meets expectations (e.g., correct output and normal interface response), the service resource meets the operating conditions and can proceed to the subsequent service node construction phase. If the debugging result is abnormal, the developer needs to make corrections and redeploy based on the feedback.

[0054] S206: When the debugging result indicates 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 constructs an MCP Server node in a waiting-to-be-called state based on the service node construction request and generates 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.

[0055] Preset operating conditions are the operational standards used to determine whether a service resource can be formally deployed and invoked. These conditions may include functional correctness (output results consistent with expectations), interface connectivity (matching input-output mapping rules), performance metrics (response time, throughput), and stability (consistent results across multiple executions). It should be understood that if a service resource meets these conditions, it has passed basic verification and can be formally built as a callable service node.

[0056] Optionally, a service node build request can be used to instruct the target server to encapsulate the verified service resources into a runnable, callable, independent service node. This request can include the service resource identifier, deployment parameter references, runtime environment information, and the node build method. This request triggers the target server to perform a formal build operation, thereby generating the corresponding MCP Server service node.

[0057] Optionally, an MCP Server node in a pending call state refers to a service node that has been built on the target server but has not yet been actually called by the target model. At this point, the MCP Server node is capable of running but is in a pending call state. Once the MCP Server node receives a call request from the target model, it immediately starts and executes the corresponding resource service task. Node metadata can be structured descriptive information generated by the target server when building the MCP Server node. It may include, but is not limited to: the MCP Server node's unique identifier, the MCP Server node address (call route), supported service resource types, interface description information, and MCP Server node status information. Node metadata is registered with the MCP Server management platform for subsequent node call and route management.

[0058] 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 field AI model. The target model needs to implement extended functions by calling the MCP Server service node. For example, the large model in the takeaway scenario needs to call the "merchant information query service node", "order status service node" or "delivery scheduling service node" to complete the end-to-end service logic. The call request is an execution request issued by the target model to the MCP Server service node, which can include specific task instructions and input data. For example, "get the delivery status of the order" can be used as a call request. After receiving the call request, the MCP Server node can process it according to the resource configuration and return the result (such as the delivery status details of the order).

[0059] It's understood that the corresponding resource service task is the task logic that the MCP server node actually executes after receiving a call request. It corresponds one-to-one with the function of the service resource. For example, the resource service task for the merchant information query service is to execute a database query and return merchant details; the resource service task for the order status acquisition service is to call the order management system application programming interface (API) to return the order progress. After the task is completed, the task results can be fed back to the target model for subsequent intelligent response.

[0060] S207: Receive the node metadata sent by the target server and register the node metadata in the MCP Server management platform. The node metadata is used to identify the MCP Server node and provide a call route for the MCP Server node.

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

[0062] 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 the request to the corresponding service node based on the call routing, thereby ensuring stable call of service resources and task execution.

[0063] The service node deployment method provided in the embodiment of the present application uses the MCP Server management platform to display an MCP Server configuration page through a platform client device; obtains 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 including input mapping rules, output mapping rules, and interface description information; generates deployment parameters for running the MCP Server and the service resources based on the MCP Server configuration information and the resource configuration information, and then sends the deployment parameters to the target server so that the target server deploys the operating environment corresponding to the MCP Server based on the deployment parameters; responds to the debugging instruction for the service resource, performs a debugging operation based on the operating environment, and obtains a debugging result; if the debugging result indicates that the service resource meets the preset operating conditions, sends a service node construction request to the target server so that the target server constructs an MCP Server node in a waiting-to-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 the service resources and respond to the call request of the target model to perform the corresponding resource service task; 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 the MCP Server node with the MCP Server management platform. The call route of the Server node. In this way, the automated configuration, deployment and management of the MCP Server and its associated service resources can be realized. Through the MCP Server management platform in the platform client device, a visual low-code configuration platform is provided for users, allowing users to complete the entire process from configuration entry, parameter generation, environment deployment to debugging verification, service node construction and registration in a unified interface, reducing the complexity of manual configuration and improving the efficiency of service deployment and debugging. At the same time, the service node is built into a waiting-to-call state only after the preset operating conditions are met, which improves the stability and reliability of the service. The registration of node metadata and the establishment of call routes enable the target model to quickly and accurately access service resources based on a unified route, improving the flexibility and scalability of service node calls.

[0064] In one embodiment, Figure 3 As shown, another service node deployment method is provided, which is applied to Figure 1 The platform client device 10 is used as an example for description, and the following steps are included: S301: Displaying an MCP Server configuration page via the MCP Server management platform running on a platform client device.

[0065] In some embodiments, an MCP Server configuration page can be displayed via the MCP Server management platform running on a platform client device in response to a user-triggered service creation instruction. The service creation instruction can be triggered by the user triggering a new service control on the service list page, which can be used to display information related to each service.

[0066] Figure 4 A schematic diagram of a service list page provided by an exemplary embodiment of the present application is shown as follows: Figure 4The service list page 400 can display the MCP Servers currently available in the MCP Server management platform to the user. Specifically, the service list page 400 can display a first navigation bar 401, which includes category controls corresponding to labels such as "I Manage," "Visible to Me," "All Plans," and "No Permission Plans." This can be used to categorize and display MCP Servers, allowing administrators to quickly filter services based on their permissions. Taking "All Plans" as an example, the service list page 400 can also display existing MCP Server entries, such as a merchant MCP Server entry 402, a map MCP Server entry 403, an MCP Server test entry 404, and a tool test entry 405. The services represented by the merchant MCP Server entry 402 can be used to host 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 the 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 search. The Map MCP can support route scheduling and location information querying in scenarios such as food delivery and travel. The service represented by the MCP Server Test entry 404 can be used to provide testing service resources, such as verifying the proper operation of the MCP Server deployment, configuration, and invocation, facilitating functional and performance debugging before launch. The service represented by the Tool Test entry 405 can be used to provide general tool service resources, such as data format conversion, message push, log collection and analysis, to support the invocation and verification of auxiliary functions during development and debugging. Each service entry can be displayed as a card, which may include, but is not limited to, the service name, service identifier, service description, and user permission information. The user permission information indicates the type of permissions the current administrator has for the service, such as "administrator permissions" or "read-only permissions." Administrators can perform actions based on these entries, such as clicking to enter the corresponding management interface to adjust the service's configuration parameters or triggering a deletion operation to remove a no longer needed service.

[0067] In addition, a search box 406 may be provided on the service list page 400. Search box 406 is used to receive user input for quick location of service entries. Users can enter a service identifier (e.g., a code), name, or description in search box 406. The MCP Server management platform then performs a fuzzy match query on the service entries displayed on the current page based on the search information. Query results are displayed after the user completes their input and presses the Enter key. This allows users to quickly find the target MCP Server even when there are many services, improving the efficiency of service retrieval and configuration.

[0068] Furthermore, the service list page 400 can also include a new service control 407. Upon detecting a user triggering this new service control 407, a service creation instruction is triggered, and the MCP Server configuration page is displayed for creating and configuring a new MCP Server. This allows users to manage existing services while also flexibly expanding new ones. The MCP Server management platform significantly improves service management efficiency through intelligent categorized navigation, visual service cards, and a cluster of efficiency tools.

[0069] S302: Obtaining MCP Server initial information through the MCP Server configuration page.

[0070] The MCP Server initial information allows users to set basic descriptive parameters for the MCP Server they want to create or manage on the MCP Server configuration page. This information can be used to identify and distinguish different service instances and provide metadata support for subsequent service deployment and invocation. This initial information may include, but is not limited to: a service name, which uniquely identifies the MCP Server for easy identification and management; a service identifier, which is a unique identifier generated or specified for the MCP Server and used to bind subsequent deployment parameters and invocation routes; version information, which records the MCP Server version number to support version iteration and compatibility management; a service description, which briefly describes the MCP Server's functionality; a service type, which specifies the configuration parameters for the operating environment category of the created MCP Server, clarifying the type of operating platform or deployment environment in which the MCP Server service will be installed and executed; and service permissions, which limit the scope of operations 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 operating status but not change them; operating port number, which refers to the network port number used by the MCP Server to provide external services in the target operating environment; communication protocol type, which refers to the transmission protocol and format standard followed by the MCP Server when exchanging data with external systems or callers; dependent middleware information, which refers to the third-party software components or basic services that the MCP Server relies on during operation, such as databases, message queues, cache services, and registration centers; log configuration, which refers to the parameter settings related to recording service status and operating behavior during operation of the MCP Server; and network access mode, which refers to the definition of network access modes and access paths supported by the MCP Server when providing external services.

[0071] Figure 5 A schematic diagram of an MCP Server configuration page provided by an exemplary embodiment of the present application is shown as follows: 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 permissions configuration area 504. The basic information area 502 allows users to enter or select information such as the service ID, service name, and service description; the service configuration area 503 allows users to enter or select information such as the service type; and the permissions configuration area 504 allows users to enter or select service permissions such as administrator or read-only member. Optionally, the service type can be any of the following: a public Time-Triggered Protocol (TPP), a private TPP, or a custom type, indicating 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 operating environment pre-provided by the platform. Users can quickly start the MCP Server based on the public TPP without having to deploy server resources separately, so as to achieve rapid verification and debugging of service resources; the private TPP is used to indicate the target platform deployed by the user in its proprietary operating environment based on the MCP Server solution. After deployment, it can provide the same tool registration and script conversion capabilities as the public TPP, and realize instance-level differentiation and management through a unique TPP identifier, thereby improving the independence of service operation and data security; the custom one is used to instruct the user to bind the MCP Server to a specific third-party operating environment or external service resource by entering a custom Uniform Resource Locator (URL) and path information during the configuration process, so that the MCP Server can be loaded and executed in the user-specified exclusive environment, thereby achieving flexible support for differentiated application scenarios.

[0072] On the MCP Server configuration page 500, the user can complete steps such as setting the unique identifier of the MCP Server, selecting the operating environment, and assigning permissions. The user can also cancel the current operation by clicking the Cancel control 505 on the MCP Server configuration page 500, or submit the configuration result by clicking the Save control 506. Thus, the MCP Server configuration page acquires initial MCP Server information.

[0073] S303: Perform a validity check on the MCP Server initial information to obtain a verification result.

[0074] In one embodiment, the legitimacy check may include at least one of the following verification methods: verifying the matching of the communication protocol type and the operating port number, that is, determining whether the communication protocol type and the operating port number configured by the user in the MCP Server initial information meet the preset matching rules to avoid service startup anomalies caused by inconsistencies between the protocol and the port number; checking the compatibility of the network access method with the preset security policy, that is, checking whether the access method set by the user (e.g., intranet access, public network access, etc.) complies with the security control policy specified by the platform, thereby ensuring data transmission security and access compliance during the operation of the MCP Server; confirming the uniqueness of the service identifier in the current platform, that is, verifying whether the service identifier entered by the user conflicts with an identifier 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 operation risks caused by configuration conflicts or non-compliant operations can be effectively avoided, thereby improving the stability and security of the system.

[0075] Optionally, the verification result may indicate that the MCP server initial information verification passed or failed. If the verification result indicates that the MCP server initial information verification failed, a specific error reason (such as "service identifier already exists" or "service type is invalid") may be returned.

[0076] For example, if the MCP server initial information meets the following conditions, the MCP server initial information can be determined to meet the validity condition, and a verification result indicating that the MCP server initial information has passed verification is generated: the communication protocol type and the operating port number correctly match, and the operating port number is not occupied; the selected network access method complies with the preset security policy, for example, it does not violate firewall rules or use prohibited plaintext transmission methods; and the server identifier is unique within the current configuration platform, i.e., there is no duplicate identifier with other configured MCP servers. Furthermore, if the MCP server initial information does not meet any of the above conditions, the MCP server initial information is determined to not meet the validity condition, and a verification result indicating that the MCP server initial information has failed verification is generated.

[0077] S304: When the verification result indicates that the MCP Server initial information verification has passed, MCP Server configuration information is generated in the MCP Server management platform based on the MCP Server initial information.

[0078] In one embodiment, the MCP Server management platform can structure and map initial MCP Server information according to predefined configuration templates to form a standardized set of configuration information, resulting in MCP Server configuration information, which is then stored on the MCP Server management platform. MCP Server configuration information is not only used to distinguish different service instances but also serves as fundamental metadata for subsequent resource configuration, deployment parameter generation, and service node construction, ensuring consistency and manageability of the MCP Server within the operating environment.

[0079] In this embodiment, by obtaining initial MCP Server information on the MCP Server configuration page and performing a validation and standardized generation process within the management platform, each MCP Server is equipped with a clear unique identifier, compliant access policies, and correct communication configuration during its 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 this initial information not only enables standardized management of different service instances but also provides unified metadata support for subsequent resource configuration, deployment parameter generation, and service node construction, thereby improving system scalability, stability, and operational efficiency.

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

[0081] The service resource registration instruction may be an operation triggered by a user (such as clicking a register resource button), indicating that a specific service resource is bound to a configured MCP Server.

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

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

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

[0085] In one embodiment, after generating the service resource registration context environment, a resource configuration page can also be displayed. The resource configuration page can include a new resource control. When it is detected that the user triggers the new resource control, it is determined to execute S306 to load the input mapping rule editing component, output mapping rule editing component and interface description information entry component corresponding to the service resource in the service resource registration context environment.

[0086] Figure 6 A schematic diagram of a resource configuration page provided by an exemplary embodiment of the present application is shown as follows: 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 sections, such as an "Online Tool" display area 602, a "Non-Online Tool" display area 603, and a "De-Offline Tool" display area 604. The "Online Tool" display area 602 displays tool resources that have been successfully registered and published. Users can use this area to perform version management, configuration updates, or de-offline operations on these tools. The "Non-Online Tool" display area 603 displays tool resources that have completed preliminary configuration but have not yet been published. Users can use this area to debug, add information, or perform publishing operations. The "De-Offline Tool" display area 604 displays tool resources that have been de-offlined. Users can use this area to re-publish or completely delete these tools as needed. In addition, the resource configuration page 600 may also include a new resource control 605. Upon detecting a user trigger, the new resource control 605 is used to obtain the user-specified basic resource information and invoke step S306, which 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 uniformly manage and maintain resources in different states within a single page, supporting both the addition, configuration, and release of service resources, as well as their decommissioning and version evolution. This improves the operational efficiency and controllability of service resources within the MCP Server.

[0087] 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, allowing users to 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 mapping relationships, data type conversion rules, default value filling methods, and other settings, 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 tailoring output data to ensure that the results received by the caller conform to the interface contract and user experience. The interface description information entry component can be a tool for entering and managing descriptive information about the service resource interface. This interface description information entry component is primarily used to supplement unstructured but critically important interface metadata for the caller, such as interface function description, input and output parameter meanings and value ranges, call methods, authentication methods, and error code descriptions. The description information entered by this component can automatically generate interface documentation or configuration files, making it easier for callers to understand and correctly use service resources. This description information can also be used for automated verification (for example, detecting missing caller parameters or type mismatches) and debugging assistance.

[0088] In one embodiment, the basic resource information may include resource identifiers, resource names, resource descriptions, resource permissions, query per second (QPS) rate limiting information, remote procedure call (RPC) information, etc. QPS rate limiting information can be used to configure the tool's maximum request rate, such as 100 QPS; RPC information can be used to define the tool's remote call method. RPC information may include the following types: High-speed Service Framework (HSF) RPC, Hypertext Transfer Protocol (HTTP) RPC, TPP RPC, and Solution RPC.

[0089] In one embodiment, in a service resource registration context environment, 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: obtaining the resource type of the service resource; determining the target configuration template identifier based on the resource type; obtaining a 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.

[0090] Exemplarily, the resource type of the service resource to be registered can be obtained first; then, the target configuration template identifier is determined based on the resource type, and the identifier is used to uniquely indicate the configuration template that matches the resource type; then, 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, which is used to define the page layout, parameter items and component call logic required in the service resource configuration process; finally, the resource configuration interface template is rendered into an interactive page, and the input mapping rule editing component, output mapping rule editing component and 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 standardized registration and management of service resources.

[0091] In the embodiment of the present application, when loading the service resource configuration interface, the corresponding configuration template is automatically matched and called according to the resource type of different service resources, thereby generating a unified interactive page. This can effectively avoid the tedious operations of manual selection or repeated configuration by the user, thereby improving the automation and standardization of service resource registration. In addition, 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 MCP Server.

[0092] S307: Acquire the input mapping rule determined by the user through the input mapping rule editing component, acquire the output mapping rule determined by the user through the output mapping rule editing component, and acquire the interface description information through the interface description information entry component.

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

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

[0095] Optionally, the input mapping rules are first converted into a standardized parameter mapping table to clarify the correspondence between external call parameters and internal execution parameters of the MCP Server. Subsequently, the output mapping rules are converted into a result mapping table to uniformly encapsulate and format the original output results of the 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 that includes elements such as the interface name, call 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 can include basic tool information, technical constraints for input and output, and a semantic description of the interface description, which can serve as the basis for subsequent deployment parameter generation, runtime environment construction, and service call routing configuration.

[0096] In one embodiment, integrating input mapping rules, output mapping rules, and interface description information can include: converting model input parameters into standardized inputs required by the external service interface based on the field mapping rules defined in the input mapping rules; and extracting and transforming the complex JSON data returned by the external interface based on the output mapping rules, retaining only the required key fields to produce a simplified output result. For example, for JSON data containing a large amount of store information returned by the external interface, a script can be used to extract the "store name" and "store address" fields, thereby generating a concise and clear output result, which is then stored in association with the MCP server as the configuration content of the service resource.

[0097] In this embodiment, by introducing a service resource registration context into the service resource registration process and loading the input mapping rule editing component, output mapping rule editing component, and interface description information entry component into this context, 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 the structured entry of interface description information, thereby enhancing the operational efficiency and controllability of the entire MCP Server operating environment.

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

[0099] For details, please refer to the above S203, which will not be described again here.

[0100] S310: Send the deployment parameters to the target server, so that the target server deploys the operating environment corresponding to the MCPServer based on the deployment parameters.

[0101] For details, please refer to the above S204, which will not be repeated here.

[0102] S311: In response to the debugging instruction for the service resource, a debugging operation is performed based on the operating environment to obtain a debugging result.

[0103] For details, please refer to the above S205, which will not be repeated here.

[0104] S312: When the debugging result indicates 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 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 request of the target model to perform the corresponding resource service task.

[0105] For details, please refer to the above S206, which will not be repeated here.

[0106] S313: Receive the node metadata sent by the target server and register the node metadata in the MCP Server management platform. The node metadata is used to identify the MCP Server node and provide a call route for the MCP Server node.

[0107] For details, please refer to the above S207, which will not be repeated here.

[0108] In the embodiment of the present application, through the full-process automated management of service nodes from configuration, verification, registration to deployment, the legitimacy and uniqueness of service information can be improved, standardized binding and flexible expansion of service resources can be supported, the security and compatibility of interface calls can be improved, and thus the efficiency and reliability of service deployment can be improved.

[0109] In one embodiment, Figure 7 As shown, another service node deployment method is provided, which is applied to Figure 1 The platform client device 10 is used as an example for description, and the following steps are included: S701: Displaying an MCP Server configuration page through the MCP Server management platform running on the platform client device.

[0110] For details, please refer to the above S201, which will not be repeated here.

[0111] S702: Obtain 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.

[0112] For details, please refer to the above S202, which will not be repeated here.

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

[0114] For details, please refer to the above S203, which will not be described again here.

[0115] S704: Send the deployment parameters to the target server, so that the target server deploys the operating environment corresponding to the MCPServer based on the deployment parameters.

[0116] For details, please refer to the above S204, which will not be repeated here.

[0117] S705: In response to the debugging instruction for the service resource, display a debugging page.

[0118] The debugging page is an interactive interface provided by the MCP Server management platform after service resource configuration is complete. It allows users to verify configuration correctness and functional availability. This page allows users to intuitively view service resource input and output rules, interface descriptions, and real-time debugging results. The debugging page allows users to enter test parameters, execute calls, view return results, and troubleshoot anomalies, ensuring that service resource configuration meets expectations before release.

[0119] Optionally, sample input data can be automatically generated based on user-configured input mapping rules, allowing you to simulate external call requests within the debugging interface. The sample input data adheres to 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 the correctness of input parameter mapping without having to manually construct complex test requests, thereby improving debugging efficiency and accuracy.

[0120] Figure 8A schematic diagram of a debugging page provided by an exemplary embodiment of the present application is shown as follows: Figure 8 , the debugging page 800 can include an example page function description area 801, a generate example control 802, a fill data control 803, an example data display area 804, an input data area 805, an execute debugging control 806, a debugging result display area 807, a copy result control 808, and a view call link control 809. Among them, the example page function description area 801 can be used to display the function introduction and usage instructions of the debugging page 800, prompting users to perform tool debugging operations on this page and guiding users to understand how to input and test data. The generate example control 802 can be used to automatically generate example input data that meets the format requirements according to the input mapping rules, so that users can quickly obtain standardized input references. The fill data control 803 can be used to directly fill the generated example input data into the input data area, thereby reducing the user's manual input operations and improving debugging efficiency. The example data display area 804 can be used to display example input data generated by the system, allowing users to clearly view the format, parameter names and example values ​​of the input data. The input data area 805 can be used for users to enter or modify data parameters required for debugging. This area supports data formats such as JSON. The execute debug control 806 can be used to trigger a debug call request after the user confirms the input data, convert the input data into a request format that matches the MCP Server through the mapping rules, and send it to the target server to obtain the debug results. The debug result display area 807 can be used to display the debug output data returned by the target server. The user can intuitively view the results after parsing through the output mapping rules to verify whether the service resources are running as expected. The copy result control 808 can be used to support users to copy the debug results with one click, which is convenient for subsequent archiving, comparison or reuse in other systems, improving debugging efficiency and operability. The view call link control 809 can be used to display the link information of the debug call process, such as the request sending path, parameter mapping process, response receiving path, etc., to help users troubleshoot problems and verify the integrity and correctness of requests and responses.

[0121] S706: Generate sample input data based on the input mapping rule, and display the sample input data on the debugging page.

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

[0123] 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 through the input mapping rule, and a debugging call request is initiated to the target server, so that the target server generates debugging output data based on the debugging call request in the running environment.

[0124] In one embodiment, upon detecting a user 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 caller-side field names to the target field names required by the service resource, performing data type conversion and formatting on the input values, filling missing but required parameters with default values ​​or renaming the fields, generating derived fields based on expressions or scripts in the rules, and verifying the data format and value range. Subsequently, based on the protocol requirements of the target service, the mapped data is assembled into a request format that matches the MCP server. For example, in HTTP scenarios, a standard message containing the method type, message header, and message body is generated; in RPC scenarios, an interface method call sequence and parameter signature are generated; and in TPP scenarios, 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, generates a link tracking identifier for debugging and tracing, and finally sends the request to the target server's runtime environment via the corresponding transmission channel or software development kit.

[0125] S708: Obtain the debugging output data returned by the target server, and parse and process the debugging output data according to the output mapping rule to generate a debugging result.

[0126] In one embodiment, when 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. This includes mapping the original output fields to standardized field names, performing necessary data type conversions, filtering out content to be displayed, and filtering out irrelevant or sensitive information. The processed data is then encapsulated into a unified format, generating the final debug results and displaying them on the debug page, allowing users to intuitively verify whether the service resource output meets expectations.

[0127] S709: When the debugging result indicates 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 constructs an MCPServer 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 request of the target model to execute the corresponding resource service task.

[0128] For details, please refer to the above S206, which will not be repeated here.

[0129] S710: Receive node metadata sent by the target server and register the node metadata in the MCP Server management platform. The node metadata is used to identify the MCP Server node and provide a call route for the MCP Server node.

[0130] For details, please refer to the above S207, which will not be repeated here.

[0131] In another embodiment, when the debugging result indicates that the service resource does not meet the preset operating conditions, the method further includes: determining an abnormal operating configuration item corresponding to the MCP Server based on the debugging result; displaying the abnormal operating configuration item on an abnormal configuration modification page; obtaining first modification information determined for the abnormal operating configuration item; updating the deployment parameters based on the first modification information to generate updated deployment parameters; and returning 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 operating environment corresponding to the MCP Server based on the deployment parameters.

[0132] Operational configuration anomalies can be configuration issues that are discovered during service resource debugging and are inconsistent with preset operating conditions. These anomalies may include, but are not limited to, inconsistent input / output data types, missing or incorrect interface authentication methods, unreasonable QPS limit threshold settings, and RPC protocol incompatibility. These anomalies identify specific configuration defects that prevent service resources from operating as expected.

[0133] Optionally, the abnormal configuration modification page can be an interactive interface provided by the MCP Server management platform. When an abnormal operation configuration item is detected, the content of the abnormal item will be intuitively displayed on the page, and a corresponding modification entry will be provided. The user can view the cause of the abnormality on this page and modify the configuration parameters to ensure that the operating environment meets the 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 abnormal operation configuration item. The first modification information may include the modified value of the configuration parameter, the replaced authentication method, the adjusted current limiting threshold, the modified input-output mapping rule, etc., and then the updated deployment parameters can be generated based on the first modification information.

[0134] In one embodiment, the deployment parameters are updated based on the first modification information to generate updated deployment parameters. This can be: when the modification information involves input mapping rules, the field mapping configuration is updated; when it involves output mapping rules, the result parsing rules are updated; when it involves interface description information, the interface parameters or authentication methods are updated; when it involves performance or operating conditions, the call frequency, timeout policy and other parameters are updated, so that the updated deployment parameters can accurately reflect the user's modification content.

[0135] In this embodiment, after a debugging failure, the system automatically identifies operational configuration anomalies and visually displays the problem points on the abnormal configuration modification page, enabling users to quickly locate and correct errors. Furthermore, by automatically generating updated deployment parameters based on the first modification information entered by the user, this achieves a closed-loop fix for configuration issues. This process not only reduces the cost of manual troubleshooting and repeated deployment by users, but also enables service resources to be restored to a state that meets preset operating conditions in a shorter time, significantly improving the efficiency and reliability of MCP Server deployment and debugging.

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

[0137] The modification request may refer to an instruction / event for triggering a change to existing service resource configuration information, and may be initiated by a user or a system to access a service resource modification page.

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

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

[0140] Optionally, the second modification information refers to the modification content entered or confirmed by the user through the service resource modification page. The second modification information includes, but is not limited to: adjustments to input / output data mapping rules, such as modifying field names or data types; updates to interface specifications, such as adding new parameter specifications or modifying call methods; updates to permission-related parameters, such as changing the authentication method or modifying the permission code; and adjustments to operating parameters, such as call frequency limits and timeout thresholds.

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

[0142] In other words, the second modification information is a collection of change operations made by the user on the current configuration of the service resource. 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.

[0143] S714: 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 operating environment corresponding to the MCP Server based on the deployment parameters.

[0144] In the embodiment of the present application, by introducing service resource modification requests and service resource modification pages, users can conveniently complete adjustments to service resource configurations in a centralized, visual interactive interface without directly operating the underlying configuration files, thereby reducing the risk of human configuration errors; by collecting second modification information and generating updated deployment parameters based on it, dynamic updates and rapid iterations of the operating environment can be achieved, thereby improving configuration maintenance efficiency and system flexibility.

[0145] 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, 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 call requests from the target model to execute corresponding resource service tasks. Furthermore, the node metadata sent by the target server is received and registered on the MCP Server management platform. The node metadata is used to identify the MCP Server node and provide a call route for the MCP Server node. This completes a complete closed-loop process from service resource configuration adjustment, dynamic update of the operating environment, to debugging verification and service node construction.

[0146] In this embodiment of the present application, upon receiving a modification request, the service resource modification page is accessed to collect the second modification information, and deployment parameters are incrementally updated accordingly (a new version is generated and a history is retained to support rollback / comparison). The updated deployment parameters are then distributed to the target server, completing the hot update / cancellation deployment of the operating environment. The system automatically triggers regression debugging and generates debugging results. If the preset operating conditions are not met, the system automatically extracts abnormal operating configuration items based on the results and backfills them to the modification page, driving the next round of modification, update, and debugging until the requirements are met. If the preset operating conditions are met, an MCP Server node is constructed in a pending call state, and node metadata is generated and registered with the management platform, enabling the call route to take effect immediately. This cyclical mechanism transforms configuration changes, environment updates, effect verification, problem location, further changes, and solidifies them 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.

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

[0148] Specifically, node metadata contains unique identification information for the MCP Server node and call routing information. During the execution of the target model on the terminal device, when it detects the need to call an external service resource, it determines the call route based on the node metadata returned by the MCP Server management platform. During the terminal device's service agent configuration phase, the terminal user can select the target MCP Server to enable (such as a map MCP Server or a general knowledge details MCP Server) and further select specific service resources under the target MCP Server (such as a knowledge base document list tool or a store basic information acquisition tool). After configuration is complete, when the target model running on the terminal device generates a call request, it can match the input context to the registered node metadata, identify the corresponding MCP Server node, and direct the call request to the target MCP Server runtime environment based on the call routing information in the node metadata. Once the route is reached, the MCP Server triggers the corresponding service resource execution logic (such as querying the knowledge base, calling a map interface, or retrieving store information). The service resource execution results are then returned to the terminal device through the MCP Server, which injects the results into the target model's inference context to generate the final output response.

[0149] It is understandable that the above-mentioned terminal users can be individual users, such as ordinary users who use a certain intelligent application (map query, knowledge quiz); 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; they can also be system callers, such as customer service robots, recommendation systems, search engines, etc., which are target models running on terminal devices.

[0150] In this embodiment of the application, terminal devices do not need to directly perceive the physical deployment location or underlying configuration of service resources such as tools. Instead, they can rely solely on 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 based on the configuration, effectively improving the efficiency of model reasoning.

[0151] It should be understood that, although the various steps in the flowcharts involved in the various embodiments described above are displayed in sequence according to the instructions of the arrows, these steps are not necessarily executed in sequence in the order indicated by the arrows. Unless otherwise specified herein, there is no strict order restriction on the execution of these steps, and these steps can be executed in other orders. Moreover, at least a portion of the steps in the flowcharts involved in the various embodiments described above can include multiple steps or multiple stages, and these steps or stages are not necessarily executed and completed at the same time, but can be executed at different times, and the execution order of these steps or stages is not necessarily to be carried out in sequence, but can be executed in turn or alternately with other steps or at least a portion of steps or stages in other steps.

[0152] Based on the inventive concept of the above service node deployment method, Figure 9 As shown, the embodiment of the present application further provides a first service node deployment device 900 for implementing the above-mentioned service node deployment method applied to the platform client device. The first service node deployment device 900 includes: 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; A first acquisition module 902 is configured to acquire, through the MCP Server configuration page, MCP Server configuration information determined by the user and resource configuration information of service resources associated with the MCP Server configuration information, wherein the resource configuration information includes input mapping rules, output mapping rules, and interface description information; A generation module 903 is configured to generate deployment parameters for running the MCP Server and service resources based on the MCP Server configuration information and resource configuration information; A first sending module 904 is configured to send the deployment parameters to the target server, so that the target server deploys the operating environment corresponding to the MCP Server based on the deployment parameters; The debugging module 905 is used to respond to the debugging instruction for the service resource, perform debugging operations based on the operating environment, and obtain debugging results; The second sending module 906 is configured to send a service node construction request to the target server if 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 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 the service resource and respond to the call request of the target model to execute the corresponding resource service task. The registration module 907 is used to receive the node metadata sent by the target server and register the node metadata in the MCP Server management platform. The node metadata is used to identify the MCP Server node and provide a call route for the MCP Server node.

[0153] In one embodiment, the first acquisition module 902 is specifically configured to: acquire MCP server initial information through an MCP server configuration page; perform a validity check on the MCP server initial information to 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 service resources associated with the MCP server configuration information.

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

[0155] In one embodiment, the first acquisition module 902 is specifically used to: 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.

[0156] In one embodiment, the generation module 903 is specifically configured to: perform structured parsing of the MCP Server configuration information to obtain MCP Server operating parameter information; perform rule-based parsing of the resource configuration information to generate interface configuration information compatible with the MCP Server operating environment; and perform correlation mapping between the MCP Server operating parameter information and the interface configuration information to generate deployment parameters for operating the MCP Server and serving resources.

[0157] 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 confirmation instruction for the sample input data, convert the sample input data into a request format that matches the MCPServer using the input mapping rules, and initiate a debugging call request to a target server, so that the target server generates debugging output data based on the debugging call request in the running 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 a debugging result.

[0158] In one embodiment, the first service node deployment apparatus 900 further includes: a determination module configured to determine, based on the debugging result, an abnormal operation configuration item corresponding to the MCP Server when the debugging result indicates that the service resource does not meet the preset operation conditions; a second display module configured to display the abnormal operation configuration item through an abnormal configuration modification page; a second acquisition module configured to obtain first modification information determined for the abnormal operation configuration 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 executing the 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.

[0159] In one embodiment, the first service node deployment apparatus 900 further includes: a third display module, configured to display a service resource modification page in response to a modification request for a service resource; a third acquisition module, configured to obtain 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 executing the 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.

[0160] Based on the inventive concept of the above service node deployment method, Figure 10As shown, the embodiment of the present application further provides a second service node deployment device 1000 for implementing the above-mentioned service node deployment method applied to the target server. The second service node deployment device 1000 includes: Receiving module 1001 is configured to receive deployment parameters sent by a platform client device. The deployment parameters are deployment parameters generated by the platform client device based on MCP server configuration information and resource configuration information for running the MCP server and 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. A deployment module 1002 is configured to deploy an operating environment corresponding to the MCP Server based on deployment parameters; Construction module 1003 is configured to receive a service node construction request sent by a platform client device, construct an MCP Server 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. The service node construction request is sent by the platform client device when a debugging result indicates that the service resource meets preset operating conditions. The debugging result is the result of the platform client device performing debugging operations based on the operating environment in response to the debugging instruction for the service resource. The third sending module 1004 is configured 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 a call route for the MCP Server node.

[0161] Each module in the first service node deployment apparatus 900 and the second service node deployment apparatus 1000 may be implemented in whole or in part through software, hardware, or a combination thereof. Each module may be embedded in or independent of a processor in a computer device in the form of hardware, or may be stored in a memory in the computer device in the form of software, so that the processor can call and execute the corresponding operations of each module.

[0162] The embodiment of the present application also provides an electronic device, which may be a server, and its internal structure diagram may be as shown in FIG. Figure 11 See Figure 11The electronic device includes a processor, a memory, an input / output interface (I / O) and a communication interface. The processor, memory and input / output interface are connected via a system bus, and the communication interface is connected to the system bus via the input / output interface. The processor of the electronic device is used to provide computing and control capabilities. The memory of the electronic device includes a non-volatile storage medium and an internal memory. The non-volatile storage medium stores an operating system, a computer program and a database. The internal memory provides an environment for the operation of the operating system and computer program in the non-volatile storage medium. The database of the electronic device is used to store MCP server configuration information and resource configuration information of service resources associated with the MCP server configuration information. The input / output interface of the electronic device is used to exchange information between the processor and an external device. The communication interface of the electronic device is used to communicate with an external terminal via a network connection. The processor of the electronic device executes a computer program to implement a service node deployment method.

[0163] It is worth noting that the electronic device can also be a terminal, and its internal structure diagram can be as follows: Figure 12 See Figure 12 The electronic device includes a processor, memory, an input / output interface, a communication interface, a display unit, and an 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 connected to the system bus via the input / output interface. The processor of the electronic device provides computing and control capabilities. The memory of the electronic device includes a non-volatile storage medium and internal memory. The non-volatile storage medium stores an operating system and computer programs. The internal memory provides an environment for the operating system and computer programs stored in the non-volatile storage medium. The input / output interface of the electronic device is used to exchange information between the processor and external devices. The communication interface of the electronic device is used to communicate with external terminals via wired or wireless means, where the wireless means may be implemented via Wi-Fi, a mobile cellular network, NFC (near-field communication), or other technologies. When executed by the processor, the computer program implements a service node deployment method. The display unit of the electronic device is used to produce a visually visible image and may be a display screen, a projection device, or a virtual reality imaging device. The display screen can be a liquid crystal display screen or an electronic ink display screen, and the input device of the electronic device can be a touch layer covering the display screen, or a button, trackball or touchpad set on the electronic device casing, or an external keyboard, touchpad or mouse.

[0164] The present application also provides a computer storage medium having instructions stored therein that, when executed on a computer or processor, cause the computer or processor to perform one or more steps of the above-described embodiments. If the components of the electronic device described above are implemented as software functional units and sold or used as independent products, they may be stored in the computer-readable storage medium described above.

[0165] In the above embodiments, all or part of the embodiments may be implemented using software, hardware, firmware, or any combination thereof. When implemented using software, all or part of the embodiments may be implemented in the form of 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 the present application are generated. The computer may be a general-purpose computer, a special-purpose computer, a computer network, or other programmable device. The computer instructions may be stored in a computer storage medium or transmitted via the computer storage medium. The computer instructions may be transmitted from one website, computer, server, or data center to another website, computer, server, or data center via wired (e.g., coaxial cable, optical fiber, digital subscriber line (DSL)) or wireless (e.g., infrared, wireless, microwave, etc.) means. The computer storage medium may be any available medium accessible by a computer or a data storage device such as a server or data center that integrates one or more available media. The available medium may be a magnetic medium (eg, a floppy disk, a hard disk, a magnetic tape), an optical medium (eg, a digital versatile disc (DVD)), or a semiconductor medium (eg, a solid state drive (SSD)).

[0166] Those skilled in the art will appreciate that all or part of the processes in the above-described method embodiments can be implemented by instructing the relevant hardware through a computer program. The program can be stored in a computer-readable storage medium. When executed, the program can include the processes of the above-described method embodiments. The aforementioned storage medium includes various media capable of storing program code, such as ROM, RAM, magnetic disks, or optical disks. The technical features of this embodiment and the implementation scheme can be combined in any manner unless they conflict.

[0167] The embodiments described above are merely preferred embodiments of the present application and are not intended to limit the scope of the present application. Without departing from the design spirit of the present application, various modifications and improvements made to the technical solutions of the present application by ordinary technicians in this field should fall within the scope of protection determined by the claims.

[0168] It should be noted that the technical solutions of this application can be applied to transactions and delivery services on instant e-commerce platforms, such as Taobao Flash Sales, Taoxianda, and Ele.me takeout and retail. The information and data involved in the embodiments of this application are all authorized by the user or fully authorized by all parties, and the collection, use, and processing of relevant 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 are all obtained with full authorization.

[0169] The foregoing description describes specific embodiments of the present application. Other embodiments are within the scope of the appended claims. In some cases, the actions or steps recited in the claims can be performed in an order different from that described in the embodiments and still achieve the desired results. Furthermore, the processes depicted in the accompanying drawings do not necessarily require the specific order shown or the sequential order to achieve the desired results. In certain embodiments, multitasking and parallel processing are also possible or may be advantageous.

Claims

1. A service node deployment method, characterized in that: Applied to a platform client device, the method includes: Display the MCP Server configuration page through the MCP Server management platform running on the platform client device; Obtaining, through the MCP Server configuration page, MCP Server configuration information determined by the user and resource configuration information of service resources associated with the MCP Server configuration information, wherein the resource configuration information includes input mapping rules, output mapping rules, and interface description information; Generating deployment parameters for running the MCP Server and the service resources based on the MCP Server configuration information and the resource configuration information; Sending the deployment parameters to a target server, so that the target server deploys the operating environment corresponding to the MCP Server based on the deployment parameters; In response to a debugging instruction for the service resource, performing a debugging operation based on the operating environment to obtain a debugging result; If the debugging result indicates 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 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 host the service resource and respond to the call request of the target model to perform the corresponding resource service task; Receive node metadata sent by the target server and register the node metadata in the MCP Server management platform. The node metadata is used to identify the MCP Server node and provide a call route for the MCP Server node.

2. The method according to claim 1, wherein The acquiring, through the MCP Server configuration page, the MCP Server configuration information determined by the user and resource configuration information of service resources associated with the MCP Server configuration information includes: Obtain the initial information of the MCP Server through the MCP Server configuration page; Performing a validity check on the MCP Server initial information to obtain a verification result; If the verification result indicates that the MCP Server initial information has passed verification, generating MCP Server configuration information in the MCP Server management platform based on the MCP Server initial information; In response to the 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 acquired.

3. The method according to claim 2, wherein The acquiring, in response to the service resource registration instruction for the MCP Server configuration information, resource configuration information of the service resources associated with the MCP Server configuration information includes: generating, in response to a service resource registration instruction for the MCP Server configuration information, a service resource registration context environment, wherein the service resource registration context environment is used to define interaction constraint parameters between the service resource and the MCP Server configuration information; In 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; Acquiring the input mapping rule determined by the user through the input mapping rule editing component, acquiring the output mapping rule determined by the user through the output mapping rule editing component, and acquiring interface description information through the interface description information entry component; The input mapping rule, the output mapping rule, and the interface description information are integrated to obtain resource configuration information of the service resources associated with the MCP Server configuration information.

4. The method according to claim 3, wherein The step of loading the input mapping rule editing component, the output mapping rule editing component, and the interface description information entry component corresponding to the service resource in the service resource registration context environment includes: Obtaining the resource type of the service resource; Determine a target configuration template identifier based on the resource type; Acquire a resource configuration interface template that matches the service resource according to the target configuration template identifier; The resource configuration interface template file is rendered as 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 according to claim 2, wherein The generating, based on the MCP Server configuration information and the resource configuration information, deployment parameters for running the MCP Server and the service resources includes: Performing structured parsing on the MCP Server configuration information to obtain MCP Server operating parameter information; Performing regularized parsing processing on the resource configuration information to generate interface configuration information compatible with the operating environment of the MCP Server; An association mapping process is performed on the MCP Server operating parameter information and the interface configuration information to generate deployment parameters for operating the MCP Server and the service resources.

6. The method according to claim 1, wherein The step of performing a debugging operation based on the operating environment in response to the debugging instruction for the service resource to obtain a debugging result includes: In response to a debugging instruction for the service resource, displaying a debugging page; Generating sample input data based on the input mapping rule, and displaying the sample input data on the debugging page; After detecting a confirmation instruction from the user for the sample input data, converting the sample input data into a request format matching the MCP Server using the input mapping rule, and initiating a debug call request to the target server, so that the target server generates debug output data based on the debug call request in the running environment; The debugging output data returned by the target server is acquired, and the debugging output data is parsed and processed according to the output mapping rule to generate a debugging result.

7. The method according to claim 1, wherein The method further comprises: If the debugging result indicates that the service resource does not meet the preset operating condition, determining an abnormal operation configuration item corresponding to the MCP Server based on the debugging result; Display the abnormal configuration items through the abnormal configuration modification page; Acquire first modification information determined for the abnormal running configuration item; updating the deployment parameters 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 is returned to execute, so that the target server deploys the operating environment corresponding to the MCP Server based on the deployment parameters.

8. The method according to claim 1, wherein After registering the node metadata on the MCPServer management platform, the method further includes: In response to a modification request for the service resource, displaying a service resource modification page; Acquiring second modification information through the service resource modification page; updating the deployment parameters 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 is returned to execute, so that the target server deploys the operating environment corresponding to the MCP Server based on the deployment parameters.

9. A service node deployment method, characterized in that: Applied to a target server, the method includes: Receive deployment parameters sent by a platform client device, where the deployment parameters are deployment parameters generated by the platform client device based on MCP Server configuration information and resource configuration information for running the MCP Server and 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 an MCP Server configuration page, which is displayed by the platform client device through an MCP Server management platform running on the platform client device. Deploy the operating environment corresponding to the MCP Server based on the deployment parameters; receiving a service node construction request sent by the platform client device, and constructing an MCP Server node in a pending call state based on the service node construction request, and generating node metadata for the MCP Server node. The MCP Server node is used to host the service resource and respond to the call request of the target model to perform the corresponding resource service task. The service node construction request is a request sent by the platform client device when a debugging result indicates that the service resource meets a preset operating condition. The debugging result is a result obtained by the platform client device performing a debugging operation based on the operating environment in response to a debugging instruction for the service resource; 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 run by the platform client device. The node metadata is used to identify the MCP Server node and provide a call route for the MCP Server node.

10. A service node deployment system, characterized in that: The service node deployment system includes: a platform client device and a target server; wherein, The platform client device is configured to display an MCP Server configuration page through an MCP Server management platform running on the platform client device; obtain, through the MCP Server configuration page, MCP Server configuration information determined by a user and resource configuration information of service resources associated with the MCP Server configuration information, the resource configuration information including 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 a target server; The target server is configured to receive the deployment parameters sent by the platform client device and deploy the operating environment corresponding to the MCP Server based on the deployment parameters; and receive the service node construction request sent by the platform client device, and construct an MCP Server node in a pending call state based on the service node construction request, generate node metadata for the MCP Server node, and send the node metadata to the platform client device. The MCP Server node is configured to host the service resources and respond to the target model's call request to execute the corresponding resource service task. The platform client device is further configured to receive node metadata sent by the target server and register the node metadata in the MCP Server management platform. The node metadata is used to identify the MCP Server node and provide a call route for the MCP Server node.

11. A service node deployment device, characterized in that: Applied to a platform client device, the apparatus comprises: The first display module is used to display the MCP Server configuration page through the MCP Server management platform running on the platform client device; A first acquisition module is configured to acquire, through the MCP Server configuration page, MCP Server configuration information determined by a user and resource configuration information of service resources associated with the MCP Server configuration information, wherein the resource configuration information includes input mapping rules, output mapping rules, and interface description information; A generation module, configured 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; A first sending module is configured to send the deployment parameters to a target server, so that the target server deploys an operating environment corresponding to the MCP Server based on the deployment parameters; a debugging module, configured to respond to a debugging instruction for the service resource, perform a debugging operation based on the operating environment, and obtain a debugging result; a second sending module, configured to send a service node construction request to the target server if 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 pending call state based on the service node construction request and generates node metadata for the MCP Server node. The MCP Server node is configured to host the service resource and respond to the call request of the target model to execute the corresponding resource service task; A registration module is configured to receive node metadata sent by the target server and register the node metadata in the MCP Server management platform. The node metadata is used to identify the MCP Server node and provide a call route for the MCP Server node.

12. A service node deployment device, characterized in that: Applied to a target server, the device comprises: a receiving module, configured to receive deployment parameters sent by a platform client device, wherein the deployment parameters are deployment parameters generated by the platform client device based on MCP Server configuration information and resource configuration information for running the MCP Server and 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 via an MCP Server configuration page; and the MCP Server configuration page is a page displayed by the platform client device via an MCP Server management platform running on the platform client device. A deployment module, configured to deploy an operating environment corresponding to the MCP Server based on the deployment parameters; a construction module, configured to receive a service node construction request sent by the platform client device, and construct an MCP Server 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 configured to host 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 a debugging result indicates that the service resource meets preset operating conditions. The debugging result is a result of the platform client device performing a debugging operation based on the operating environment in response to a debugging instruction for the service resource. A third sending module is configured 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 run by the platform client device. The node metadata is used to identify the MCP Server node and provide a call route 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 when the processor executes the computer program, the method steps of any one of claims 1 to 9 are implemented.

14. A computer storage medium, characterized in that The computer storage medium stores a plurality of instructions, which are suitable for being loaded by a processor and executing the method steps according to any one of claims 1 to 9.

Images