Remote MCP gateway (virtual runtime)

Step 1: Install Solo Enterprise for agentgateway

Install Solo Enterprise for agentgateway and the Kubernetes Gateway API CRDs in your cluster.

1. Set the Solo Enterprise for agentgateway version.

   export AGENTGATEWAY_VERSION=v2026.9.0

2. Install the standard Gateway API CRDs, which include the Gateway, HTTPRoute, and related resources.

   kubectl apply -f https://github.com/kubernetes-sigs/gateway-api/releases/download/v1.5.0/standard-install.yaml

3. Install the Solo Enterprise for agentgateway CRDs.

   helm upgrade -i enterprise-agentgateway-crds \
     oci://us-docker.pkg.dev/solo-public/enterprise-agentgateway/charts/enterprise-agentgateway-crds \
     --create-namespace \
     --namespace agentgateway-system \
     --version "${AGENTGATEWAY_VERSION}"

4. Install the Solo Enterprise for agentgateway controller and data plane.

   helm upgrade -i enterprise-agentgateway \
     oci://us-docker.pkg.dev/solo-public/enterprise-agentgateway/charts/enterprise-agentgateway \
     -n agentgateway-system \
     --version "${AGENTGATEWAY_VERSION}" \
     --set-string licensing.licenseKey="${AGENTGATEWAY_LICENSE_KEY}"

5. Verify that the control plane pod is running.

   kubectl get pods -n agentgateway-system

   Example output:

   NAME                                                     READY   STATUS    RESTARTS   AGE
   enterprise-agentgateway-controller-7d9f8b6d4c-xvpzk     1/1     Running   0          45s
   

Step 2: Create the Gateway and parent HTTPRoute

Create the Gateway and parent HTTPRoute that the agentgateway proxy uses to accept MCP traffic. Both resources must carry the agentregistry.solo.io/runtime: mcp-gateway label so that the registry can discover them and populate the exposedAt URL on each Deployment.

1. Create the Gateway.

   kubectl apply -f - <<EOF
   apiVersion: gateway.networking.k8s.io/v1
   kind: Gateway
   metadata:
     name: agentgateway-proxy
     namespace: agentgateway-system
     labels:
       agentregistry.solo.io/runtime: mcp-gateway
   spec:
     gatewayClassName: enterprise-agentgateway
     listeners:
     - protocol: HTTP
       port: 80
       name: http
       allowedRoutes:
         namespaces:
           from: All
   EOF

   Note

   This example uses an HTTP listener for simplicity. Production deployments typically add an HTTPS listener with a TLS certificate.

2. Create the parent HTTPRoute that delegates traffic on the /registry path prefix to every child HTTPRoute that the registry creates in the agentregistry-system namespace.

   kubectl apply -f - <<EOF
   apiVersion: gateway.networking.k8s.io/v1
   kind: HTTPRoute
   metadata:
     name: agentregistry-delegate
     namespace: agentgateway-system
     labels:
       agentregistry.solo.io/runtime: mcp-gateway
   spec:
     parentRefs:
     - name: agentgateway-proxy
     rules:
     - matches:
       - path:
           type: PathPrefix
           value: /registry
       backendRefs:
       - group: gateway.networking.k8s.io
         kind: HTTPRoute
         name: "*"
         namespace: agentregistry-system
   EOF

3. Verify that the gateway proxy pod is running.

   kubectl get pods -n agentgateway-system | grep agentgateway-proxy

   Example output:

   agentgateway-proxy-64c4bf7c4c-gzfhj   1/1     Running   0          93s
   

Step 3: Register the virtual runtime

Create a Virtual runtime in Solo Enterprise for agentregistry. The name field must match the agentregistry.solo.io/runtime label value that you set on the Gateway and parent HTTPRoute in the previous step.

1. Create the runtime.

   arctl apply -f - <<EOF
   apiVersion: ar.dev/v1alpha1
   kind: Runtime
   metadata:
     name: mcp-gateway
   spec:
     type: Virtual
   EOF

   Example output:

   ✓ Runtime/mcp-gateway created
   

2. Verify that the runtime appears in the catalog.

   arctl get runtimes

   Example output:

   NAME                 TYPE
   kubernetes-default   Kubernetes
   local                Local
   mcp-gateway          Virtual
   virtual-default      Virtual