@aws/nx-plugin-mcp 1.0.0-rc.57 → 1.0.0-rc.59

package/docs/guides/connection/react-agentcore-gateway.mdx

@@ -0,0 +1,112 @@
+---
+title: React Website to AgentCore Gateway
+description: Connect a React website to agents through an AgentCore Gateway
+when:
+  sourceType: ts#react-website
+  targetType: agentcore-gateway
+---
+import { FileTree } from '@astrojs/starlight/components';
+import Link from '@components/link.astro';
+import RunGenerator from '@components/run-generator.astro';
+import GeneratorParameters from '@components/generator-parameters.astro';
+import NxCommands from '@components/nx-commands.astro';
+import Infrastructure from '@components/infrastructure.astro';
+
+The `connection` generator can connect a <Link path="guides/react-website">React website</Link> to the agents fronted by an <Link path="guides/agentcore-gateway">AgentCore Gateway</Link> generated with `protocol: http`.
+
+The browser talks only to the Gateway — requests to `<gatewayUrl>/<targetName>/invocations` are proxied to the agent runtime behind it. Because the website never needs to reach the runtimes directly, the agents can be deployed inside a VPC, with the Gateway as the single governed entry point providing authentication and observability.
+
+## Prerequisites
+
+Before using this generator, ensure you have:
+
+1. A <Link path="guides/react-website">React website</Link> project
+2. An <Link path="guides/agentcore-gateway">`agentcore-gateway`</Link> project generated with `protocol: http`
+3. At least one AG-UI or HTTP agent attached to the Gateway via the <Link path="guides/connection/agentcore-gateway-agent">Gateway to agent connection generator</Link>
+
+The generator creates a website client for **each** AG-UI or HTTP agent attached to the Gateway (A2A targets are skipped — they speak agent-to-agent JSON-RPC, not a browser protocol). It generates the same clients as connecting the website to each agent directly (<Link path="guides/connection/react-agui">AG-UI/CopilotKit</Link> for AG-UI agents, an <Link path="guides/connection/react-py-agent">OpenAPI client</Link> for Python HTTP agents), routed through the Gateway rather than at the runtime.
+
+:::note[Authentication]
+The browser authenticates with the **Gateway**, not the agents: SigV4 for an IAM Gateway (via the website's Cognito identity pool), or a JWT bearer token for a Cognito Gateway.
+:::
+
+## Usage
+
+### Run the Generator
+
+<RunGenerator generator="connection" />
+
+Select the website project as the source and the Gateway project as the target.
+
+### Options
+
+<GeneratorParameters generator="connection" />
+
+## Generator Output
+
+For each fronted AG-UI agent, the same files as the <Link path="guides/connection/react-agui">React to AG-UI agent connection</Link> are generated (an `AguiProvider`, a `useAgui<Agent>` hook and a themed CopilotKit component module), with the hook reading the Gateway's URL from runtime configuration:
+
+<FileTree>
+
+- packages/\<website>/src
+  - components
+    - AguiProvider.tsx CopilotKit provider registering each agent
+    - copilot/ Themed chat components
+  - hooks
+    - useAgui\<Agent>.tsx Connects to the agent via the Gateway's `/<targetName>/invocations` route
+
+</FileTree>
+
+For each fronted Python HTTP agent, the same files as the <Link path="guides/connection/react-py-agent">React to Python agent connection</Link> are generated (a type-safe OpenAPI client, hooks, and a provider), with the client's base URL routed through the Gateway.
+
+The Gateway's URL is registered in the `connection.gateways.<GatewayClassName>` namespace of <Link path="guides/runtime-config">Runtime Configuration</Link>, so it is published to the website's `runtime-config.json`.
+
+## Granting website users access
+
+For an **IAM** Gateway, grant the website's authenticated users permission to invoke it (a **Cognito** Gateway needs no grant — the browser authenticates with its JWT bearer token instead):
+
+<Infrastructure>
+<Fragment slot="cdk">
+```ts title="packages/infra/src/stacks/application-stack.ts" {6}
+const identity = new UserIdentity(this, 'UserIdentity');
+new Website(this, 'Website');
+
+const myGateway = new MyGateway(this, 'MyGateway');
+myGateway.addAgent(myAgent);
+myGateway.grantInvokeAccess(identity.identityPool.authenticatedRole);
+```
+</Fragment>
+<Fragment slot="terraform">
+```hcl title="packages/infra/src/main.tf"
+resource "aws_iam_policy" "gateway_invoke_policy" {
+  name = "GatewayInvokePolicy"
+
+  policy = jsonencode({
+    Version = "2012-10-17"
+    Statement = [
+      {
+        Effect   = "Allow"
+        Action   = ["bedrock-agentcore:InvokeGateway"]
+        Resource = [module.my_gateway.gateway_arn]
+      }
+    ]
+  })
+}
+
+resource "aws_iam_role_policy_attachment" "authenticated_gateway_access" {
+  role       = module.user_identity.authenticated_role_name
+  policy_arn = aws_iam_policy.gateway_invoke_policy.arn
+}
+```
+</Fragment>
+</Infrastructure>
+
+## Local Development
+
+The website's `dev` target gains a dependency on the Gateway project's `dev` target, which starts the local gateway plus every attached agent. The website's runtime configuration is overridden in `local-dev` mode to point the Gateway's URL at the local gateway, so the browser exercises the same `/<targetName>/invocations` routes locally:
+
+<NxCommands commands={["dev <website-name>"]} />
+
+## Connecting new agents
+
+The generator connects the website to the agents attached to the Gateway **at the time it runs**. After attaching another agent to the Gateway, re-run the connection generator to generate its website client — existing clients are left untouched.

package/docs/guides/connection/smithy-rdb.mdx

@@ -69,7 +69,7 @@ export interface ServiceContext {
 
 The Prisma client is instantiated inside `lambdaHandler` and passed through the service context:
 
-```ts title="packages/api/src/handler.ts" {1,10}
+```ts title="packages/api/src/handler.ts" {1,5,10}
 import { getPrisma as getMyDb } from '@my-scope/my-db';
 
 export const lambdaHandler = async (event: APIGatewayProxyEvent) => {

package/docs/guides/connection/trpc-rdb.mdx

@@ -65,7 +65,7 @@ export const authenticatedProcedure = t.procedure
 
 The plugin merges `IMyDbContext` into your procedure context, making `myDb` available as an optional property:
 
-```ts title="packages/api/src/procedures/users.ts" {8,12}
+```ts title="packages/api/src/procedures/users.ts" {7-8}
 import { z } from 'zod';
 import { authenticatedProcedure } from '../router.js';
 

package/docs/guides/connection/ts-agent-a2a.mdx

@@ -68,7 +68,7 @@ Additionally, it:
 
 The generator transforms your agent's `agent.ts` to wrap the remote A2A agent as a tool:
 
-```ts title="packages/example/src/my-agent/agent.ts" {2,5-11,14}
+```ts title="packages/example/src/my-agent/agent.ts" {2,5-12,15}
 import { Agent, tool } from '@strands-agents/sdk';
 import { RemoteAgentClientStrands } from '@my-scope/agent-connection';
 import { z } from 'zod';

package/docs/guides/connection/ts-agent-gateway.mdx

@@ -99,7 +99,7 @@ gateway.grantInvokeAccess(myAgent);
 The Gateway URL is automatically registered in the `agentcore.gateways.<ClassName>` namespace of <Link path="guides/runtime-config">Runtime Configuration</Link> by the generated CDK construct, so the agent can discover it at runtime.
 </Fragment>
 <Fragment slot="terraform">
-```hcl title="packages/infra/src/main.tf" {6-13}
+```hcl title="packages/infra/src/main.tf" {8-13}
 module "my_gateway" {
   source = "../../common/terraform/src/app/gateways/my-gateway"
 }

package/docs/guides/connection/ts-agent-mcp.mdx

@@ -102,7 +102,7 @@ The MCP server's AgentCore runtime ARN is automatically registered in the `agent
 <Fragment slot="terraform">
 After running the connection generator, you need to grant the agent permission to invoke the MCP server in your Terraform configuration:
 
-```hcl title="packages/infra/src/main.tf" {12-24}
+```hcl title="packages/infra/src/main.tf" {9-25}
 module "inventory_mcp_server" {
   source = "../../common/terraform/src/app/mcp-servers/inventory-mcp"
 }

package/docs/guides/connection.mdx

@@ -11,6 +11,10 @@ import GeneratorParameters from '@components/generator-parameters.astro';
 
 This generator is used to connect projects together, such as websites calling APIs. Simply select the source project (for example the project that will call your API) and target project (for example your API project), and this generator will handle integrating the two.
 
+:::tip[Sketch it visually]
+Prefer to design your workspace first? The <Link path="get_started/graph-builder">Graph Builder</Link> lets you drag out projects and draw the connections between them, then gives you the commands to scaffold the lot.
+:::
+
 ## Usage
 
 ### Run the Generator
@@ -243,6 +247,20 @@ The Connection generator supports the following connections:
     sourceBadge="python"
     target="agentcore"
   />
+  <ConnectionCard
+    title="AgentCore Gateway to Agent"
+    description="Front an agent with an AgentCore Gateway as a runtime target"
+    href={`/nx-plugin-for-aws/${Astro.currentLocale || 'en'}/guides/connection/agentcore-gateway-agent`}
+    source="agentcore"
+    target="strands"
+  />
+  <ConnectionCard
+    title="React Website to AgentCore Gateway"
+    description="Connect a React website to agents through an AgentCore Gateway"
+    href={`/nx-plugin-for-aws/${Astro.currentLocale || 'en'}/guides/connection/react-agentcore-gateway`}
+    source="react"
+    target="agentcore"
+  />
 </CardGrid>
 
 :::note[Runtime Configuration]

package/docs/guides/fastapi.mdx

@@ -542,7 +542,7 @@ This sets up:
 :::note[Cognito Authentication]
 If you selected to use `Cognito` authentication, you will need to supply the Cognito configuration:
 
-```hcl {3, 5-6}
+```hcl {6-7}
 module "my_api" {
   source = "../../common/terraform/src/app/apis/my-api"
 

package/docs/guides/py-agent.mdx

@@ -688,4 +688,11 @@ Use the <Link path="guides/connection">`connection`</Link> generator to integrat
     sourceBadge="python"
     target="agentcore"
   />
+  <ConnectionCard
+    title="AgentCore Gateway to Agent"
+    description="Front an agent with an AgentCore Gateway as a runtime target"
+    href={`/nx-plugin-for-aws/${Astro.currentLocale || 'en'}/guides/connection/agentcore-gateway-agent`}
+    source="agentcore"
+    target="strands"
+  />
 </CardGrid>

package/docs/guides/react-website.mdx

@@ -145,7 +145,7 @@ By default the distribution uses the default CloudFront domain name (`*.cloudfro
 <Fragment slot="cdk">
 Pass the `certificate` and `domainNames` props through in your generated website construct in `packages/common/constructs/src/app/static-websites`:
 
-```ts {6-9}
+```ts {6-8}
 export class MyWebsite extends StaticWebsite {
   constructor(scope: Construct, id: string) {
     super(scope, id, {
@@ -272,7 +272,7 @@ With Terraform, runtime configuration is managed through the runtime-config modu
 
 Your website Terraform module will deploy the `connection` namespace of the runtime configuration as a `runtime-config.json` file to the root of your S3 bucket.
 
-```hcl title="packages/infra/src/main.tf" {18-19}
+```hcl title="packages/infra/src/main.tf" {20-21}
 module "asset_bucket" {
   source = "../../common/terraform/src/core/asset-bucket"
 }
@@ -533,4 +533,11 @@ Use the <Link path="guides/connection">`connection`</Link> generator to integrat
     source="react"
     target="copilotkit"
   />
+  <ConnectionCard
+    title="React Website to AgentCore Gateway"
+    description="Connect a React website to agents through an AgentCore Gateway"
+    href={`/nx-plugin-for-aws/${Astro.currentLocale || 'en'}/guides/connection/react-agentcore-gateway`}
+    source="react"
+    target="agentcore"
+  />
 </CardGrid>

package/docs/guides/terraform-project.mdx

@@ -84,7 +84,7 @@ Application projects include full deployment capabilities with remote state mana
 
 You can start writing your Terraform infrastructure inside `src/main.tf`, for example:
 
-```diff title="src/main.tf" {2-4}
+```diff title="src/main.tf" {16-19}
 -locals {
 -  account_id = data.aws_caller_identity.current.account_id
 -  aws_region = data.aws_region.current.id

package/docs/guides/trpc.mdx

@@ -577,7 +577,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">
-```ts {6,9}
+```ts {6,10}
 import { MyApi, UserIdentity } from '@my-scope/common-constructs';
 
 export class ExampleStack extends Stack {
@@ -633,7 +633,7 @@ module "my_api" {
 </OptionFilter>
 
 <OptionFilter when={{ auth: 'cognito' }} description="Terraform usage with Cognito authentication — supply user pool and client">
-```hcl {1-3, 8-9}
+```hcl {1-3, 8, 10-11}
 module "asset_bucket" {
   source = "../../common/terraform/src/core/asset-bucket"
 }

package/docs/guides/ts-agent.mdx

@@ -599,4 +599,11 @@ Use the <Link path="guides/connection">`connection`</Link> generator to integrat
     sourceBadge="typescript"
     target="agentcore"
   />
+  <ConnectionCard
+    title="AgentCore Gateway to Agent"
+    description="Front an agent with an AgentCore Gateway as a runtime target"
+    href={`/nx-plugin-for-aws/${Astro.currentLocale || 'en'}/guides/connection/agentcore-gateway-agent`}
+    source="agentcore"
+    target="strands"
+  />
 </CardGrid>

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

@@ -308,7 +308,7 @@ You must construct the context yourself in both `handler.ts` (the Lambda functio
 
 The generator configures structured logging using AWS Lambda Powertools with automatic context injection via Middy middleware.
 
-```typescript {4}
+```typescript {3}
 // handler.ts
 export const handler = middy<APIGatewayProxyEvent, APIGatewayProxyResult>()
   .use(captureLambdaHandler(tracer))
@@ -319,7 +319,7 @@ export const handler = middy<APIGatewayProxyEvent, APIGatewayProxyResult>()
 
 You can reference the logger from your operation implementations via the context:
 
-```typescript {6}
+```typescript {5}
 // operations/echo.ts
 import { ServiceContext } from '../context.js';
 import { Echo as EchoOperation } from '../generated/ssdk/index.js';
@@ -334,7 +334,7 @@ export const Echo: EchoOperation<ServiceContext> = async (input, ctx) => {
 
 AWS X-Ray tracing is configured automatically via the `captureLambdaHandler` middleware.
 
-```typescript {3}
+```typescript {2}
 // handler.ts
 export const handler = middy<APIGatewayProxyEvent, APIGatewayProxyResult>()
   .use(captureLambdaHandler(tracer))
@@ -345,7 +345,7 @@ export const handler = middy<APIGatewayProxyEvent, APIGatewayProxyResult>()
 
 You can add custom subsegments to your traces in your operations:
 
-```typescript {7, 11, 14}
+```typescript {6, 10, 13}
 // operations/echo.ts
 import { ServiceContext } from '../context.js';
 import { Echo as EchoOperation } from '../generated/ssdk/index.js';
@@ -368,7 +368,7 @@ export const Echo: EchoOperation<ServiceContext> = async (input, ctx) => {
 
 CloudWatch metrics are collected automatically for each request via the `logMetrics` middleware.
 
-```typescript {5}
+```typescript {4}
 // handler.ts
 export const handler = middy<APIGatewayProxyEvent, APIGatewayProxyResult>()
   .use(captureLambdaHandler(tracer))
@@ -379,7 +379,7 @@ export const handler = middy<APIGatewayProxyEvent, APIGatewayProxyResult>()
 
 You can add custom metrics in your operations:
 
-```typescript {7}
+```typescript {6}
 // operations/echo.ts
 import { MetricUnit } from '@aws-lambda-powertools/metrics';
 import { ServiceContext } from '../context.js';
@@ -451,7 +451,7 @@ structure UnauthorizedError {
 
 First, expose the resolved identity on the service context in `src/context.ts`. We provide it as a function so that the `UnauthorizedError` is thrown from within an operation (where the Server SDK serializes it to a `403`), rather than from the handler:
 
-```ts {4-7,15} ins={4-7,15}
+```ts {5-8,17} ins={5-8,17}
 import { Logger } from '@aws-lambda-powertools/logger';
 import { Metrics } from '@aws-lambda-powertools/metrics';
 import { Tracer } from '@aws-lambda-powertools/tracer';
@@ -710,7 +710,7 @@ This sets up:
 :::note[Cognito Authentication]
 If you selected `Cognito` authentication, you will need to supply the Cognito configuration:
 
-```hcl {3, 5-6}
+```hcl {6-7}
 module "my_api" {
   source = "../../common/terraform/src/app/apis/my-api"
 

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

@@ -149,7 +149,7 @@ The `UserIdentity` construct can be generated using the <Link path="/guides/reac
 <Fragment slot="terraform">
 The generated module accepts `user_pool_id` and `user_pool_client_ids` variables for Cognito authentication:
 
-```terraform {8-9}
+```terraform {11-12}
 module "user_identity" {
   source = "../../common/terraform/src/core/user-identity"
 }

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

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

package/docs/snippets/api/cors-configuration-terraform-note.mdx

@@ -9,7 +9,7 @@ Given a CloudFront domain name `<domain_name>`, within the Terraform module for
 - a `cors_allow_origins` property, set to `["http://localhost:4200", "http://localhost:4300", "https://<domain name>"]`, for HTTP APIs. This restricts the API gateway CORS to this distribution and local host.
 - an `ALLOWED_ORIGINS` environment variable, set to `"https://<domain_name>"`, for REST APIs. This sets the CloudFront distribution as the only permitted CORS origin (other than local host) in AWS Lambda integrations. Note that this restriction is not applied to preflight OPTIONS - please +1 [this GitHub issue](https://github.com/awslabs/nx-plugin-for-aws/issues/377) to help prioritise addressing this.
 
-```hcl {4,6,9}
+```hcl {6,9}
 module "my_api" {
   source = "../../common/terraform/src/app/apis/my-api"
 

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

@@ -69,7 +69,7 @@ api.integrations.sayHello.handler.addToRolePolicy(new PolicyStatement({
 
 If your API uses the `shared` pattern, the shared router Lambda is exposed as `api.integrations.$router`:
 
-```ts {6}
+```ts {5}
 const api = new MyApi(this, 'MyApi', {
   integrations: MyApi.defaultIntegrations(this).build(),
 });
@@ -640,7 +640,7 @@ Generated CDK API constructs support two integration patterns:
 
 For example, setting `pattern` to `'shared'` creates a single function instead of one per integration:
 
-```ts {5,11-12}
+```ts {6}
 // packages/common/constructs/src/app/apis/my-api.ts
 export class MyApi<...> extends ... {
 

package/docs/snippets/api/waf-configuration.mdx

@@ -15,7 +15,7 @@ You can edit the generated rest-api construct to add, remove, or adjust rules (f
 <Fragment slot="cdk">
 To opt out (for example, to attach your own Web ACL), set `enableWaf` to `false`:
 
-```ts {4}
+```ts {3}
 const api = new MyApi(this, 'MyApi', {
   integrations: MyApi.defaultIntegrations(this).build(),
   enableWaf: false,
@@ -25,7 +25,7 @@ const api = new MyApi(this, 'MyApi', {
 <Fragment slot="terraform">
 To opt out (for example, to attach your own Web ACL), set `enable_waf` to `false`:
 
-```hcl {4-5}
+```hcl {5}
 module "my_api" {
   source = "../../common/terraform/src/app/apis/my-api"
 

package/docs/snippets/connection/a2a-infrastructure.mdx

@@ -21,7 +21,7 @@ remoteAgent.grantInvokeAccess(myAgent);
 The remote agent's AgentCore runtime ARN is automatically registered in the `agentcore` namespace of <Link path="guides/runtime-config">Runtime Configuration</Link> by the generated CDK construct, so the host agent can discover it at runtime.
 </Fragment>
 <Fragment slot="terraform">
-```hcl title="packages/infra/src/main.tf" {3-6, 11-12, 16-17}
+```hcl title="packages/infra/src/main.tf" {15-34}
 module "remote_agent" {
   source = "../../common/terraform/src/app/agents/remote-agent"
 

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

@@ -144,7 +144,7 @@ The `UserIdentity` construct can be generated using the <Link path="/guides/reac
 <Fragment slot="terraform">
 The generated module accepts `user_pool_id` and `user_pool_client_ids` variables for Cognito authentication:
 
-```terraform {8-9}
+```terraform {11-12}
 module "user_identity" {
   source = "../../common/terraform/src/core/user-identity"
 }

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

@@ -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 {4}
+```ts {3}
 // service.ts
 export const Service: ApiService<ServiceContext> = {
   ...

package/generators.json

@@ -30,6 +30,20 @@
       "metric": "g65",
       "hidden": true
     },
+    "agentcore-gateway#agent-connection": {
+      "factory": "./src/agentcore-gateway/agent-connection/generator",
+      "schema": "./src/agentcore-gateway/agent-connection/schema.json",
+      "description": "Connect an AgentCore Gateway to an agent, adding the agent as a gateway target",
+      "metric": "g69",
+      "hidden": true
+    },
+    "agentcore-gateway#react-connection": {
+      "factory": "./src/agentcore-gateway/react-connection/generator",
+      "schema": "./src/agentcore-gateway/react-connection/schema.json",
+      "description": "Connect a React website to an AgentCore Gateway fronting agents",
+      "metric": "g70",
+      "hidden": true
+    },
     "connection": {
       "factory": "./src/connection/generator",
       "schema": "./src/connection/schema.json",
@@ -54,7 +68,9 @@
         "connection/ts-agent-gateway",
         "connection/py-agent-gateway",
         "connection/agentcore-gateway-mcp",
-        "connection/agentcore-gateway-gateway"
+        "connection/agentcore-gateway-gateway",
+        "connection/agentcore-gateway-agent",
+        "connection/react-agentcore-gateway"
       ]
     },
     "license": {

package/package.json

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

package/src/agentcore-gateway/agent-connection/schema.json

@@ -0,0 +1,31 @@
+{
+  "$schema": "https://json-schema.org/schema",
+  "$id": "agentcore-gateway#agent-connection",
+  "title": "agentcore-gateway#agent-connection",
+  "description": "Connect an AgentCore Gateway to an agent, adding the agent as a gateway target",
+  "type": "object",
+  "properties": {
+    "sourceProject": {
+      "type": "string",
+      "description": "The gateway project"
+    },
+    "targetProject": {
+      "type": "string",
+      "description": "The agent project"
+    },
+    "sourceComponent": {
+      "type": "string",
+      "description": "The gateway component in the source project"
+    },
+    "targetComponent": {
+      "type": "string",
+      "description": "The agent component in the target project"
+    },
+    "preferInstallDependencies": {
+      "type": "boolean",
+      "description": "Whether to prefer installing dependencies after the generator runs. Set to false to defer installing when batching multiple generators (an install still runs if needed so subsequent generators can compute the Nx project graph); install once at the end.",
+      "default": true
+    }
+  },
+  "required": ["sourceProject", "targetProject"]
+}

package/src/agentcore-gateway/react-connection/schema.json

@@ -0,0 +1,31 @@
+{
+  "$schema": "https://json-schema.org/schema",
+  "$id": "agentcore-gateway#react-connection",
+  "title": "agentcore-gateway#react-connection",
+  "description": "Connect a React website to an AgentCore Gateway fronting agents",
+  "type": "object",
+  "properties": {
+    "sourceProject": {
+      "type": "string",
+      "description": "The React website project"
+    },
+    "targetProject": {
+      "type": "string",
+      "description": "The gateway project"
+    },
+    "sourceComponent": {
+      "type": "string",
+      "description": "The website component in the source project"
+    },
+    "targetComponent": {
+      "type": "string",
+      "description": "The gateway component in the target project"
+    },
+    "preferInstallDependencies": {
+      "type": "boolean",
+      "description": "Whether to prefer installing dependencies after the generator runs. Set to false to defer installing when batching multiple generators (an install still runs if needed so subsequent generators can compute the Nx project graph); install once at the end.",
+      "default": true
+    }
+  },
+  "required": ["sourceProject", "targetProject"]
+}

package/src/agentcore-gateway/schema.json

@@ -2,6 +2,7 @@
   "$schema": "https://json-schema.org/schema",
   "$id": "agentcore-gateway",
   "title": "agentcore-gateway",
+  "x-label": "AgentCore Gateway",
   "description": "Generate an AgentCore Gateway project",
   "type": "object",
   "properties": {
@@ -26,8 +27,8 @@
     },
     "protocol": {
       "type": "string",
-      "description": "The inbound protocol exposed by your gateway. Only mcp is supported today; additional protocols may be added in future.",
-      "enum": ["mcp"],
+      "description": "The inbound protocol exposed by your gateway. An mcp gateway aggregates MCP server targets into a single MCP endpoint. An http gateway proxies requests to agent runtime targets via path-based routing, so callers (e.g. a website) can reach agents through the gateway.",
+      "enum": ["mcp", "http"],
       "default": "mcp",
       "x-priority": "important"
     },

package/src/py/agent/schema.json

@@ -2,6 +2,7 @@
   "$schema": "https://json-schema.org/schema",
   "$id": "py#agent",
   "title": "py#agent",
+  "x-label": "Agent",
   "description": "Add an AI Agent to a Python project",
   "type": "object",
   "properties": {

package/src/py/dynamodb/schema.json

@@ -2,6 +2,7 @@
   "$schema": "https://json-schema.org/schema",
   "$id": "py#dynamodb",
   "title": "py#dynamodb",
+  "x-label": "DynamoDB",
   "description": "Create a Python DynamoDB project",
   "type": "object",
   "properties": {

package/src/py/fast-api/schema.json

@@ -2,6 +2,7 @@
   "$schema": "https://json-schema.org/schema",
   "$id": "PyFastApi",
   "title": "Create a Python FastAPI project",
+  "x-label": "FastAPI",
   "description": "Create a Python FastAPI project",
   "type": "object",
   "properties": {

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

@@ -2,6 +2,7 @@
   "$schema": "https://json-schema.org/schema",
   "$id": "py#mcp-server",
   "title": "py#mcp-server",
+  "x-label": "MCP Server",
   "description": "Generate a Python Model Context Protocol (MCP) server for providing context to Large Language Models",
   "type": "object",
   "properties": {

package/src/py/rdb/schema.json

@@ -2,6 +2,7 @@
   "$schema": "https://json-schema.org/schema",
   "$id": "py#rdb",
   "title": "py#rdb",
+  "x-label": "Relational Database",
   "description": "Create a Python relational database project",
   "type": "object",
   "properties": {

package/src/smithy/ts/api/schema.json

@@ -2,6 +2,7 @@
   "$schema": "https://json-schema.org/schema",
   "$id": "ts#smithy-api",
   "title": "ts#smithy-api",
+  "x-label": "Smithy API",
   "description": "Create an API using Smithy and the Smithy TypeScript Server SDK",
   "type": "object",
   "properties": {