All Products
Search

This Product

    API Gateway:Synchronize Nacos MCP services

    Document Center

    API Gateway:Synchronize Nacos MCP services

    Last Updated:Dec 03, 2025

    This topic describes how to synchronize Nacos service information to AI Gateway through the Model Context Protocol (MCP). This synchronization extends service registration, discovery, and governance capabilities to enhance unified management efficiency across multi-platform environments.

    Prerequisites

    • You are using MCP services registered in MSE Nacos Enterprise Edition 3.0 or later.

    • The gateway engine is upgraded to v2.1.6 or later.

      1. On the Instance page of the AI Gateway console, select the region where your instance is located.

      2. Click the target instance name to go to the instance details page. In the Running Information section of the Basic Information tab, check the Engine Version.

      3. (Optional) If it is not the latest version, click Upgrade.

      The gateway upgrade process takes approximately 5 to 10 minutes. Short-lived connections remain unaffected, while long-lived connections may require re-establishment. You can execute the upgrade during off-peak hours.

    Procedure

    The synchronization operations for HTTP-converted MCP services and standard MCP services created in Nacos Enterprise Edition are identical:

    1. On the Instance page of the AI Gateway console, select the region where your instance is located.

    2. Click the target instance name to go to the instance details page. In the navigation pane on the left, click MCP Management.

    3. Click Sync Nacos MCP Services and select the MSE Nacos service you created as the Service Source.

    4. Select the Nacos Namespace where the MCP service is located, and select the domain name used to access the MCP service. You can select multiple domain names.

    5. When selecting the Nacos MCP Service to be synchronized, you can filter backend services by Protocol Type:

      • mcp-sse: The backend is a Server-Sent Events (SSE) type MCP server.

      • mcp-streamable: The backend is a streamable type MCP server.

      • http: The backend is an HTTP service converted to MCP type on Nacos.

    6. After synchronization, the MCP service card displays the direct proxy or HTTP-to-MCP identifier along with the Nacos managed identifier.