@aws/nx-plugin-mcp 1.0.0-rc.98 → 1.0.1

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

@@ -8,6 +8,7 @@ import Link from '@components/link.astro';
 import NxCommands from '@components/nx-commands.astro';
 import Drawer from '@components/drawer.astro';
 import InstallCommand from '@components/install-command.astro';
+import PackageManagerShortCommand from '@components/package-manager-short-command.astro';
 
 The `TypeSafeApiProject` used in the shopping list application made use of:
 
@@ -25,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.
 
@@ -114,12 +115,12 @@ Now that we have the basic structure for our Smithy API project, we can migrate
 
 At this point, let's run a build to check our model changes and ensure we have some generated server code to work with. There will be some failures in the backend project (`@shopping-list/api`) but we'll address those next.
 
-<NxCommands commands={["run-many --target build"]} />
+<PackageManagerShortCommand commands={["build"]} />
 
 :::note
 You may see a build failure due to lint issues. These can usually be automatically fixed:
 
-<NxCommands commands={["run-many --target lint --fix"]} />
+<PackageManagerShortCommand commands={["lint"]} />
 :::
 
 #### Migrate the Lambda Handlers
@@ -132,7 +133,7 @@ The shopping list application's lambda handlers rely on the `@aws-sdk/client-dyn
 
 <InstallCommand pkg="@aws-sdk/client-dynamodb" project="@shopping-list/api" />
 
-Then, let's copy the `handlers/src/dynamo-client.ts` file from the PDK project to `backend/src/operations` so it's available for our handlers.
+Then, let's copy the `handlers/typescript/src/dynamo-client.ts` file from the PDK project to `backend/src/operations` so it's available for our handlers.
 
 The `ts#smithy-api` generator scaffolds an example `Echo` operation. Since we removed this from our model, delete the corresponding handler in `backend/src/operations/echo.ts`. We'll register our migrated operations in `service.ts` further below.
 
@@ -587,6 +588,7 @@ Additionally, update `packages/api/backend/project.json` and update `metadata.ap
 +    "apiName": "my-api",
     "auth": "iam",
     "modelProject": "@shopping-list/api-model",
+    "iac": "cdk",
     "ports": [3001]
   },
 ```
@@ -595,10 +597,10 @@ Additionally, update `packages/api/backend/project.json` and update `metadata.ap
 
 We can now build the project to check that the migration has worked so far:
 
-<NxCommands commands={["run-many --target build"]} />
+<PackageManagerShortCommand commands={["build"]} />
 
 :::note
 You may see a build failure due to lint issues. These can usually be automatically fixed:
 
-<NxCommands commands={["run-many --target lint --fix"]} />
+<PackageManagerShortCommand commands={["lint"]} />
 :::

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

@@ -8,6 +8,7 @@ import Link from '@components/link.astro';
 import NxCommands from '@components/nx-commands.astro';
 import Drawer from '@components/drawer.astro';
 import InstallCommand from '@components/install-command.astro';
+import PackageManagerShortCommand from '@components/package-manager-short-command.astro';
 
 The `CloudscapeReactTsWebsiteProject` used in the shopping list application configured a React website with CloudScape and Cognito authentication built in.
 
@@ -19,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`.
 
@@ -33,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`.
@@ -51,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.
 
@@ -100,7 +100,7 @@ Since we're using [file-based routing](https://tanstack.com/router/latest/docs/f
 
 Let's start the local website server:
 
-<NxCommands commands={["dev website"]} />
+<PackageManagerShortCommand commands={["dev"]} />
 
 :::tip
 We're using the `dev` target here, which also starts local servers for any APIs which have been connected with `connection`, and hot-reloads if your website, model, or backend changes! This allows us to test our API and website locally before we've even written any CDK code.

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

@@ -8,6 +8,7 @@ import Link from '@components/link.astro';
 import NxCommands from '@components/nx-commands.astro';
 import Drawer from '@components/drawer.astro';
 import InstallCommand from '@components/install-command.astro';
+import PackageManagerShortCommand from '@components/package-manager-short-command.astro';
 
 The last project we need to migrate for our shopping list application is the `InfrastructureTsProject`. This is a TypeScript CDK project, for which the Nx Plugin for AWS equivalent is the <Link path="/guides/typescript-infrastructure">`ts#infra` generator</Link>.
 
