AWS CDK MCP Server

Overview

AWS CDK MCP Server is a stdio MCP server for AWS Cloud Development Kit guidance, infrastructure-as-code patterns, CDK Nag security/compliance guidance, AWS Solutions Constructs discovery, GenAI CDK construct discovery, Lambda layer documentation, and Bedrock Agent schema generation.

This submission reviews the published PyPI package awslabs.cdk-mcp-server version 1.0.2. The package source distribution includes the README, pyproject metadata, server entry point, core tools/resources, and data loader/parser modules used for external documentation fetching, file IO, and schema generation.

Install and launch

The upstream README documents an MCP client launch using uvx with awslabs.cdk-mcp-server@latest and FASTMCP_LOG_LEVEL=ERROR. Wardn registry metadata pins the runnable package argument to the reviewed package version:

{
  "command": "uvx",
  "args": ["[email protected]"],
  "env": {
    "FASTMCP_LOG_LEVEL": "ERROR"
  }
}

The README also documents optional Docker build/run commands: docker build -t awslabs/cdk-mcp-server . and docker run --rm --interactive --env FASTMCP_LOG_LEVEL=ERROR awslabs/cdk-mcp-server:latest. Those Docker flags are install/alternate launch documentation only and are not MCP package launch arguments for the uvx target.

Configuration

FASTMCP_LOG_LEVEL is the only environment variable in the documented MCP client launch. ENABLE_CDK_NAG appears in CDK application guidance as an example user-app setting and is not read by the MCP server runtime. Dockerfile variables such as UV_COMPILE_BYTECODE, UV_LINK_MODE, UV_PYTHON_PREFERENCE, UV_FROZEN, and PATH are image-internal settings and are recorded in source review rather than package launch configuration.

Tools

• CDKGeneralGuidance: returns prescriptive CDK best-practice guidance.
• GetAwsSolutionsConstructPattern: searches or retrieves AWS Solutions Constructs patterns by pattern name or AWS service list.
• SearchGenAICDKConstructs: searches GenAI CDK constructs by query and/or construct type.
• GenerateBedrockAgentSchema: generates OpenAPI schemas from local Lambda Python files using BedrockAgentResolver and writes output schema/fallback files to client-provided paths.
• LambdaLayerDocumentationProvider: provides Lambda layer documentation and code-generation guidance.
• ExplainCDKNagRule: explains a CDK Nag rule and remediation guidance.
• CheckCDKNagSuppressions: checks CDK code or a local file path for CDK Nag suppressions.

Resources

Registered resource URI families include cdk-nag://rules/{rule_pack}, cdk-nag://warnings/{rule_pack}, cdk-nag://errors/{rule_pack}, aws-solutions-constructs://{pattern_name}, genai-cdk-constructs://..., and lambda-powertools://{topic}.

Prerequisites

Requires uv and Python 3.10+. The README documents AWS CDK CLI installation with npm install -g aws-cdk for the CDK workflows the server guides; that implies Node.js/npm for CDK CLI installation. Some tools fetch documentation dynamically from GitHub or AWS documentation. Bedrock Agent schema generation requires Lambda code using AWS Lambda Powertools BedrockAgentResolver; missing Lambda dependencies may cause the tool to create a fallback script that must be run in a properly configured local environment.

Limitations and security notes

The server runs over stdio; SSE support was removed before this version. External documentation features depend on GitHub/AWS documentation availability and structure. File-oriented tools operate on client-provided paths: suppression checking can read local code files, and schema generation can read Lambda files, create simplified variants, write OpenAPI schemas, and write fallback scripts. CDK Nag suppressions require human review; users should review warnings and avoid suppressing issues whenever possible.

Additional reviewed configuration evidence

The PyPI project metadata still advertises https://awslabs.github.io/mcp/servers/cdk-mcp-server/, but that page returned 404 during review, so the visible website/documentation URL is set to the reviewed PyPI 1.0.2 page. The packaged static/lambda_powertools guidance files document Lambda application environment variables POWERTOOLS_SERVICE_NAME, POWERTOOLS_METRICS_NAMESPACE, and LOG_LEVEL; these are recorded as non-launch user-application variables because they configure generated/user Lambda functions, not the MCP server stdio process.