@aws/nx-plugin-mcp 1.0.0 → 1.0.1

package/docs/snippets/agent/architecture.mdx

@@ -2,71 +2,28 @@
 title: Agent Architecture
 ---
 import { Tabs, TabItem } from '@astrojs/starlight/components';
+import ArchitectureDiagram from '@components/architecture-diagram.astro';
 
 <Tabs syncKey="infra">
-<TabItem label="Bedrock AgentCore Runtime" _filter={{ infra: 'agentcore' }}>
+<TabItem label="AgentCore Runtime" _filter={{ infra: 'agentcore' }}>
 
-When deployed to [Bedrock AgentCore Runtime](https://aws.amazon.com/bedrock/agentcore/), the agent is built into a container image, pushed to Amazon ECR and run in AgentCore Runtime. Clients invoke the AgentCore Runtime data plane endpoint, which forwards requests to your agent. The agent calls Amazon Bedrock for model inference and may invoke tools, MCP servers, or downstream APIs.
+When deployed to [Bedrock AgentCore Runtime](https://aws.amazon.com/bedrock/agentcore/), your agent's code is packaged as a zip and run in the AgentCore managed runtime. Clients invoke the AgentCore Runtime data plane endpoint, which forwards requests to your agent. The agent calls Amazon Bedrock for model inference and may invoke tools, MCP servers, or downstream APIs.
 
-```d2 inline=true
-direction: right
+<ArchitectureDiagram options={{ infra: 'agentcore' }} />
 
-client: Client {
-  shape: image
-  icon: /nx-plugin-for-aws/icons/aws/client.svg
-}
-
-ecr: ECR {
-  shape: image
-  icon: /nx-plugin-for-aws/icons/aws/ecr.svg
-}
-
-agentcore: Strands Agent\n(AgentCore Runtime) {
-  shape: image
-  icon: /nx-plugin-for-aws/icons/aws/bedrock-agentcore-runtime.svg
-}
+</TabItem>
+<TabItem label="AgentCore Runtime (container)" _filter={{ infra: 'agentcore-ecr' }}>
 
-bedrock: Bedrock\n(Model Inference) {
-  shape: image
-  icon: /nx-plugin-for-aws/icons/aws/bedrock.svg
-  near: top-right
-}
+With `infra: agentcore-ecr`, the agent is built into a container image, pushed to Amazon ECR and run in AgentCore Runtime. This gives you OS-level control over the runtime environment, at the cost of a longer build and deploy cycle than the zip packaging above.
 
-cw: CloudWatch\n(Logs, Metrics) {
-  shape: image
-  icon: /nx-plugin-for-aws/icons/aws/cloudwatch.svg
-  near: bottom-right
-}
+<ArchitectureDiagram options={{ infra: 'agentcore-ecr' }} />
 
-client -> agentcore
-ecr -> agentcore: Container\nimage
-agentcore -> bedrock: InvokeModel
-agentcore -> cw
-```
 </TabItem>
 <TabItem label="None (local only)" _filter={{ infra: 'none' }}>
 
 With `infra: none`, no AWS infrastructure is generated. The agent runs as a local process and calls Amazon Bedrock for model inference.
 
-```d2 inline=true
-direction: right
-
-client: Client {
-  shape: image
-  icon: /nx-plugin-for-aws/icons/aws/client.svg
-}
-
-agent: Strands Agent\n(local process) {
-  shape: rectangle
-}
-
-bedrock: Bedrock\n(Model Inference) {
-  shape: image
-  icon: /nx-plugin-for-aws/icons/aws/bedrock.svg
-}
+<ArchitectureDiagram options={{ infra: 'none' }} />
 
-client -> agent
-agent -> bedrock: InvokeModel
-```
 </TabItem>
 </Tabs>

package/docs/snippets/agent/bedrock-deployment.mdx

@@ -111,7 +111,7 @@ export class ExampleStack extends Stack {
 ```
 </Fragment>
 <Fragment slot="terraform">
-```terraform {9-10}
+```terraform {10-11}
 module "asset_bucket" {
   source = "../../common/terraform/src/core/asset-bucket"
 }

package/docs/snippets/agent/runtime-arn.mdx

@@ -26,7 +26,7 @@ export class ExampleStack extends Stack {
 ```
 </Fragment>
 <Fragment slot="terraform">
-```terraform {9-10}
+```terraform {10-12}
 # Agent
 module "my_project_agent" {
   # Relative path to the generated module in the common/terraform project

package/docs/snippets/api/access-logging.mdx

@@ -16,7 +16,7 @@ The account role is managed by the `ApiGatewayAccount` construct, a stack-scoped
 
 The access log format is set by the `RestApi` construct your API extends. To customise it, pass `deployOptions` through to `super` in the generated `packages/common/constructs/src/app/apis/my-api.ts`, keeping the `tracingEnabled` the construct already sets:
 
-```ts {5-8} title="packages/common/constructs/src/app/apis/my-api.ts"
+```ts {4-7} title="packages/common/constructs/src/app/apis/my-api.ts"
 super(scope, id, {
   apiName: 'MyApi',
   // ...

package/docs/snippets/api/api-architecture.mdx

@@ -2,91 +2,20 @@
 title: API Architecture
 ---
 import { Tabs, TabItem } from '@astrojs/starlight/components';
+import ArchitectureDiagram from '@components/architecture-diagram.astro';
 
-The deployed application has the following architecture:
+The deployed application has the following architecture: an API Gateway API in front of a Lambda function running your handler.
 
 <Tabs syncKey="http-rest">
 <TabItem label="REST API" _filter={{ infra: 'rest-lambda' }}>
-```d2 inline=true
-direction: right
 
-client: Client {
-  shape: image
-  icon: /nx-plugin-for-aws/icons/aws/client.svg
-}
-
-waf: WAF {
-  shape: image
-  icon: /nx-plugin-for-aws/icons/aws/waf.svg
-}
-
-apigw: API Gateway\n(REST API) {
-  shape: image
-  icon: /nx-plugin-for-aws/icons/aws/api-gateway.svg
-}
-
-lambda: Lambda {
-  shape: image
-  icon: /nx-plugin-for-aws/icons/aws/lambda.svg
-}
-
-cw: CloudWatch\n(Logs, Metrics) {
-  shape: image
-  icon: /nx-plugin-for-aws/icons/aws/cloudwatch.svg
-  near: top-right
-}
-
-xray: X-Ray\n(Traces) {
-  shape: image
-  icon: /nx-plugin-for-aws/icons/aws/xray.svg
-  near: bottom-right
-}
-
-client -> waf
-waf -> apigw
-apigw -> lambda
-lambda -> cw
-lambda -> xray
-```
+<ArchitectureDiagram options={{ infra: 'rest-lambda' }} />
 
 REST APIs include an [AWS WAFv2](https://docs.aws.amazon.com/waf/latest/developerguide/waf-chapter.html) Web ACL in front of the API Gateway stage with the AWS managed default ruleset enabled.
 </TabItem>
 <TabItem label="HTTP API" _filter={{ infra: 'http-lambda' }}>
-```d2 inline=true
-direction: right
-
-client: Client {
-  shape: image
-  icon: /nx-plugin-for-aws/icons/aws/client.svg
-}
-
-apigw: API Gateway\n(HTTP API) {
-  shape: image
-  icon: /nx-plugin-for-aws/icons/aws/api-gateway.svg
-}
-
-lambda: Lambda {
-  shape: image
-  icon: /nx-plugin-for-aws/icons/aws/lambda.svg
-}
-
-cw: CloudWatch\n(Logs, Metrics) {
-  shape: image
-  icon: /nx-plugin-for-aws/icons/aws/cloudwatch.svg
-  near: top-right
-}
-
-xray: X-Ray\n(Traces) {
-  shape: image
-  icon: /nx-plugin-for-aws/icons/aws/xray.svg
-  near: bottom-right
-}
 
-client -> apigw
-apigw -> lambda
-lambda -> cw
-lambda -> xray
-```
+<ArchitectureDiagram options={{ infra: 'http-lambda' }} />
 
 HTTP APIs do not support WAF directly — if you need WAF protection, choose REST API instead or front the HTTP API with a CloudFront distribution.
 </TabItem>

package/docs/snippets/api/type-safe-api-integrations.mdx

@@ -5,7 +5,6 @@ import { Steps } from '@astrojs/starlight/components';
 import Infrastructure from '@components/infrastructure.astro';
 import Drawer from '@components/drawer.astro';
 import OptionFilter from '@components/option-filter.astro';
-import RunGenerator from '@components/run-generator.astro';
 
 The REST/HTTP API CDK constructs are configured to provide a type-safe interface for defining integrations for each of your operations.
 
@@ -405,7 +404,7 @@ Generated APIs support two integration patterns:
 <Fragment slot="cdk">
 The integration pattern can be changed at any time in CDK by updating your API construct. For example, setting `pattern` to `'shared'` creates a single function instead of one per integration:
 
-```ts {6}
+```ts {7}
 // packages/common/constructs/src/app/apis/my-api.ts
 export class MyApi<...> extends ... {
 
@@ -424,8 +423,7 @@ Unlike CDK, the integration pattern is baked into the generated module. To chang
 
 <Steps>
   1. Delete the previously generated API module in `packages/common/terraform/src/app/apis`
-  2. Re-run the API generator with the other integration pattern:
-      <RunGenerator generator="ts#api" requiredParameters={{ integrationPattern: 'shared' }} />
+  2. Re-run the generator that created your API with the other integration pattern (eg `--integrationPattern=shared`)
 </Steps>
 
 With the `isolated` pattern, the module reads the operations from a generated file:

package/docs/snippets/lambda-function/architecture.mdx

@@ -1,36 +1,10 @@
 ---
 title: Lambda Function Architecture
 ---
+import ArchitectureDiagram from '@components/architecture-diagram.astro';
 
-The deployed function has the following architecture:
+The deployed function has the following architecture, with its logs, metrics and traces going to CloudWatch and X-Ray:
 
-```d2 inline=true
-direction: right
-
-source: Event Source\n(SNS, SQS, ...) {
-  shape: rectangle
-}
-
-lambda: Lambda {
-  shape: image
-  icon: /nx-plugin-for-aws/icons/aws/lambda.svg
-}
-
-cw: CloudWatch\n(Logs, Metrics) {
-  shape: image
-  icon: /nx-plugin-for-aws/icons/aws/cloudwatch.svg
-  near: top-right
-}
-
-xray: X-Ray\n(Traces) {
-  shape: image
-  icon: /nx-plugin-for-aws/icons/aws/xray.svg
-  near: bottom-right
-}
-
-source -> lambda
-lambda -> cw
-lambda -> xray
-```
+<ArchitectureDiagram name="my-function" />
 
 The generator vends the function itself; you wire the event source up in your stack to invoke it (for example, an API Gateway integration, an EventBridge rule, an S3 notification or an SQS event source mapping).

package/docs/snippets/mcp/architecture.mdx

@@ -2,57 +2,28 @@
 title: MCP Server Architecture
 ---
 import { Tabs, TabItem } from '@astrojs/starlight/components';
+import ArchitectureDiagram from '@components/architecture-diagram.astro';
 
 <Tabs syncKey="infra">
-<TabItem label="Bedrock AgentCore Runtime" _filter={{ infra: 'agentcore' }}>
+<TabItem label="AgentCore Runtime" _filter={{ infra: 'agentcore' }}>
 
-When deployed to [Bedrock AgentCore Runtime](https://aws.amazon.com/bedrock/agentcore/), the MCP server is built into a container image, pushed to Amazon ECR, and run in AgentCore Runtime. AI assistants invoke the AgentCore Runtime data plane endpoint, which forwards `tools/*` and `resources/*` calls to your server over the [streamable HTTP transport](https://modelcontextprotocol.io/specification/draft/basic/transports#streamable-http).
+When deployed to [Bedrock AgentCore Runtime](https://aws.amazon.com/bedrock/agentcore/), your server's code is packaged as a zip and run in the AgentCore managed runtime. AI assistants invoke the AgentCore Runtime data plane endpoint, which forwards `tools/*` and `resources/*` calls to your server over the [streamable HTTP transport](https://modelcontextprotocol.io/specification/draft/basic/transports#streamable-http).
 
-```d2 inline=true
-direction: right
+<ArchitectureDiagram options={{ infra: 'agentcore' }} />
 
-assistant: AI Assistant {
-  shape: image
-  icon: /nx-plugin-for-aws/icons/aws/client.svg
-}
-
-ecr: ECR {
-  shape: image
-  icon: /nx-plugin-for-aws/icons/aws/ecr.svg
-}
+</TabItem>
+<TabItem label="AgentCore Runtime (container)" _filter={{ infra: 'agentcore-ecr' }}>
 
-agentcore: MCP Server\n(AgentCore Runtime) {
-  shape: image
-  icon: /nx-plugin-for-aws/icons/aws/bedrock-agentcore-runtime.svg
-}
+With `infra: agentcore-ecr`, the MCP server is built into a container image, pushed to Amazon ECR and run in AgentCore Runtime. This gives you OS-level control over the runtime environment, at the cost of a longer build and deploy cycle than the zip packaging above.
 
-cw: CloudWatch\n(Logs, Metrics) {
-  shape: image
-  icon: /nx-plugin-for-aws/icons/aws/cloudwatch.svg
-}
+<ArchitectureDiagram options={{ infra: 'agentcore-ecr' }} />
 
-assistant -> agentcore: Streamable\nHTTP
-ecr -> agentcore: Container\nimage
-agentcore -> cw
-```
 </TabItem>
 <TabItem label="None (local only)" _filter={{ infra: 'none' }}>
 
 With `infra: none`, no AWS infrastructure is generated. The MCP server is configured for local STDIO and HTTP transports only, and is consumed by AI assistants running on the same machine.
 
-```d2 inline=true
-direction: right
-
-assistant: AI Assistant {
-  shape: image
-  icon: /nx-plugin-for-aws/icons/aws/client.svg
-}
-
-server: MCP Server\n(local process) {
-  shape: rectangle
-}
+<ArchitectureDiagram options={{ infra: 'none' }} />
 
-assistant -> server: STDIO\nor\nStreamable HTTP
-```
 </TabItem>
 </Tabs>

package/docs/snippets/mcp/bedrock-deployment.mdx

@@ -106,7 +106,7 @@ export class ExampleStack extends Stack {
 ```
 </Fragment>
 <Fragment slot="terraform">
-```terraform {5-6}
+```terraform {6-7}
 # MCP Server
 module "my_project_mcp_server" {
   # Relative path to the generated module in the common/terraform project

package/docs/snippets/pdk-migration/example/01-migrate-api.mdx

@@ -26,7 +26,7 @@ If you used OpenAPI or TypeSpec as your modelling language, or have handlers imp
 
 Run the <Link path="/guides/ts-smithy-api">`ts#api` generator</Link> with `framework` set to `smithy` to set up your api project in `packages/api`:
 
-<RunGenerator generator="ts#api" noInteractive requiredParameters={{ name: 'api', framework: 'smithy', namespace: 'com.aws', auth: 'iam' }} />
+<RunGenerator generator="ts#api" noInteractive requiredParameters={{ name: 'api', framework: 'smithy', namespace: 'com.aws', auth: 'iam' }} noOptions />
 
 You will notice this generates a `model` project, as well as a `backend` project. The `model` project contains your Smithy model, and `backend` contains your server implementation.
 

package/docs/snippets/pdk-migration/example/02-migrate-website.mdx

@@ -20,13 +20,13 @@ As part of the migration, we will also move from PDK's configured React Router t
 
 Run the <Link path="/guides/react-website">`ts#website` generator</Link> with `framework` set to `react` to set up your website project in `packages/website`. Since the shopping list application is built with CloudScape components, we also set `ux` to `cloudscape` (the default is `shadcn`):
 
-<RunGenerator generator="ts#website" noInteractive requiredParameters={{ name: 'website', framework: 'react', ux: 'cloudscape' }} />
+<RunGenerator generator="ts#website" noInteractive requiredParameters={{ name: 'website', framework: 'react', ux: 'cloudscape' }} noOptions />
 
 #### Add Cognito Authentication
 
 The React website generator above doesn't bundle cognito authentication by default like `CloudscapeReactTsWebsiteProject`, instead it's added explicitly via the <Link path="/guides/react-website-auth">`ts#website#auth` generator</Link>.
 
-<RunGenerator generator="ts#website#auth" noInteractive requiredParameters={{ project: 'website', cognitoDomain: 'shopping-list' }} />
+<RunGenerator generator="ts#website#auth" noInteractive requiredParameters={{ project: 'website', cognitoDomain: 'shopping-list' }} noOptions />
 
 This adds React components which manage the appropriate redirects to ensure users log in using the Cognito hosted UI. This also adds a CDK construct to deploy the Cognito resources in `packages/common/constructs`, called `UserIdentity`.
 
@@ -34,13 +34,12 @@ This adds React components which manage the appropriate redirects to ensure user
 The PDK `CloudscapeReactTsWebsiteProject` relied on `@aws-northstar/ui` to provide Cognito login components in-app. If you would prefer to use this approach instead of moving to the hosted UI, you can replace the generated `packages/common/constructs/src/core/user-identity.ts` with the [implementation from PDK](https://github.com/aws/aws-pdk/blob/mainline/packages/identity/src/user-identity.ts), replacing the constructs from `@aws-cdk/aws-cognito-identitypool-alpha` with those vended by `aws-cdk-lib`, and make sure to set the relevant values in `RuntimeConfig`:
 
 ```ts
-RuntimeConfig.ensure(this).config = {
-  ...RuntimeConfig.ensure(this).config,
+RuntimeConfig.ensure(this).set('connection', 'cognitoProps', {
   region: Stack.of(this).region,
   identityPoolId: this.identityPool.identityPoolId,
   userPoolId: this.userPool.userPoolId,
   userPoolWebClientId: this.userPoolClient.userPoolClientId,
-};
+});
 ```
 
 You can then reuse the `Auth` component from your `CloudscapeReactTsWebsiteProject`.
@@ -52,7 +51,7 @@ In PDK you could pass the vended Projen projects to one another to trigger integ
 
 With the Nx Plugin for AWS, API integration is supported via the <Link path="/guides/connection">`connection` generator</Link>. Next, we use this generator so that our website can invoke our Smithy API:
 
-<RunGenerator generator="connection" noInteractive requiredParameters={{ sourceProject: 'website', targetProject: 'api' }} />
+<RunGenerator generator="connection" noInteractive requiredParameters={{ sourceProject: 'website', targetProject: 'api' }} noOptions />
 
 This generates the necessary client providers and build targets for your website to call your API via a generated TypeScript client.
 

package/docs/snippets/pdk-migration/example/03-migrate-infra.mdx

@@ -22,7 +22,7 @@ A big advantage of the Nx Plugin for AWS over PDK is that the CDK constructs it
 
 Run the <Link path="/guides/typescript-infrastructure">`ts#infra` generator</Link> to set up your infrastructure project in `packages/infra`:
 
-<RunGenerator generator="ts#infra" noInteractive requiredParameters={{ name: 'infra' }} />
+<RunGenerator generator="ts#infra" noInteractive requiredParameters={{ name: 'infra' }} noOptions />
 
 #### Migrate the CDK Infrastructure
 

package/docs/snippets/pdk-migration/faq/type-safe-api.mdx

@@ -79,7 +79,7 @@ Type Safe API provided a Projen project type named `SmithyShapeLibraryProject` w
 
 The equivalent is the <Link path="/guides/smithy-project">`smithy#project` generator</Link> with `type` set to `shapes`:
 
-<RunGenerator generator="smithy#project" requiredParameters={{ name: 'my-shapes', type: 'shapes' }} />
+<RunGenerator generator="smithy#project" requiredParameters={{ name: 'my-shapes', type: 'shapes' }} noOptions />
 
 Move the shapes from your `SmithyShapeLibraryProject` into the generated project's `src` folder, then refer to the <Link path="/guides/smithy-project#depending-on-a-shape-library">Smithy project guide</Link> for how to wire the library up as a dependency of your API's model.
 
@@ -167,7 +167,7 @@ new Api(this, 'MyApi', {
 
 You will need to "stub" your service/router for your service to compile if using the `ts#smithy-api` and the TypeScript Server SDK, eg:
 
-```ts {3}
+```ts {4}
 // service.ts
 export const Service: ApiService<ServiceContext> = {
   ...

package/docs/snippets/rdb/architecture.mdx

@@ -1,39 +1,8 @@
 ---
 title: RDB Architecture
 ---
+import ArchitectureDiagram from '@components/architecture-diagram.astro';
 
 The deployed database has the following architecture. By default, an [Amazon RDS Proxy](https://docs.aws.amazon.com/AmazonRDS/latest/UserGuide/rds-proxy.html) sits in front of the Aurora cluster to pool connections and to enable [IAM authentication](https://docs.aws.amazon.com/AmazonRDS/latest/UserGuide/UsingWithRDS.IAMDBAuth.html) — see [Disable RDS Proxy](#disable-rds-proxy) for the alternative. The architecture is the same whether you select the PostgreSQL or MySQL engine; only the Aurora engine flavor differs.
 
-```d2 inline=true
-direction: right
-
-app: Application\n(Lambda, Agent, ...) {
-  shape: hexagon
-}
-
-proxy: RDS Proxy {
-  shape: image
-  icon: /nx-plugin-for-aws/icons/aws/rds.svg
-}
-
-migrations: Migrations Lambda {
-  shape: image
-  icon: /nx-plugin-for-aws/icons/aws/lambda.svg
-}
-
-aurora: Aurora\n(PostgreSQL or MySQL) {
-  shape: image
-  icon: /nx-plugin-for-aws/icons/aws/aurora.svg
-}
-
-secrets: Secrets Manager\n(DB credentials) {
-  shape: image
-  icon: /nx-plugin-for-aws/icons/aws/secrets-manager.svg
-}
-
-app -> proxy: SQL (IAM auth)
-proxy -> aurora
-migrations -> aurora: Schema migrations
-migrations -> secrets: Admin credentials
-aurora -> secrets: Generates and rotates\nadmin credentials
-```
+<ArchitectureDiagram />

package/generators.json

@@ -104,6 +104,13 @@
       "metric": "g15",
       "hidden": true
     },
+    "open-api#py-client": {
+      "factory": "./src/open-api/py-client/generator",
+      "schema": "./src/open-api/py-client/schema.json",
+      "description": "Generate a Python httpx client from an OpenAPI specification",
+      "metric": "g73",
+      "hidden": true
+    },
     "open-api#ts-client": {
       "factory": "./src/open-api/ts-client/generator",
       "schema": "./src/open-api/ts-client/schema.json",

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@aws/nx-plugin-mcp",
-  "version": "1.0.0",
+  "version": "1.0.1",
   "repository": {
     "type": "git",
     "url": "https://github.com/awslabs/nx-plugin-for-aws.git",

package/src/agentcore-gateway/schema.json

@@ -35,6 +35,7 @@
     "auth": {
       "type": "string",
       "description": "The method used to authenticate inbound requests to your gateway. Only applicable when infra is set (ignored when infra is none).",
+      "x-when": { "infra": "agentcore" },
       "enum": ["iam", "cognito"],
       "default": "iam",
       "x-prompt": "How would you like to authenticate inbound requests to your gateway?",

package/src/open-api/py-client/schema.json

@@ -0,0 +1,28 @@
+{
+  "$schema": "https://json-schema.org/schema",
+  "$id": "OpenApiPyClient",
+  "title": "OpenAPI Python Client",
+  "description": "Generate a Python httpx client from an OpenAPI specification",
+  "type": "object",
+  "properties": {
+    "openApiSpecPath": {
+      "type": "string",
+      "description": "Path to the OpenAPI specification relative to the monorepo root",
+      "x-priority": "important"
+    },
+    "outputPath": {
+      "type": "string",
+      "description": "Path to the directory in which to generate the client relative to the monorepo root",
+      "x-priority": "important"
+    },
+    "clientType": {
+      "type": "string",
+      "description": "Which clients to emit. 'sync' emits client.py using httpx.Client, 'async' emits async_client.py using httpx.AsyncClient, 'both' emits both.",
+      "enum": ["sync", "async", "both"],
+      "x-prompt": "Which clients would you like to emit?",
+      "default": "both",
+      "x-priority": "important"
+    }
+  },
+  "required": ["openApiSpecPath", "outputPath"]
+}

package/src/py/agent/schema.json

@@ -32,6 +32,7 @@
     "auth": {
       "type": "string",
       "description": "The method used to authenticate with your Agent. Only applicable when infra is set (ignored when infra is none).",
+      "x-when": { "infra": ["agentcore", "agentcore-ecr"] },
       "default": "iam",
       "enum": ["iam", "cognito"],
       "x-prompt": "How would you like to authenticate with your Agent?",
@@ -66,6 +67,7 @@
       "description": "The storage used to persist session for your Agent. LangChain supports 's3' or 'dynamodb-s3'; Strands supports 's3'; 'in-memory' is valid for both.",
       "x-prompt": "How would you like to persist session for your Agent?",
       "enum": ["s3", "dynamodb-s3", "in-memory"],
+      "x-value-when": { "dynamodb-s3": { "framework": "langchain" } },
       "default": "s3",
       "x-priority": "important"
     },

package/src/py/mcp-server/schema.json

@@ -24,6 +24,7 @@
     "auth": {
       "type": "string",
       "description": "The method used to authenticate with your MCP server. Only applicable when infra is set (ignored when infra is none).",
+      "x-when": { "infra": ["agentcore", "agentcore-ecr"] },
       "default": "iam",
       "enum": ["iam", "cognito"],
       "x-prompt": "How would you like to authenticate with your MCP server?",

package/src/ts/agent/schema.json

@@ -32,6 +32,7 @@
     "auth": {
       "type": "string",
       "description": "The method used to authenticate with your Agent. Only applicable when infra is set (ignored when infra is none).",
+      "x-when": { "infra": ["agentcore", "agentcore-ecr"] },
       "default": "iam",
       "enum": ["iam", "cognito"],
       "x-prompt": "How would you like to authenticate with your Agent?",

package/src/ts/api/schema.json

@@ -39,6 +39,7 @@
     "namespace": {
       "type": "string",
       "description": "The namespace for the Smithy API (only applicable for the smithy framework). Defaults to your monorepo scope",
+      "x-when": { "framework": "smithy" },
       "x-prompt": "What namespace would you like your API to have? i.e: com.example"
     },
     "integrationPattern": {
@@ -97,6 +98,7 @@
       "description": "The type of infrastructure to use to deploy this API.",
       "default": "rest-lambda",
       "enum": ["rest-lambda", "http-lambda", "none"],
+      "x-value-when": { "http-lambda": { "framework": "trpc" } },
       "x-prompt": "What infrastructure would you like to deploy your API with?",
       "x-priority": "important"
     },

package/src/ts/mcp-server/schema.json

@@ -24,6 +24,7 @@
     "auth": {
       "type": "string",
       "description": "The method used to authenticate with your MCP server. Only applicable when infra is set (ignored when infra is none).",
+      "x-when": { "infra": ["agentcore", "agentcore-ecr"] },
       "default": "iam",
       "enum": ["iam", "cognito"],
       "x-prompt": "How would you like to authenticate with your MCP server?",

package/src/ts/react-website/app/schema.json

@@ -40,6 +40,7 @@
       "type": "string",
       "description": "The preferred UX provider.",
       "enum": ["none", "cloudscape", "shadcn"],
+      "x-value-when": { "shadcn": { "tailwind": "true" } },
       "x-priority": "important",
       "default": "shadcn",
       "x-prompt": {

package/src/ts/website/app/schema.json

@@ -47,6 +47,7 @@
       "type": "string",
       "description": "The preferred UX provider.",
       "enum": ["none", "cloudscape", "shadcn"],
+      "x-value-when": { "shadcn": { "tailwind": "true" } },
       "x-priority": "important",
       "default": "shadcn",
       "x-prompt": {