@aws/nx-plugin-mcp 1.0.0-rc.0 → 1.0.0-rc.2

package/docs/guides/trpc.mdx

@@ -4,6 +4,7 @@ description: Reference documentation for tRPC
 generator: ts#trpc-api
 when:
   framework: [trpc]
+  infra: [rest-lambda, http-lambda]
 ---
 import { FileTree, Tabs, TabItem } from '@astrojs/starlight/components';
 import Link from '@components/link.astro';
@@ -33,7 +34,7 @@ You can generate a new tRPC API in two ways:
 <Snippet name="api/api-choice-note" />
 
 :::tip[API Type]
-Select `ServerlessApiGatewayRestApi` (default) as your `computeType` if you would like to use [tRPC Subscriptions](https://trpc.io/docs/server/subscriptions) to stream responses.
+Select `rest-lambda` (default) as your `infra` if you would like to use [tRPC Subscriptions](https://trpc.io/docs/server/subscriptions) to stream responses.
 :::
 
 :::tip[Integration Pattern]
@@ -151,10 +152,10 @@ The use of `query` to define the implementation indicates that the operation is
 
 If you add a new procedure, make sure you register it by adding it to the router in `src/router.ts`.
 
-<OptionFilter when={{ computeType: 'ServerlessApiGatewayRestApi' }} description="Streaming subscriptions — REST API only, uses SSE">
+<OptionFilter when={{ infra: 'rest-lambda' }} description="Streaming subscriptions — REST API only, uses SSE">
 ### Subscriptions (Streaming)
 
-tRPC subscriptions allow you to stream data from the server to the client using [Server-Sent Events (SSE)](https://developer.mozilla.org/en-US/docs/Web/API/Server-sent_events). When you select `ServerlessApiGatewayRestApi` as your compute type, the generator automatically configures the infrastructure required for streaming, as well as a streaming Lambda handler and the `ZodAsyncIterable` schema helper.
+tRPC subscriptions allow you to stream data from the server to the client using [Server-Sent Events (SSE)](https://developer.mozilla.org/en-US/docs/Web/API/Server-sent_events). When you select `rest-lambda` as your compute type, the generator automatically configures the infrastructure required for streaming, as well as a streaming Lambda handler and the `ZodAsyncIterable` schema helper.
 
 To define a subscription procedure, use the `.subscription` method with an async generator function. Use the `ZodAsyncIterable` helper from `src/schema/z-async-iterable.ts` to define the output schema:
 
@@ -290,7 +291,7 @@ You can add additional values to the context provided to procedures by implement
 
 As an example, let's implement some middlware to extract some details about the calling user from our API in `src/middleware/identity.ts`.
 
-<OptionFilter when={{ auth: 'IAM' }} description="Identity middleware example for IAM-authenticated APIs">
+<OptionFilter when={{ auth: 'iam' }} description="Identity middleware example for IAM-authenticated APIs">
 This example walks through identity middleware for `IAM` authentication. We look up the caller in Cognito using the sub extracted from the API Gateway event.
 
 First, we define what we'll add to the context:
@@ -326,7 +327,7 @@ export const createIdentityPlugin = () => {
 In our case, we want to extract details about the calling Cognito user. We'll do that by extracting the user's subject ID (or "sub") from the API Gateway event, and retrieving user details from Cognito. The implementation varies depending on whether the event was provided to our function by a REST API or an HTTP API:
 
 <Tabs syncKey="http-rest">
-<TabItem label="REST API" _filter={{ computeType: 'ServerlessApiGatewayRestApi' }}>
+<TabItem label="REST API" _filter={{ infra: 'rest-lambda' }}>
 ```ts
 import { CognitoIdentityProvider } from '@aws-sdk/client-cognito-identity-provider';
 import { initTRPC, TRPCError } from '@trpc/server';
@@ -389,7 +390,7 @@ export const createIdentityPlugin = () => {
 };
 ```
 </TabItem>
-<TabItem label="HTTP API" _filter={{ computeType: 'ServerlessApiGatewayHttpApi' }}>
+<TabItem label="HTTP API" _filter={{ infra: 'http-lambda' }}>
 ```ts
 import { CognitoIdentityProvider } from '@aws-sdk/client-cognito-identity-provider';
 import { initTRPC, TRPCError } from '@trpc/server';
@@ -461,8 +462,8 @@ export const createIdentityPlugin = () => {
 </Tabs>
 </OptionFilter>
 
-<OptionFilter when={{ auth: 'Cognito' }} description="Identity middleware example for Cognito-authenticated APIs">
-When you deploy with `auth: 'Cognito'`, the API Gateway Cognito User Pools authorizer verifies the JWT that the caller supplies in the `Authorization` header and places the verified claims on the Lambda event at `event.requestContext.authorizer.claims`. Our middleware just reads those claims — no extra AWS SDK calls, no manual JWT verification.
+<OptionFilter when={{ auth: 'cognito' }} description="Identity middleware example for Cognito-authenticated APIs">
+When you deploy with `auth: 'cognito'`, the API Gateway Cognito User Pools authorizer verifies the JWT that the caller supplies in the `Authorization` header and places the verified claims on the Lambda event at `event.requestContext.authorizer.claims`. Our middleware just reads those claims — no extra AWS SDK calls, no manual JWT verification.
 
 First, we define what we'll add to the context:
 
@@ -553,7 +554,7 @@ The tRPC API generator creates CDK or Terraform infrastructure as code based on
 <Fragment slot="cdk">
 The CDK construct for deploying your API lives in the `common/constructs` folder. You can consume this in a CDK application, for example:
 
-<OptionFilter when={{ auth: ['IAM', 'Custom'] }} description="CDK usage for IAM or Custom authentication">
+<OptionFilter when={{ auth: ['iam', 'custom'] }} description="CDK usage for IAM or Custom authentication">
 ```ts {6-8}
 import { MyApi } from ':my-scope/common-constructs';
 
@@ -572,7 +573,7 @@ When using `Custom` auth, the construct creates a Lambda Authorizer internally f
 :::
 </OptionFilter>
 
-<OptionFilter when={{ auth: 'Cognito' }} description="CDK usage with Cognito authentication — pass the identity construct">
+<OptionFilter when={{ auth: 'cognito' }} description="CDK usage with Cognito authentication — pass the identity construct">
 ```ts {6,9}
 import { MyApi, UserIdentity } from ':my-scope/common-constructs';
 
@@ -601,7 +602,7 @@ The Terraform modules for deploying your API are in the `common/terraform` folde
 
 The API module stages its Lambda deployment zip in a shared S3 asset bucket — see the <Link path="/guides/terraform-project">Terraform infrastructure guide</Link> for details. Instantiate the `core/asset-bucket` module once per deployment and pass its `bucket_name` output into every API / Lambda module via the `asset_bucket_name` input:
 
-<OptionFilter when={{ auth: ['IAM', 'Custom'] }} description="Terraform usage for IAM or Custom authentication">
+<OptionFilter when={{ auth: ['iam', 'custom'] }} description="Terraform usage for IAM or Custom authentication">
 ```hcl {1-3, 8}
 module "asset_bucket" {
   source = "../../common/terraform/src/core/asset-bucket"
@@ -628,7 +629,7 @@ module "my_api" {
 ```
 </OptionFilter>
 
-<OptionFilter when={{ auth: 'Cognito' }} description="Terraform usage with Cognito authentication — supply user pool and client">
+<OptionFilter when={{ auth: 'cognito' }} description="Terraform usage with Cognito authentication — supply user pool and client">
 ```hcl {1-3, 8-9}
 module "asset_bucket" {
   source = "../../common/terraform/src/core/asset-bucket"
@@ -711,7 +712,7 @@ module "my_api" {
 }
 ```
 
-<OptionFilter when={{ auth: 'Custom' }} description="Custom Lambda Authorizer usage with Terraform">
+<OptionFilter when={{ auth: 'custom' }} description="Custom Lambda Authorizer usage with Terraform">
 :::caution[Custom Lambda Authorizer]
 When using `Custom` auth, your API is protected by a Lambda Authorizer that **denies all requests by default**. You must implement your authorization logic in the generated `src/authorizer.ts` file before your API will accept any traffic.
 :::
@@ -719,7 +720,7 @@ When using `Custom` auth, your API is protected by a Lambda Authorizer that **de
 </Fragment>
 </Infrastructure>
 
-<OptionFilter when={{ computeType: 'ServerlessApiGatewayRestApi' }} description="WAF — REST APIs get a WAF Web ACL by default">
+<OptionFilter when={{ infra: 'rest-lambda' }} description="WAF — REST APIs get a WAF Web ACL by default">
 ### WAF
 
 <Snippet name="api/waf-configuration" parentHeading="WAF" />
@@ -733,7 +734,7 @@ When using `Custom` auth, your API is protected by a Lambda Authorizer that **de
 If you selected CDK for your `iacProvider`, when you add or remove a procedure in your tRPC API, these changes will be reflected immediately in the CDK construct without the need to rebuild.
 :::
 
-<OptionFilter when={{ auth: 'IAM' }} description="Granting API invoke access — IAM-authenticated APIs only">
+<OptionFilter when={{ auth: 'iam' }} description="Granting API invoke access — IAM-authenticated APIs only">
 ### Granting Access (IAM Only)
 
 You can grant access to your API as follows:

package/docs/guides/ts-agent.mdx

@@ -47,7 +47,7 @@ First use the <Link path="/guides/typescript-project">`ts#project`</Link> genera
 
 The generator will add the following files to your existing TypeScript project. The files generated depend on the chosen `protocol`:
 
-<OptionFilter when={{ protocol: 'HTTP' }} description="tRPC-over-WebSocket layout">
+<OptionFilter when={{ protocol: 'http' }} description="tRPC-over-WebSocket layout">
 ### HTTP Protocol (default)
 
 <FileTree>
@@ -60,13 +60,13 @@ The generator will add the following files to your existing TypeScript project.
         - agent.ts Main agent definition with sample tools
         - client.ts Vended client for invoking your agent
         - agent-core-trpc-client.ts Client factory for connecting to agents on AgentCore Runtime
-        - Dockerfile Entry point for hosting your agent (excluded when `computeType` is set to `None`)
+        - Dockerfile Entry point for hosting your agent (excluded when `infra` is set to `None`)
     - package.json Updated with Strands dependencies
     - project.json Updated with agent serve targets
 </FileTree>
 </OptionFilter>
 
-<OptionFilter when={{ protocol: 'A2A' }} description="Strands A2A Express server layout">
+<OptionFilter when={{ protocol: 'a2a' }} description="Strands A2A Express server layout">
 ### A2A Protocol
 
 The entry point uses the [Strands A2A Express Server](https://strandsagents.com/docs/user-guide/concepts/multi-agent/agent-to-agent) instead of tRPC:
@@ -77,13 +77,13 @@ The entry point uses the [Strands A2A Express Server](https://strandsagents.com/
       - agent/ (or custom name if specified)
         - index.ts A2A Express server entry point
         - agent.ts Main agent definition with sample tools
-        - Dockerfile Entry point for hosting your agent (excluded when `computeType` is set to `None`)
+        - Dockerfile Entry point for hosting your agent (excluded when `infra` is set to `None`)
     - package.json Updated with Strands and Express dependencies
     - project.json Updated with agent serve targets
 </FileTree>
 </OptionFilter>
 
-<OptionFilter when={{ protocol: 'AG-UI' }} description="AG-UI SSE-over-POST server layout">
+<OptionFilter when={{ protocol: 'ag-ui' }} description="AG-UI SSE-over-POST server layout">
 ### AG-UI Protocol
 
 The entry point uses [`@ag-ui/aws-strands`](https://www.npmjs.com/package/@ag-ui/aws-strands) to expose the agent via the [AG-UI protocol](https://docs.ag-ui.com/) (SSE over POST), compatible with [CopilotKit](https://docs.copilotkit.ai/aws-strands):
@@ -94,7 +94,7 @@ The entry point uses [`@ag-ui/aws-strands`](https://www.npmjs.com/package/@ag-ui
       - agent/ (or custom name if specified)
         - index.ts AG-UI server entry point (Express + SSE)
         - agent.ts Main agent definition with sample tools
-        - Dockerfile Entry point for hosting your agent (excluded when `computeType` is set to `None`)
+        - Dockerfile Entry point for hosting your agent (excluded when `infra` is set to `None`)
     - package.json Updated with Strands and AG-UI dependencies
     - project.json Updated with agent serve targets
 </FileTree>
@@ -102,7 +102,7 @@ The entry point uses [`@ag-ui/aws-strands`](https://www.npmjs.com/package/@ag-ui
 
 ### Infrastructure
 
-<OptionFilter when={{ computeType: 'BedrockAgentCoreRuntime' }} description="Bedrock AgentCore Runtime deployment">
+<OptionFilter when={{ infra: 'agentcore' }} description="Bedrock AgentCore Runtime deployment">
 <Snippet name="shared-constructs" />
 
 For deploying your Agent, the following files are generated:
@@ -132,8 +132,8 @@ For deploying your Agent, the following files are generated:
 </Infrastructure>
 </OptionFilter>
 
-<OptionFilter when={{ computeType: 'None' }} description="No infrastructure is vended for computeType=None">
-If you selected `None` for `computeType`, no CDK constructs or Terraform modules are generated — the Agent can only be run locally. The `auth` option is ignored in this mode since there is no hosted endpoint to authenticate.
+<OptionFilter when={{ infra: 'none' }} description="No infrastructure is vended for infra=none">
+If you selected `none` for `infra`, no CDK constructs or Terraform modules are generated — the Agent can only be run locally. The `auth` option is ignored in this mode since there is no hosted endpoint to authenticate.
 </OptionFilter>
 
 #### Architecture
@@ -152,7 +152,7 @@ Your agent's server protocol determines how it communicates. You can choose betw
 
 The protocol is set in the CDK/Terraform infrastructure, and the application code is generated accordingly.
 
-<OptionFilter when={{ protocol: 'HTTP' }} description="tRPC over WebSocket details">
+<OptionFilter when={{ protocol: 'http' }} description="tRPC over WebSocket details">
 ### tRPC over WebSocket (HTTP protocol)
 
 The TypeScript Agent uses [tRPC](https://trpc.io/) over WebSocket, leveraging [AgentCore's bidirectional streaming support](https://docs.aws.amazon.com/bedrock-agentcore/latest/devguide/runtime-get-started-websocket.html) to enable real-time, type-safe communication between clients and your agent.
@@ -239,7 +239,7 @@ For other MCP servers, please refer to the [Strands Documentation](https://stran
 
 For a more in-depth guide to writing Strands agents, refer to the [Strands documentation](https://strandsagents.com/docs/user-guide/quickstart/overview/).
 
-<OptionFilter when={{ protocol: 'A2A' }} description="A2A Express server details">
+<OptionFilter when={{ protocol: 'a2a' }} description="A2A Express server details">
 ## A2A Server (A2A protocol)
 
 The generated `index.ts` mounts the [Strands A2A Express Server](https://strandsagents.com/docs/user-guide/concepts/multi-agent/agent-to-agent) onto an Express app so the generated agent exposes the A2A protocol endpoints alongside a `/ping` health check. When deployed to AgentCore, the entry point resolves the runtime's public ARN from AppConfig and advertises it in the agent card.
@@ -247,7 +247,7 @@ The generated `index.ts` mounts the [Strands A2A Express Server](https://strands
 Most users will not need to modify this file — edit `agent.ts` to change tools or the system prompt. A2A agents listen on port `9000` (vs `8080` for HTTP), which the generated Dockerfile and infrastructure are already configured for.
 </OptionFilter>
 
-<OptionFilter when={{ protocol: 'AG-UI' }} description="AG-UI server details">
+<OptionFilter when={{ protocol: 'ag-ui' }} description="AG-UI server details">
 ## AG-UI Server (AG-UI protocol)
 
 The generated `index.ts` wraps your Strands `Agent` in an [`@ag-ui/aws-strands`](https://www.npmjs.com/package/@ag-ui/aws-strands) `StrandsAgent` and creates an Express app via `createStrandsApp()`. The resulting app exposes a single POST endpoint that streams [AG-UI](https://docs.ag-ui.com/) events over Server-Sent Events (SSE), as well as `/ping` for the AgentCore runtime health check.
@@ -275,7 +275,7 @@ The generator configures a `<your-agent-name>-chat` Nx target that depends on `<
 
 For **HTTP** (tRPC over WebSocket) agents, the generator also emits a tiny `scripts/<your-agent-name>/chat.ts` that wraps the generated `<Agent>Client.local({ url })` so you can customize it as you evolve the agent's input shape.
 
-<OptionFilter when={{ computeType: 'BedrockAgentCoreRuntime' }} description="Bedrock AgentCore Runtime deployment details">
+<OptionFilter when={{ infra: 'agentcore' }} description="Bedrock AgentCore Runtime deployment details">
 ## Deploying Your Agent to Bedrock AgentCore Runtime
 
 <Snippet name="agent/bedrock-deployment" parentHeading="Deploying Your Agent to Bedrock AgentCore Runtime" />
@@ -305,7 +305,7 @@ For more details, refer to the [AgentCore documentation on observability](https:
 
 Agent communication is transmitted via tRPC over WebSocket. As such, it's recommended to use the generated type-safe client factory in `client.ts`.
 
-<OptionFilter when={{ protocol: 'HTTP' }} description="tRPC-over-WebSocket client factory invocation details">
+<OptionFilter when={{ protocol: 'http' }} description="tRPC-over-WebSocket client factory invocation details">
 ### Invoke the Local Server
 
 You can invoke a locally running agent using the `.local` factory method from the client factory.
@@ -340,7 +340,7 @@ The client factory uses HTTP headers in the WebSocket handshake to authenticate
 :::
 
 <Tabs syncKey="auth">
-<TabItem label="IAM" _filter={{ auth: 'IAM' }}>
+<TabItem label="IAM" _filter={{ auth: 'iam' }}>
 ##### IAM Authentication
 
 You can invoke your deployed agent by passing its ARN to the `withIamAuth` factory method:
@@ -364,7 +364,7 @@ This will use the default AWS credential provider chain to authenticate requests
 :::
 </TabItem>
 
-<TabItem label="Cognito" _filter={{ auth: 'Cognito' }}>
+<TabItem label="Cognito" _filter={{ auth: 'cognito' }}>
 ##### JWT / Cognito Authentication
 
 Use the `withJwtAuth` factory method to authenticate with the JWT / Cognito access token.
@@ -415,7 +415,7 @@ For invoking your Agent from a React website, you can make use of the <Link path
 Refer to the <Link path="/guides/connection/react-ts-agent">`connection` generator guide</Link> for details about how the connection is set up.
 </OptionFilter>
 
-<OptionFilter when={{ protocol: 'A2A' }} description="A2A delegation details">
+<OptionFilter when={{ protocol: 'a2a' }} description="A2A delegation details">
 ### Invoking an A2A Agent as a Tool
 
 To delegate work from this agent to a remote A2A agent (either <Link path="/guides/ts-agent">TypeScript</Link> or <Link path="/guides/py-agent">Python</Link>), use the <Link path="/guides/connection/ts-agent-a2a">`connection` generator</Link>. It vends a SigV4-authenticated client for the target agent and AST-transforms this agent's `agent.ts` to register the remote A2A agent as a Strands `tool`.
@@ -425,7 +425,7 @@ To delegate work from this agent to a remote A2A agent (either <Link path="/guid
 Refer to the <Link path="/guides/connection/ts-agent-a2a">`connection` generator guide</Link> for details about how the connection is set up.
 </OptionFilter>
 
-<OptionFilter when={{ protocol: 'AG-UI' }} description="AG-UI / React connection details">
+<OptionFilter when={{ protocol: 'ag-ui' }} description="AG-UI / React connection details">
 ### Invoking an AG-UI Agent
 
 To invoke your AG-UI agent from a React website, use the <Link path="/guides/connection/react-agui">`connection` generator</Link>, which wires up a [CopilotKit](https://docs.copilotkit.ai/aws-strands) client configured for your deployed agent with the correct authentication (IAM or Cognito).

package/docs/guides/ts-lambda-function.mdx

@@ -179,8 +179,8 @@ export const handler = middy()
 
 ### Type Safety
 
-<OptionFilter not when={{ eventSource: 'Any' }} description="eventSource provides a typed Zod schema for the incoming event">
-If you chose an `eventSource` when generating your lambda function, your function is instrumented with the [`parser` middleware from AWS Lambda Powertools](https://docs.powertools.aws.dev/lambda/typescript/latest/utilities/parser/). For example:
+<OptionFilter not when={{ event: 'Any' }} description="event provides a typed Zod schema for the incoming event">
+If you chose an `event` when generating your lambda function, your function is instrumented with the [`parser` middleware from AWS Lambda Powertools](https://docs.powertools.aws.dev/lambda/typescript/latest/utilities/parser/). For example:
 
 ```typescript {4}
 export const myFunction = async (
@@ -205,8 +205,8 @@ If you have custom data nested within an event, for example a DynamoDB stream or
 :::
 </OptionFilter>
 
-<OptionFilter when={{ eventSource: 'Any' }} description="eventSource=Any — no parser middleware, event is typed as `any`">
-If you selected `Any` for your `eventSource`, the `parser` middleware is not wired in and the `event` parameter is typed as `any`. Regenerate the function with a specific `eventSource` if you want compile-time type safety and runtime validation.
+<OptionFilter when={{ event: 'Any' }} description="event=Any — no parser middleware, event is typed as `any`">
+If you selected `Any` for your `event`, the `parser` middleware is not wired in and the `event` parameter is typed as `any`. Regenerate the function with a specific `event` if you want compile-time type safety and runtime validation.
 </OptionFilter>
 
 ## Bundling

package/docs/guides/ts-mcp-server.mdx

@@ -53,21 +53,21 @@ The generator will add the following files to your existing TypeScript project:
           - divide.ts Sample tool
         - resources/
           - sample-guidance.ts Sample resource
-        - Dockerfile Entry point for hosting your MCP server (excluded when `computeType` is set to `None`)
+        - Dockerfile Entry point for hosting your MCP server (excluded when `infra` is set to `None`)
     - package.json Updated with bin entry and MCP dependencies
     - project.json Updated with MCP server serve target
 </FileTree>
 
 ### Infrastructure
 
-<OptionFilter when={{ computeType: 'BedrockAgentCoreRuntime' }} description="Bedrock AgentCore Runtime deployment">
+<OptionFilter when={{ infra: 'agentcore' }} description="Bedrock AgentCore Runtime deployment">
 <Snippet name="shared-constructs" />
 
 <Snippet name="mcp/shared-constructs" />
 </OptionFilter>
 
-<OptionFilter when={{ computeType: 'None' }} description="No infrastructure is vended for computeType=None">
-If you selected `None` for `computeType`, no CDK constructs or Terraform modules are generated — the MCP server is configured for local STDIO / HTTP use only. The `auth` option is ignored in this mode since there is no hosted endpoint to authenticate.
+<OptionFilter when={{ infra: 'none' }} description="No infrastructure is vended for infra=none">
+If you selected `none` for `infra`, no CDK constructs or Terraform modules are generated — the MCP server is configured for local STDIO / HTTP use only. The `auth` option is ignored in this mode since there is no hosted endpoint to authenticate.
 </OptionFilter>
 
 #### Architecture
@@ -146,7 +146,7 @@ If you would like to run your MCP server locally using [Streamable HTTP transpor
 
 This command uses `tsx --watch` to automatically restart the server when files change.
 
-<OptionFilter when={{ computeType: 'BedrockAgentCoreRuntime' }} description="Bedrock AgentCore Runtime deployment details">
+<OptionFilter when={{ infra: 'agentcore' }} description="Bedrock AgentCore Runtime deployment details">
 ## Deploying Your MCP Server to Bedrock AgentCore Runtime
 
 <Snippet name="mcp/bedrock-deployment" parentHeading="Deploying Your MCP Server to Bedrock AgentCore Runtime" />

package/docs/guides/ts-rdb.mdx

@@ -528,7 +528,7 @@ By default, the generated local Docker database image matches the default Aurora
 
 The local database image is configured in the generated database project's `serve-local` target in `project.json`. Update the image argument passed to `scripts/docker-start.ts` when you change engine versions.
 
-<OptionFilter when={{ engine: 'PostgreSQL' }}>
+<OptionFilter when={{ engine: 'postgres' }}>
 <Infrastructure>
 <Fragment slot="cdk">
 
@@ -554,7 +554,7 @@ module "my_database" {
 </Infrastructure>
 </OptionFilter>
 
-<OptionFilter when={{ engine: 'MySQL' }}>
+<OptionFilter when={{ engine: 'mysql' }}>
 <Infrastructure>
 <Fragment slot="cdk">
 
@@ -689,7 +689,7 @@ module "my_database" {
 
 ## Limitations
 
-<OptionFilter when={{ engine: 'MySQL' }}>
+<OptionFilter when={{ engine: 'mysql' }}>
 
 ### MySQL: API Gateway Streaming Mode
 

package/docs/guides/ts-smithy-api.mdx

@@ -4,6 +4,7 @@ description: Reference documentation for Smithy TypeScript API
 generator: ts#smithy-api
 when:
   framework: [smithy]
+  infra: [rest-lambda]
 ---
 
 import { FileTree } from '@astrojs/starlight/components';
@@ -462,7 +463,7 @@ This sets up:
 
 <Snippet name="api/cors-configuration-cdk-note" />
 
-<OptionFilter when={{ auth: 'Cognito' }} description="Cognito identity construct wiring">
+<OptionFilter when={{ auth: 'cognito' }} description="Cognito identity construct wiring">
 :::note[Cognito Authentication]
 If you selected `Cognito` authentication, you will need to supply the `identity` property to the API construct:
 
@@ -485,7 +486,7 @@ The `UserIdentity` construct can be generated using the <Link path="/guides/reac
 :::
 </OptionFilter>
 
-<OptionFilter when={{ auth: 'Custom' }} description="Custom Lambda Authorizer CDK usage">
+<OptionFilter when={{ auth: 'custom' }} description="Custom Lambda Authorizer CDK usage">
 :::caution[Custom Lambda Authorizer]
 When using `Custom` auth, the construct creates a Lambda Authorizer internally from the generated `src/authorizer.ts` file, which **denies all requests by default**. You must implement your authorization logic in that file before your API will accept any traffic.
 :::
@@ -532,7 +533,7 @@ This sets up:
 
 <Snippet name="api/cors-configuration-terraform-note" />
 
-<OptionFilter when={{ auth: 'Cognito' }} description="Cognito module wiring">
+<OptionFilter when={{ auth: 'cognito' }} description="Cognito module wiring">
 :::note[Cognito Authentication]
 If you selected `Cognito` authentication, you will need to supply the Cognito configuration:
 
@@ -556,7 +557,7 @@ module "my_api" {
 :::
 </OptionFilter>
 
-<OptionFilter when={{ auth: 'Custom' }} description="Custom Lambda Authorizer usage with Terraform">
+<OptionFilter when={{ auth: 'custom' }} description="Custom Lambda Authorizer usage with Terraform">
 :::caution[Custom Lambda Authorizer]
 When using `Custom` auth, your API is protected by a Lambda Authorizer that **denies all requests by default**. You must implement your authorization logic in the generated `src/authorizer.ts` file before your API will accept any traffic.
 :::
@@ -618,7 +619,7 @@ We do not support type-safe integrations for Terraform, and therefore no code ge
 </Fragment>
 </Infrastructure>
 
-<OptionFilter when={{ auth: 'IAM' }} description="IAM-authenticated APIs only">
+<OptionFilter when={{ auth: 'iam' }} description="IAM-authenticated APIs only">
 ### Granting Access (IAM Only)
 
 If you selected `IAM` authentication, you can use the `grantInvokeAccess` method to grant access to your API:

package/docs/guides/workspace.mdx

@@ -167,7 +167,7 @@ import { AwsNxPluginConfig } from '@aws/nx-plugin';
 
 export default {
   iac: {
-    provider: 'CDK', // or 'Terraform'
+    provider: 'cdk', // or 'terraform'
   },
   containers: {
     engine: 'docker', // or 'finch'
@@ -175,7 +175,7 @@ export default {
 } satisfies AwsNxPluginConfig;
 ```
 
-- **`iac.provider`** — the default infrastructure-as-code provider (`CDK` or `Terraform`) used by generators that emit infrastructure (e.g. `ts#infra`, `ts#trpc-api`, `py#fast-api`). Generators that accept an `--iacProvider` flag default to `Inherit`, which reads this value.
+- **`iac.provider`** — the default infrastructure-as-code provider (`cdk` or `terraform`) used by generators that emit infrastructure (e.g. `ts#infra`, `ts#trpc-api`, `py#fast-api`). Generators that accept an `--iac` flag default to `inherit`, which reads this value.
 - **`containers.engine`** — the container CLI (`docker` or `finch`) baked into generated build/push/login commands. CDK image-asset builds also pick this up via the `CDK_DOCKER` environment variable. See the <Link path="guides/docker-bundling">Docker bundling guide</Link> for details.
 
 You can edit either setting at any time — subsequent generator runs will pick up the new value.

package/docs/snippets/agent/architecture.mdx

@@ -3,8 +3,8 @@ title: Agent Architecture
 ---
 import { Tabs, TabItem } from '@astrojs/starlight/components';
 
-<Tabs syncKey="computeType">
-<TabItem label="Bedrock AgentCore Runtime" _filter={{ computeType: 'BedrockAgentCoreRuntime' }}>
+<Tabs syncKey="infra">
+<TabItem label="Bedrock 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.
 
@@ -44,9 +44,9 @@ agentcore -> bedrock: InvokeModel
 agentcore -> cw
 ```
 </TabItem>
-<TabItem label="None (local only)" _filter={{ computeType: 'None' }}>
+<TabItem label="None (local only)" _filter={{ infra: 'none' }}>
 
-With `computeType: None`, no AWS infrastructure is generated. The agent runs as a local process and calls Amazon Bedrock for model inference.
+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

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

@@ -6,7 +6,7 @@ import Infrastructure from '@components/infrastructure.astro';
 
 ### Infrastructure as Code
 
-If you selected `BedrockAgentCoreRuntime` for `computeType`, the relevant CDK or Terraform infrastructure is generated which you can use to deploy your Agent to [Amazon Bedrock AgentCore Runtime](https://docs.aws.amazon.com/bedrock-agentcore/latest/devguide/agents-tools-runtime.html).
+If you selected `agentcore` for `infra`, the relevant CDK or Terraform infrastructure is generated which you can use to deploy your Agent to [Amazon Bedrock AgentCore Runtime](https://docs.aws.amazon.com/bedrock-agentcore/latest/devguide/agents-tools-runtime.html).
 
 <Infrastructure>
 <Fragment slot="cdk">

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

@@ -6,7 +6,7 @@ import { Tabs, TabItem } from '@astrojs/starlight/components';
 The deployed application has the following architecture:
 
 <Tabs syncKey="http-rest">
-<TabItem label="REST API" _filter={{ computeType: 'ServerlessApiGatewayRestApi' }}>
+<TabItem label="REST API" _filter={{ infra: 'rest-lambda' }}>
 ```d2 inline=true
 direction: right
 
@@ -51,7 +51,7 @@ lambda -> xray
 
 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={{ computeType: 'ServerlessApiGatewayHttpApi' }}>
+<TabItem label="HTTP API" _filter={{ infra: 'http-lambda' }}>
 ```d2 inline=true
 direction: right
 

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

@@ -306,7 +306,7 @@ Edit `packages/common/terraform/src/app/apis/my-api/my-api.tf`:
 3. **Create specific integrations and routes** for each operation, reusing the same ZIP bundle:
 
 <Tabs syncKey="http-rest">
-<TabItem label="HTTP API" _filter={{ computeType: 'ServerlessApiGatewayHttpApi' }}>
+<TabItem label="HTTP API" _filter={{ infra: 'http-lambda' }}>
 
 ```diff
 # packages/common/terraform/src/app/apis/my-api/my-api.tf
@@ -429,7 +429,7 @@ Edit `packages/common/terraform/src/app/apis/my-api/my-api.tf`:
 + }
 ```
 </TabItem>
-<TabItem label="REST API" _filter={{ computeType: 'ServerlessApiGatewayRestApi' }}>
+<TabItem label="REST API" _filter={{ infra: 'rest-lambda' }}>
 
 ```diff
 # packages/common/terraform/src/app/apis/my-api/my-api.tf

package/docs/snippets/lambda-function/deploying-your-function.mdx

@@ -30,7 +30,7 @@ This sets up:
 This function can then be used as a target for any lambda [event source](https://docs.powertools.aws.dev/lambda/typescript/latest/utilities/parser/):
 
 :::note[Event Source Matching]
-Ensure the event source matches the selected `eventSource` option to ensure the event is properly handled within your handler function.
+Ensure the event source matches the selected `event` option to ensure the event is properly handled within your handler function.
 :::
 
 The example below demonstrates the CDK code for invoking your lambda function on a schedule using EventBridge:
@@ -112,7 +112,7 @@ resource "aws_lambda_permission" "allow_eventbridge" {
 ```
 
 :::note[Event Source Matching]
-Ensure the event source matches the selected `eventSource` option to ensure the event is properly handled within your handler function.
+Ensure the event source matches the selected `event` option to ensure the event is properly handled within your handler function.
 :::
 </Fragment>
 </Infrastructure>

package/docs/snippets/mcp/architecture.mdx

@@ -3,8 +3,8 @@ title: MCP Server Architecture
 ---
 import { Tabs, TabItem } from '@astrojs/starlight/components';
 
-<Tabs syncKey="computeType">
-<TabItem label="Bedrock AgentCore Runtime" _filter={{ computeType: 'BedrockAgentCoreRuntime' }}>
+<Tabs syncKey="infra">
+<TabItem label="Bedrock 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).
 
@@ -36,9 +36,9 @@ ecr -> agentcore: Container\nimage
 agentcore -> cw
 ```
 </TabItem>
-<TabItem label="None (local only)" _filter={{ computeType: 'None' }}>
+<TabItem label="None (local only)" _filter={{ infra: 'none' }}>
 
-With `computeType: 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.
+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

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

@@ -6,7 +6,7 @@ import Infrastructure from '@components/infrastructure.astro';
 
 ### Infrastructure as Code
 
-If you selected `BedrockAgentCoreRuntime` for `computeType`, the relevant CDK or Terraform infrastructure is generated which you can use to deploy your MCP server to [Amazon Bedrock AgentCore Runtime](https://docs.aws.amazon.com/bedrock-agentcore/latest/devguide/agents-tools-runtime.html).
+If you selected `agentcore` for `infra`, the relevant CDK or Terraform infrastructure is generated which you can use to deploy your MCP server to [Amazon Bedrock AgentCore Runtime](https://docs.aws.amazon.com/bedrock-agentcore/latest/devguide/agents-tools-runtime.html).
 
 <Infrastructure>
 <Fragment slot="cdk">

package/generators.json

@@ -100,7 +100,8 @@
       "factory": "./src/py/mcp-server/generator",
       "schema": "./src/py/mcp-server/schema.json",
       "description": "Generate a Python Model Context Protocol (MCP) server for providing context to Large Language Models",
-      "metric": "g24"
+      "metric": "g24",
+      "guidePages": ["py-mcp-server"]
     },
     "py#project": {
       "factory": "./src/py/project/generator",
@@ -113,7 +114,8 @@
       "factory": "./src/py/agent/generator",
       "schema": "./src/py/agent/schema.json",
       "description": "Add an AI Agent to a Python project",
-      "metric": "g25"
+      "metric": "g25",
+      "guidePages": ["py-agent"]
     },
     "py#agent#mcp-connection": {
       "factory": "./src/py/agent/mcp-connection/generator",
@@ -182,7 +184,8 @@
       "factory": "./src/ts/mcp-server/generator",
       "schema": "./src/ts/mcp-server/schema.json",
       "description": "Generate a TypeScript Model Context Protocol (MCP) server for providing context to Large Language Models",
-      "metric": "g18"
+      "metric": "g18",
+      "guidePages": ["ts-mcp-server"]
     },
     "ts#nx-generator": {
       "factory": "./src/ts/nx-generator/generator",
@@ -252,7 +255,8 @@
       "factory": "./src/ts/agent/generator",
       "schema": "./src/ts/agent/schema.json",
       "description": "Add an AI Agent to a TypeScript project",
-      "metric": "g30"
+      "metric": "g30",
+      "guidePages": ["ts-agent"]
     },
     "ts#agent#mcp-connection": {
       "factory": "./src/ts/agent/mcp-connection/generator",
@@ -315,7 +319,8 @@
       "factory": "./src/ts/rdb/generator",
       "schema": "./src/ts/rdb/schema.json",
       "description": "Create a relational database project",
-      "metric": "g38"
+      "metric": "g38",
+      "guidePages": ["ts-rdb"]
     },
     "ts#rdb#smithy-connection": {
       "factory": "./src/ts/rdb/smithy-connection/generator",

package/package.json

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