@@ -21,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
 
@@ -152,10 +153,10 @@ Notice that we don't pass the identity or API to the website - runtime config is
 
 Let's build the project now that we've migrated all the relevant parts of the codebase to our new project.
 
-<NxCommands commands={["run-many --target build"]} />
+<PackageManagerShortCommand commands={["build"]} />
 
 :::caution
 You may see a build failure due to lint issues. These can usually be automatically fixed:
 
-<NxCommands commands={["run-many --target lint --fix"]} />
+<PackageManagerShortCommand commands={["lint"]} />
 :::

package/docs/snippets/pdk-migration/example/04-deploy.mdx

@@ -8,6 +8,7 @@ import Link from '@components/link.astro';
 import NxCommands from '@components/nx-commands.astro';
 import Drawer from '@components/drawer.astro';
 import InstallCommand from '@components/install-command.astro';
+import PackageManagerShortCommand from '@components/package-manager-short-command.astro';
 
 
 Now we've got our fully migrated codebase, we can look at deploying it. There are two paths we can take at this point.
@@ -22,7 +23,7 @@ The simplest approach is to treat this as a completely new application, meaning
 
 1. Deploy the new application:
 
-    <NxCommands commands={["deploy infra shopping-list-infra-sandbox/*"]} />
+    <NxCommands commands={['deploy-sandbox infra']} />
 
 </Steps>
 
@@ -63,7 +64,7 @@ For our shopping list application, the stateful resources we care about are the
 
     ```diff lang="ts"
     // packages/common/constructs/src/core/user-identity.ts
-    -this.userPool = this.createUserPool();
+    -this.userPool = this.createUserPool(mfa, mfaSecondFactor);
     +this.userPool = UserPool.fromUserPoolId(
     +  this,
     +  'UserPool',
@@ -73,9 +74,9 @@ For our shopping list application, the stateful resources we care about are the
 
 1. Build and deploy the new application:
 
-    <NxCommands commands={["run-many --target build"]} />
+    <PackageManagerShortCommand commands={["build"]} />
 
-    <NxCommands commands={["deploy infra shopping-list-infra-sandbox/*"]} />
+    <NxCommands commands={['deploy-sandbox infra']} />
 
     Now we have our new application stood up referencing the existing resources, not yet taking any traffic.
 
@@ -98,7 +99,7 @@ For our shopping list application, the stateful resources we care about are the
 
     ```diff lang="ts"
     // packages/common/constructs/src/core/user-identity.ts
