MemoryCore Service Port Configuration: Understanding Port 8420 in TencentDB Agent Memory

The TencentDB MemoryCore service exposes its TDAI gateway on TCP port 8420, configured consistently across both default and standalone deployment files.

The TencentCloud/TencentDB-Agent-Memory repository implements the MemoryCore service as the central memory engine gateway for TencentDB Agent Memory operations. Understanding the default MemoryCore service port configuration is essential for network setup, health monitoring, and API integration. According to the source code on the feat/server_team branch, the service binds to port 8420 across all deployment modes.

Default Port Configuration

The MemoryCore gateway initializes its HTTP listener on port 8420 through YAML-based configuration. This setting appears in the core service definition files that control the TDAI gateway behavior.

Primary Configuration File

In MemoryCore/tdai-gateway.yaml, the default standalone configuration explicitly sets the listener port. Lines 26-28 define the service binding:

# Located in MemoryCore/tdai-gateway.yaml (lines 26-28)

port: 8420

This file serves as the primary configuration for standard deployments of the MemoryCore gateway.

Standalone Deployment Variant

The repository also maintains MemoryCore/tdai-gateway.standalone.yaml for specialized deployment scenarios. Lines 12-14 of this file replicate the same port assignment:

# Located in MemoryCore/tdai-gateway.standalone.yaml (lines 12-14)

port: 8420

Both configuration files ensure consistent network behavior whether deploying the default or standalone variant of the service.

Verifying MemoryCore Service Connectivity

Once the service starts on port 8420, you can verify availability using the exposed health endpoint and API routes.

Health Check Endpoint

Validate that the MemoryCore service is accepting connections:

# Verify service health on port 8420

curl -s http://127.0.0.1:8420/health | jq

Core API Access

Interact with the memory engine through the gateway API:

# Example: List available agents via the core API

curl -s -X GET http://127.0.0.1:8420/v3/meta/agent/list \
     -H "Authorization: Bearer <your-token>" | jq

Configuration File Reference

The following table identifies the specific files governing the MemoryCore service port assignment:

File	Description	Lines
MemoryCore/tdai-gateway.yaml	Default gateway configuration defining the core listening port	26-28
MemoryCore/tdai-gateway.standalone.yaml	Standalone deployment variant with identical port configuration	12-14

Summary

• The MemoryCore service operates exclusively on TCP port 8420 according to the TencentDB-Agent-Memory source code.
• Configuration is hardcoded in MemoryCore/tdai-gateway.yaml and MemoryCore/tdai-gateway.standalone.yaml on the feat/server_team branch.
• Health monitoring is available via HTTP requests to 127.0.0.1:8420/health.
• All core API endpoints route through the same port, requiring proper firewall and network rules for external access.

Frequently Asked Questions

What port does the MemoryCore service use by default?

The MemoryCore service uses port 8420 as its default listening port for the TDAI gateway. This value is statically configured in both the default and standalone YAML configuration files within the MemoryCore/ directory.

Where is the MemoryCore service port configured?

The port is defined in two locations within the repository: MemoryCore/tdai-gateway.yaml at lines 26-28, and MemoryCore/tdai-gateway.standalone.yaml at lines 12-14. Both files specify port: 8420 under the gateway configuration section.

How do I verify the MemoryCore service is running on port 8420?

Send an HTTP GET request to the health endpoint at http://127.0.0.1:8420/health. A successful response indicates the service is active and listening on the configured port. You can also test API functionality by accessing endpoints such as /v3/meta/agent/list using the same port.

Can the MemoryCore service port be customized?

Yes, the port can be modified by editing the port: value in either MemoryCore/tdai-gateway.yaml or MemoryCore/tdai-gateway.standalone.yaml before deployment. The configuration file structure indicates this is a standard YAML parameter that accepts integer values for the gateway listener.

{
  "mcpServers": {
    "instagit": {
      "command": "npx",
      "args": ["-y", "instagit@latest"]
    }
  }
}