RFC: New Server — aws-network-architecture-review-mcp-server

Summary

Proposing a new MCP server focused on proactive network architecture reviews with resiliency scoring and report generation. This complements the existing aws-network-mcp-server (which focuses on reactive troubleshooting/path tracing) by adding Direct Connect coverage, automated resiliency scoring, and customer-ready HTML report output.

Problem

AWS customers with hybrid networking (Direct Connect, Transit Gateway, VPN, Cloud WAN) lack automated tooling to proactively assess their architecture's resiliency. Manual reviews require deep networking expertise and hours of console navigation. The existing aws-network-mcp-server is excellent for troubleshooting but doesn't cover:

• Direct Connect (connections, VIFs, DX Gateways, BGP peer status, location diversity)
• Automated resiliency scoring
• Report generation with findings and recommendations

Proposed Solution

An MCP server (aws-network-architecture-review-mcp-server) that:

1. Collects DX, TGW, VPN, Cloud WAN, and CloudWatch data using standard AWS APIs
2. Scores resiliency across multiple dimensions (location diversity, connection redundancy, BGP health, VPN backup, MACsec, MTU, monitoring)
3. Generates an HTML report with prioritized findings and recommendations
4. Read-only operations only — safe for any environment

Proposed Tools

Tool	Returns
review_direct_connect	DX connections, VIFs, DX GWs, BGP status, location diversity
review_transit_gateway	TGW attachments, route tables, routing analysis
review_vpn	VPN tunnel status, redundancy check
review_cloud_wan	Core networks, segments, attachments, peerings
review_monitoring	CloudWatch alarms for DX/TGW/VPN, gap detection
get_resiliency_score	0-100 score with per-category breakdown (A-F grading)
generate_report	HTML report with findings, recommendations, and executive summary

Differentiation from aws-network-mcp-server

	aws-network-mcp-server	This proposal
Focus	Reactive troubleshooting	Proactive architecture review
DX support	None	Full
Scoring	None	Automated resiliency scoring
Report output	None	HTML report generation
Path tracing	Yes	No
Flow logs	Yes	No

These are complementary — a customer would use both.

Reference: aws-network-mcp-server source | docs

AWS APIs Used (read-only)

• directconnect:Describe*
• ec2:DescribeTransitGateway*, SearchTransitGatewayRoutes
• ec2:DescribeVpnConnections, DescribeCustomerGateways
• networkmanager:ListCoreNetworks, GetCoreNetwork, GetCoreNetworkPolicy, ListAttachments
• cloudwatch:DescribeAlarms, GetMetricData

Prior Art

I've built and validated this concept internally (used across 5 customer engagements). The public version replaces internal data sources with standard AWS APIs while retaining ~90% of the value.

Happy to discuss scope, tool naming, or anything else. Looking forward to feedback.