Skip to main content
Glama
toreydai

ingress2gateway-aws-mcp

by toreydai

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault

No arguments

Capabilities

Features and capabilities supported by this server

CapabilityDetails
tools
{
  "listChanged": false
}
prompts
{
  "listChanged": false
}
resources
{
  "subscribe": false,
  "listChanged": false
}
experimental
{}

Tools

Functions exposed to the LLM to take actions

NameDescription
check_prerequisitesA

Check if the target environment meets AWS Gateway API migration prerequisites.

Args: lbc_version: AWS Load Balancer Controller version (e.g. "2.14.1"). Leave empty to skip. needs_l4: Set true if migration includes TCP/UDP/TLS routes (requires experimental channel). tls_hostnames: Comma-separated TLS hostnames to check ACM certificate coverage.

analyze_ingressA

Analyze Nginx Ingress configuration and return a structured summary. Reports annotation compatibility, route type distribution, TLS hosts, cross-namespace refs, and cost estimate.

Args: ingress_yaml: Nginx Ingress YAML content (multi-document supported) or file path. tcp_services_yaml: Optional tcp-services ConfigMap YAML for L4 TCP routes. udp_services_yaml: Optional udp-services ConfigMap YAML for L4 UDP routes.

convert_to_gateway_apiA

Convert Nginx Ingress YAML to AWS Gateway API resources (full pipeline).

Steps: base conversion → GatewayClass injection → TLS fixup → L4/L7 split → Gateway merge → LoadBalancerConfiguration → TargetGroupConfiguration → ListenerRuleConfiguration

Args: ingress_yaml: Nginx Ingress YAML content or file path. tcp_services_yaml: Optional tcp-services ConfigMap YAML for TCP routes. udp_services_yaml: Optional udp-services ConfigMap YAML for UDP routes. scheme: ALB scheme — "internet-facing" or "internal". namespace: Default namespace if not specified in resources. alb_gateway_class: Name for the ALB GatewayClass (default: aws-alb). nlb_gateway_class: Name for the NLB GatewayClass (default: aws-nlb). gateway_grouping: Gateway consolidation strategy: "by-class-scheme" (default) | "by-namespace" | "by-host" | "single" health_check_path: TargetGroupConfiguration health check path. health_check_interval: TargetGroupConfiguration health check interval seconds. healthy_threshold: TargetGroupConfiguration healthy threshold count. unhealthy_threshold: TargetGroupConfiguration unhealthy threshold count.

generate_migration_reportB

Generate a complete Markdown migration report. Includes: summary, cost impact, DNS changes, annotation analysis, health check reminders, ACM checklist, migration checklist, and rollback plan.

Args: ingress_yaml: Nginx Ingress YAML content or file path. tcp_services_yaml: Optional tcp-services ConfigMap YAML. udp_services_yaml: Optional udp-services ConfigMap YAML. scheme: ALB scheme — "internet-facing" or "internal". gateway_grouping: Gateway consolidation strategy. lbc_version: AWS LBC version for pre-flight checks (optional). health_check_path: TargetGroupConfiguration health check path. health_check_interval: TargetGroupConfiguration health check interval seconds. healthy_threshold: TargetGroupConfiguration healthy threshold count. unhealthy_threshold: TargetGroupConfiguration unhealthy threshold count.

validate_outputA

Validate Gateway API YAML against schema rules and AWS LBC constraints. Checks: required fields, L4/L7 mixing, certificateRefs misuse, parentRef consistency, experimental channel requirements, and cross-namespace reference coverage.

Args: yaml_content: Gateway API YAML content to validate, or file path.

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/toreydai/ingress2gateway-aws-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server