Ext Ops Panel
Open dashboard
Comparison

nx-plugin-for-aws vs AWS Builder

nx-plugin-for-aws is a plugin bundle for AI coding tools published by AWS. Marketplaces we read that list it: 1 (Community GitHub marketplaces). AWS Builder is an MCP server published by Evozim. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-11-14. This pair was picked by a reader, not by our comparison rule, so search engines are asked not to index the page.

Where each is published

Where each is published
Marketplacenx-plugin-for-awsAWS Builder
Community marketplace awslabs/nx-plugin-for-aws Listed
Version: 1.0.0
Forks (GitHub): 37
Stars (GitHub): 154
Not marked · First seen
Not listed
Official MCP Registry Not listed Listed
Version: 1.0.0
No figure published
Not marked · First seen

Each figure is the marketplace's own and is never added up across marketplaces. A marketplace that publishes no figure shows none: no number is not zero.

The facts side by side

nx-plugin-for-aws vs AWS Builder
Factnx-plugin-for-awsAWS Builder
Marketplaces that list it11
Stars (GitHub) (differs)154No figure on GitHub
Forks (GitHub) (differs)37No figure on GitHub
Last releaseNot publishedNot published
Where it runs (differs)On your machine (@aws/nx-plugin-mcp)Remote server (aws-builder-mcp.vercel.app/api/mcp)
Transport (differs)Not statedSSE
Tools it declaresNot publishedNot published
Environment variables it asks forNot publishedNot published
Parts of the bundle (differs)2Not a bundle
Licence (differs)Apache-2.0Not stated
Repository (differs)github.com/awslabs/nx-plugin-for-awsNot stated
Changes in the last 7 days00
First seen (differs)2026-10-152026-10-11
Endpoint at the last check (differs)no remote endpoint we checkResponded less than an hour ago

Lines where the two differ have a tinted background and bold values. Where the data itself says which value is better (more marketplaces, a larger figure of the same marketplace, a fresher release, a verified mark on a marketplace that lists both), the better one is also marked green with ▲ and the worse one red with ▼. Where it runs, the transport, the tools, the settings, hooks, the bundle's parts, the licence and the week's changes are marked only as different: more or fewer is not better in itself.

What each says it does

nx-plugin-for-aws

In its own words, on Community GitHub marketplaces:

Scaffold and build cloud-native applications on AWS using @aws/nx-plugin generators.

AWS Builder

In its own words, on Official MCP Registry:

AWS CloudFormation and Terraform infrastructure blueprint builder.

How to run each

nx-plugin-for-aws As a Claude Code plugin

Claude Code
/plugin marketplace add awslabs/nx-plugin-for-aws
/plugin install nx-plugin-for-aws@nx-plugin-for-aws

AWS Builder As a remote MCP server

Claude Code
claude mcp add --transport sse aws-builder https://aws-builder-mcp.vercel.app/api/mcp --header "payment-signature: <YOUR_PAYMENT_SIGNATURE>"

Requires: payment-signature header

Commands built only from what the marketplaces declare; the full set for every client is on each card.

Only AWS Builder has a remote endpoint we check. How we check endpoints

Tools each declares

Neither one's marketplaces publish a list of tools, so there is nothing to compare.

Settings each asks for

Neither one's marketplaces publish the settings it asks for.

What it can do: nx-plugin-for-aws · What it can do: AWS Builder · Compare two other plugins

Data comes from public marketplace files in GitHub repositories of their authors. Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.

Where the data comes from: how the catalog is built