← Explore all mcp servers

AWS DATA SERVICES / AWS Labs

AWS Labs Core Network

Investigates AWS network paths, routing, security rules and flow logs across VPC, Transit Gateway, Cloud WAN, VPN and Network Firewall.

“A Model Context Protocol (MCP) server providing comprehensive tools for troubleshooting and analyzing AWS core networking services including Cloud WAN, Transit Gateway, VPC, Network Firewall, and VPN connections.”

01 / THE REASONING

Why this made the selection.

  • Specialized publisher integration with documented IAM and data access boundaries.
  • Trace an observed connectivity failure from ENI/routing data through transit and firewall inspection.
  • The README is a local, read-only troubleshooter for Cloud WAN, Transit Gateway, VPC, Network Firewall, and VPN.
  • It cannot change infrastructure, and flow-log tools do not read S3 or Firehose destinations.

02 / THE REVIEW RECORD

What we actually inspected.

Source review has boundaries.
A clear record is more useful than a “safe” badge.

Material inspected

  • src/aws-network-mcp-server/README.md
  • src/aws-network-mcp-server/pyproject.toml
  • src/aws-network-mcp-server/awslabs/aws_network_mcp_server/server.py
  • Root README.md and LICENSE
  • LICENSE

Our findings

  • Server instructions prescribe discovery, analysis, trace, inspection and verification. The retained VPC flow-log helper calls start_query, so the entry avoids promising only Describe/Get/List calls.
  • The server troubleshoots Cloud WAN, Transit Gateway, VPC, Network Firewall, and VPN from a local process that calls AWS APIs directly.
  • It requires AWS credentials. The README says no data is sent to third-party services. Cross-account calls use named profiles.
  • All tools are read-only and cannot create, modify, or delete resources. Flow-log tools do nothing unless logs go to CloudWatch Logs rather than S3 or Kinesis Data Firehose.

Not established by this review

  • Server startup, authentication, live tool execution and security isolation were not tested.
  • Published package/container parity with a source revision and hosted implementation internals were not tested.
  • The server was not started and its tools were not called.
  • A pin does not verify transitive dependencies.
  • No tools/list or tool call was made.

The review applies to the material and revision named here. A newer upstream release can change its behavior.

03 / PUT IT TO WORK

Connect a server deliberately.

Upstream setup instructions ↗

DOCUMENTED COMMAND

uvx awslabs.aws-network-mcp-server@latest

Copying does not execute this command. It may retrieve a newer version than the reviewed source.

  1. Configure named AWS profiles with required network inspection and log-query permissions.
  2. Start with get_path_trace_methodology, then discover the IP/ENI and inspect route/security data.
  3. Use bounded flow-log time windows to verify the proposed path and retain account/region identifiers with findings.

Before you start

  • Python 3.10 or newer, uv/uvx and an MCP client that can launch a local stdio process.
  • An AWS account, configured credentials and access to the intended region and service resources.

Documented configuration example

Use the client and authentication context described in the setup guidance. Configuration formats vary between hosts.

{
  "mcpServers": {
    "awslabs-aws-network": {
      "command": "uvx",
      "args": [
        "awslabs.aws-network-mcp-server@latest"
      ],
      "env": {
        "AWS_PROFILE": "YOUR_RESTRICTED_PROFILE",
        "AWS_REGION": "us-west-2"
      }
    }
  }
}

04 / FOLLOW THE EVIDENCE

The source trail.

Our notes are separate from the original resource.
Check upstream before adopting a new version.

  1. https://github.com/awslabs/mcp/blob/8840003820a78dd018561d55c7ab12fcdd708464/src/aws-network-mcp-server/README.md

    Supports: summary, install, configExample, access, limitations, bestFor, review, compatibility, transports, license

  2. https://github.com/awslabs/mcp/blob/8840003820a78dd018561d55c7ab12fcdd708464/src/aws-network-mcp-server/pyproject.toml

    Supports: summary, install, configExample, access, limitations, bestFor, review, compatibility, transports, license

  3. https://github.com/awslabs/mcp/blob/8840003820a78dd018561d55c7ab12fcdd708464/src/aws-network-mcp-server/awslabs/aws_network_mcp_server/server.py

    Supports: summary, install, configExample, access, limitations, bestFor, review, compatibility, transports, license

  4. https://github.com/awslabs/mcp/blob/8840003820a78dd018561d55c7ab12fcdd708464/README.md

    Supports: summary, install, configExample, access, limitations, bestFor, review, compatibility, transports, license

  5. Applicable licence ↗Checked

    https://github.com/awslabs/mcp/blob/8840003820a78dd018561d55c7ab12fcdd708464/LICENSE

    Supports: license

  6. https://github.com/awslabs/mcp/blob/8840003820a78dd018561d55c7ab12fcdd708464/src/aws-network-mcp-server/awslabs/aws_network_mcp_server/tools/vpc/get_vpc_flow_logs.py

    Supports: summary, install, configExample, access, limitations, bestFor, review, compatibility, transports, license

Evidence & Ask