-    +this.userPool = this.createUserPool();
+    +this.userPool = this.createUserPool(mfa, mfaSecondFactor);
     -this.userPool = UserPool.fromUserPoolId(
     -  this,
     -  'UserPool',
@@ -108,7 +109,7 @@ For our shopping list application, the stateful resources we care about are the
 
     And then run a build
 
-    <NxCommands commands={["run-many --target build"]} />
+    <PackageManagerShortCommand commands={["build"]} />
 
 1. Use `cdk import` in your new application's `packages/infra` folder to see which resources we'll be prompted to import.
 
@@ -199,7 +200,7 @@ For our shopping list application, the stateful resources we care about are the
 
 1. Deploy the new application again to make sure that any changes to these existing resources (now managed by your new stack) are made:
 
-    <NxCommands commands={["deploy infra shopping-list-infra-sandbox/*"]} />
+    <NxCommands commands={['deploy-sandbox infra']} />
 
 1. Perform a full test of your new application again
 

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

@@ -14,7 +14,7 @@ The most commonly used components from Type Safe API are covered in the example
 
 #### APIs Modelled with OpenAPI
 
-The Nx Plugin for AWS supports APIs modelled in Smithy, but not those modelled directly OpenAPI. The <Link path="/guides/ts-smithy-api">`ts#smithy-api` generator</Link> is a good starting point which you can then modify. You can define your OpenAPI specification in the `model` project's `src` folder instead of Smithy, and modify the `build.Dockerfile` to use your desired code generation tool for clients/servers if they aren't available on NPM. If your desired tools are on NPM, you can just install them as dev dependencies to your Nx workspace and call them directly as Nx build targets.
+The Nx Plugin for AWS supports APIs modelled in Smithy, but not those modelled directly OpenAPI. The <Link path="/guides/ts-smithy-api">`ts#smithy-api` generator</Link> is a good starting point which you can then modify. You can define your OpenAPI specification in the `model` project's `src` folder instead of Smithy, and update the `model` project's `compile` target to run your desired code generation tool for clients/servers. If your desired tools are on NPM, you can install them as dev dependencies to your Nx workspace and call them directly as Nx build targets.
 
 ##### Backend
 
@@ -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.
 
@@ -153,7 +153,7 @@ const pythonLambdaHandler = new Function(this, 'PythonImplementation', {
   ...
 });
 
-new MyApi(this, 'MyApi', {
+new Api(this, 'MyApi', {
   integrations: Api.defaultIntegrations(this)
     .withOverrides({
       echo: {
@@ -167,7 +167,7 @@ new MyApi(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/prerequisites.mdx

@@ -1,7 +1,6 @@
 ---
 title: Prerequisites
 ---
-import Link from '@components/link.astro';
 import Snippet from '@components/snippet.astro';
 
 ### Required
@@ -11,7 +10,3 @@ import Snippet from '@components/snippet.astro';
 ### Recommended
 
 <Snippet name="recommended-prerequisites" parentHeading="Recommended" />
-
-:::tip[AI Assistant Setup]
-If you use an AI Assistant such as Kiro, Kiro CLI, Cursor, Claude Code or Codex, you may also wish to <Link path="/get_started/building-with-ai">install the Nx Plugin for AWS MCP server.</Link>
-:::

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/docs/snippets/recommended-prerequisites.mdx

@@ -1,7 +1,7 @@
 ---
 title: Recommended Prerequisites
 ---
-- [PNPM >= 11](https://pnpm.io/installation#using-npm) (you can also use [Yarn >= 4](https://yarnpkg.com/getting-started/install), [Bun >= 1](https://bun.sh/docs/installation), or [NPM >= 10](https://nodejs.org/en/learn/getting-started/an-introduction-to-the-npm-package-manager) if you prefer)
+- [PNPM >= 11](https://pnpm.io/installation#using-npm) (you can also use [Yarn >= 4](https://yarnpkg.com/getting-started/install), [Bun >= 1](https://bun.sh/docs/installation), or [NPM >= 11](https://nodejs.org/en/learn/getting-started/an-introduction-to-the-npm-package-manager) if you prefer)
   - verify by running `pnpm --version`, `yarn --version`, `bun --version` or `npm --version`
 - [AWS Credentials](https://docs.aws.amazon.com/sdkref/latest/guide/access.html) configured to your target AWS account are required to deploy your application (as well as for some local development workflows).
 - [Docker](https://www.docker.com/) or [Finch >= 1.6.0](https://runfinch.com/) is required for some generators. For Docker, [multi-platform builds](https://docs.docker.com/build/building/multi-platform/) must be set up; Finch supports [multi-platform builds](https://runfinch.com/docs/getting-started/building-images/#building-a-multi-architecture-container-image) out of the box.

package/docs/snippets/workspace-prerequisite.mdx

@@ -0,0 +1,8 @@
+---
+title: Workspace Prerequisite
+---
+import Link from '@components/link.astro';
+
+:::note[Start here]
+Generators run inside an Nx workspace with `@aws/nx-plugin` installed. If you don't have one yet, start by <Link path="guides/workspace">creating a workspace</Link>, or <Link path="get_started/existing-project">adding the plugin to an existing project</Link>.
+:::

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-rc.98",
+  "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": {