Scenarios
When you need to batch access services from existing registries or domain name services to the AI Gateway, you can configure service sources to achieve automatic synchronization and unified management of the services. Service sources are categorized into three types:
MCP Registry: It connects to registries (such as TSF Nacos), synchronizes native MCP Servers, and enables automatic discovery of MCP Tools.
General Registry: It connects to registries (such as TSF Nacos 2.x and TSF PolarisMesh), automatically synchronizes backend service addresses and metadata, and is suitable for batch access of backend services to the AI Gateway.
Private DNS: It connects to Tencent Cloud Private DNS to perform domain name resolution. This is suitable for service scenarios accessed via domain names.
Prerequisites
The Tencent Cloud AI Gateway service has been activated.
The AI Gateway instance has been created.
The registry/TKE instance and the gateway instance are in the same VPC network.
Operation Steps
Step 1: Go to the Service Source Configuration Page
2. Click the ID/Name of the target instance to go to its details page and access the target gateway instance.
3. In the left sidebar, choose Service Management > Service Source.
4. Click the New button.
Step 2: Select a Service Source Type
The system provides three types of service sources. Please select one based on your actual scenario.
Scenario 1: Configuring the MCP Registry (Synchronizing the Native MCP Server)
Applicable Scenario: Your MCP Server has been registered to TSF Nacos, and the AI Gateway needs to automatically discover and synchronize the Tool.
Parameter Configuration:
|
Source Type | Yes | Select MCP Registry |
Source Product | Yes | TSF Nacos (Recommended) Directly connect to services registered on TSF Nacos 3.x. |
Service source name | Yes | A custom name. Up to 60 characters. Supports uppercase and lowercase letters in Chinese and English, digits, and the - and _ symbols. Cannot start or end with a separator. Must be unique within the same gateway instance. |
Instance selection | Yes | Select an existing Nacos instance (only instances located in the same VPC as the gateway instance are displayed). |
Username. | Yes | Nacos authentication username |
Password | Yes | Nacos authentication password. Supports uppercase and lowercase letters, digits, spaces, and common symbols. |
Description | No | Description of the service source. Up to 200 characters. |
Directions:
1. In the Create Service Source dialog box, select MCP Registry as the source type.
2. Select TSF Nacos as the source product.
3. Enter a service source name (for example, mcp-nacos-prod).
4. Select a Nacos instance from the drop-down list.
5. Enter the authentication username and password.
6. (Optional) Enter a description.
7. Click OK to complete the creation.
Synchronization Result:
The AI Gateway will automatically synchronize the MCP Server services registered in Nacos.
The Tool definitions of the MCP Server will be automatically discovered and displayed in the console.
When service instances change, the gateway automatically detects and updates.
Scenario 2: Configuring a Common Registry (Batch Access to Backend Services)
Applicable Scenario: Use this when your backend services are registered with TSF Nacos 2.x or TSF PolarisMesh, and you need the AI Gateway to automatically discover and access these services.
Parameter Configuration:
|
Source Type | Yes | Select Common Registry |
Source Product | Yes | TSF Nacos (Recommended): Directly connect to services registered on TSF Nacos 2.x. TSF PolarisMesh: Directly connect to services registered on TSF PolarisMesh. |
Service source name | Yes | A custom name. Up to 60 characters. Supports uppercase and lowercase letters in Chinese and English, digits, and the - and _ symbols. Cannot start or end with a separator. Must be unique within the same gateway instance. |
Instance selection | Yes | Select an existing Nacos / PolarisMesh instance (only instances located in the same VPC as the gateway instance are displayed). |
Username. | Yes | Registry authentication username. Supports uppercase and lowercase letters, digits, spaces, and common symbols. |
Password | Yes | Registry authentication password. Supports uppercase and lowercase letters, digits, spaces, and common symbols. |
Description | No | Description of the service source. Up to 200 characters. |
Directions:
1. In the Create Service Source dialog box, select General Registry as the source type.
2. Select TSF Nacos (Recommended) or TSF PolarisMesh as the source product.
3. Enter a service source name (for example, nacos-prod or polaris-prod).
4. Select the corresponding registry instance from the drop-down list.
5. Enter the authentication username and password.
6. (Optional) Enter a description.
7. Click OK to complete the creation.
Synchronization Result:
The AI Gateway will automatically synchronize the backend services registered in the registry, including metadata such as service addresses and ports.
When service instances change, the gateway automatically detects and updates them, eliminating the need to manually maintain the service list.
Synchronized services can be viewed in the Service Management > Services list and can be directly used as the backend source for creating model services.
Scenario 3: Configuring Container Services (Batch Access to TKE Services)
Use Case: Connect to Tencent Cloud TKE clusters to automatically discover Services.
Parameter Configuration
|
Source Product | Yes | TKE standard cluster Directly connect to services deployed in TKE standard clusters. |
Service source name | Yes | 2-60 characters. Supports uppercase and lowercase letters in Chinese and English, digits, and separators ("-", "_"). Cannot start with a digit or separator. Cannot end with a separator. |
Select cluster. | Yes | Only clusters in the same VPC as the current AI gateway can be selected. |
Description | No | Description of the service source. Up to 200 characters. |
Scenario 4: Configuring Private DNS (Accessing Services via Domain Name Resolution)
Applicable Scenario: Your backend service is accessed via domain names, requiring the use of Tencent Cloud Private DNS for domain name resolution.
Parameter Configuration:
|
Source Type | Yes | Select Private DNS |
Source Product | Yes | Tencent Cloud Private DNS Performs domain name resolution using Private DNS. |
Description | No | Description of the service source. Up to 200 characters. |
Directions:
1. In the Create Service Source dialog, select Private DNS as the source type.
2. Select Tencent Cloud Private DNS as the source product.
3. (Optional) Enter a description.
4. Click OK to complete the creation.
Configuration Description:
After configuration is complete, you can select this source when creating a service.
The backend address field supports domain names (for example, server.internal.example.com).
The gateway resolves domain names via Private DNS and forwards the requests.
Step 3: Save the Configuration
1. Confirm that all parameters are entered correctly.
2. Click the OK button to complete the creation.
3. The system automatically redirects to the Service Source List page.
Verifying the Result
After configuration is complete, you can verify it using the following methods:
On the Service Source List page, view the newly created source record.
MCP Registry Type: When creating a new MCP service, you can select this source from the Service Source drop-down list.
Common Registry Type: When creating a new service, you can select this source from the Service Source drop-down list. The synchronized registry service will be available as an optional backend.
Private DNS Type: When creating a new service, select this source. You can then enter a domain name for the backend address.
On the MCP Management > MCP Service page, you can select this source from the Service Source drop-down list when creating a new service.
FAQs
Q1: Why Can't I See My Nacos Instance When Selecting an Instance?
A: Please check the following points:
1. Check whether the Nacos instance and the AI gateway instance are in the same VPC network.
2. Check whether your account has permission to view Nacos instances.
3. Check whether the Nacos instance is in a running state.
Q2: Can One Service Source Be Associated with Multiple MCP Services?
A: Yes. A single service source can be associated with multiple MCP services. This applies to the following scenarios:
Multiple MCP Servers are registered in the same Nacos instance.
Multiple backend services are registered in the same Nacos / PolarisMesh instance.
A single Private DNS can resolve multiple different domain names.
Q3: How to Troubleshoot Synchronization Failures Caused by Incorrect Service Source Configuration?
A: Please troubleshoot by following these steps:
1. Go to the Service Source details page and view the error information.
2. MCP Registry: Check whether the username/password is correct and whether the Nacos instance is accessible.
3. Private DNS: Check whether the domain name resolution records are correctly configured.
4. View the AI Gateway logs to obtain detailed error information.