Documentation
Integrations
Agentgateway

Agentgateway

Use kgateway to manage agentgateway proxies for AI gateways in a Kubernetes environment.

About agentgateway

Agentgateway is an open source, highly available, highly scalable, and enterprise-grade data plane that provides AI connectivity for agents and tools in any environment. For more information, see the agentgateway docs.

Step 1: Set up kgateway

Enable the agentgateway feature in kgateway.

  1. Complete the Get started guide to create a Kubernetes cluster, deploy the Kubernetes Gateway API CRDs, and install kgateway. Note: Agentgateway is currently available in the v2.1.0-main development release.

  2. Upgrade your kgateway installation to enable agentgateway. For complete upgrade instructions, see the upgrade guide.

    helm upgrade -i --namespace kgateway-system --version v2.1.0-main kgateway oci://cr.kgateway.dev/kgateway-dev/charts/kgateway \
  --set agentGateway.enabled=true \
  --set agentGateway.enableAlphaAPIs=true

  3. Make sure that kgateway is running.

    kubectl get pods -n kgateway-system

    Example output:

    NAME                        READY   STATUS    RESTARTS   AGE
kgateway-5495d98459-46dpk   1/1     Running   0          19s

Step 2: Deploy an MCP server

Deploy a Model Context Protocol (MCP) server that you want agentgateway to proxy traffic to. The following example sets up a simple MCP server with one tool, fetch, that retrieves the content of a website URL that you pass in.

  1. Create the MCP server workload. Notice that the Service uses the appProtocol: kgateway.dev/mcp setting. This way, kgateway configures the agentgateway proxy to use MCP for the Backend that you create in the next step. For an A2A backend, you use the appProtocol: kgateway.dev/a2a setting.

    kubectl apply -f- <<EOF
apiVersion: apps/v1
kind: Deployment
metadata:
  name: mcp-website-fetcher
spec:
  selector:
    matchLabels:
      app: mcp-website-fetcher
  template:
    metadata:
      labels:
        app: mcp-website-fetcher
    spec:
      containers:
      - name: mcp-website-fetcher
        image: ghcr.io/peterj/mcp-website-fetcher:main
        imagePullPolicy: Always
---
apiVersion: v1
kind: Service
metadata:
  name: mcp-website-fetcher
  labels:
    app: mcp-website-fetcher
spec:
  selector:
    app: mcp-website-fetcher
  ports:
  - port: 80
    targetPort: 8000
    appProtocol: kgateway.dev/mcp
EOF

  2. Create a Backend that sets up the agentgateway target details for the MCP server.

    kubectl apply -f- <<EOF
apiVersion: gateway.kgateway.dev/v1alpha1
kind: Backend
metadata:
  name: mcp-backend
spec:
  type: MCP
  mcp:
    name: mcp-server
    targets:
    - static:
        name: mcp-target
        host: mcp-website-fetcher.default.svc.cluster.local
        port: 80
        protocol: SSE   
EOF

Step 3: Route with agentgateway

Route to the MCP server with agentgateway.

  1. Create a Gateway resource that uses the agentgateway GatewayClass. Kgateway automatically spins up an agentgateway proxy for you.

    kubectl apply -f- <<EOF
apiVersion: gateway.networking.k8s.io/v1
kind: Gateway
metadata:
  name: agent-gateway
spec:
  gatewayClassName: agentgateway
  listeners:
  - protocol: HTTP
    port: 80
    name: http
EOF

  2. Verify that the Gateway is created successfully. You can also review the external address that is assigned to the Gateway. Note that depending on your environment it might take a few minutes for the load balancer service to be assigned an external address. If you are using a local Kind cluster without a load balancer such as metallb, you might not have an external address.

    kubectl get gateway agent-gateway

    Example output:

    NAME            CLASS          ADDRESS                                  PROGRAMMED   AGE
agent-gateway   agentgateway   1234567890.us-east-2.elb.amazonaws.com   True         93s

  3. Create an HTTPRoute resource that routes to the Backend that you created in the previous step.

    kubectl apply -f- <<EOF
apiVersion: gateway.networking.k8s.io/v1
kind: HTTPRoute
metadata:
  name: mcp
spec:
  parentRefs:
  - name: agent-gateway
  rules:
    - backendRefs:
      - name: mcp-backend
        group: gateway.kgateway.dev
        kind: Backend   
EOF

Step 4: Verify the connection

Use the MCP Inspector tool to verify that you can connect to your sample MCP server through agentgateway.

  1. Get the agentgateway address.

    export AGENTGATEWAY_ADDRESS=$(kubectl get gateway agent-gateway -o=jsonpath="{.status.addresses[0].value}")
echo $AGENTGATEWAY_ADDRESS
    kubectl port-forward deployment/agent-gateway 8080:80

  2. From the terminal, run the MCP Inspector command. Then, the MCP Inspector opens in your browser.

    npx github:modelcontextprotocol/inspector

  3. From the MCP Inspector menu, connect to your agentgateway address as follows:

    • Transport Type: Select Streamable HTTP.
    • URL: Enter the agentgateway address and the /mcp path, such as ${AGENTGATEWAY_ADDRESS}/mcp or http://localhost:8080/mcp.
    • Click Connect.

  4. From the menu bar, click the Tools tab. Then from the Tools pane, click List Tools and select the fetch tool.

  5. From the fetch pane, in the url field, enter a website URL, such as https://lipsum.com/, and click Run Tool.

  6. Verify that you get back the the fetched URL content.

Argo Rollouts