Ext Ops Panel
Open dashboard
Comparison

migration-to-aws vs Provision Stack

migration-to-aws is a plugin bundle for AI coding tools published by awslabs. Marketplaces we read that list it: 2 (Claude Code: claude-plugins-official, Community GitHub marketplaces). Provision Stack is an MCP server published by provision-stack.com. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-30. 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
Marketplacemigration-to-awsProvision Stack
Claude Code: claude-plugins-official Listed
Version: 1.5.0
Forks (GitHub): 42
Stars (GitHub): 25
Not marked · First seen
Not listed
Official MCP Registry Not listed Listed
Version: 0.5.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

migration-to-aws vs Provision Stack
Factmigration-to-awsProvision Stack
Marketplaces that list it (differs)2 (better)1 (worse)
Stars (GitHub) (differs)25No figure on GitHub
Forks (GitHub) (differs)42No figure on GitHub
Last releaseNot publishedNot published
Where it runs (differs)Remote server (aws-mcp.us-east-1.api.aws/mcp)Remote server (api.provision-stack.com/mcp)
TransportStreamable HTTPStreamable HTTP
Tools it declaresNot publishedNot published
Environment variables it asks for (differs)2, secrets among them: 0Not published
Parts of the bundle (differs)16Not a bundle
Licence (differs)Apache-2.0Not stated
Repository (differs)github.com/awslabs/startupsgithub.com/travislinkey/provision-stack
Changes in the last 7 days00
First seen2026-10-112026-10-11
Endpoint at the last check (differs)Responded 8 h agoNot responding since 2026-10-13

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

migration-to-aws

In its own words, on Claude Code: claude-plugins-official:

Plan a migration from Google Cloud Platform (and OpenAI/Gemini AI workloads) to AWS. Analyzes your Infrastructure-as-Code files, app code, and GCP billing data to discover resources, design an AWS architecture, estimate costs, and generate migration artifacts — including AI-provider mapping to Amazon Bedrock. Processing is local; your data stays in your environment.

Provision Stack

In its own words, on Official MCP Registry:

Outcome-based infrastructure for agents — verified AWS deployments, metered billing

How to run each

migration-to-aws As a Claude Code plugin

Claude Code
/plugin install migration-to-aws@claude-plugins-official

Provision Stack As a remote MCP server

Claude Code
claude mcp add --transport http provision-stack https://api.provision-stack.com/mcp --header "Authorization: Bearer <YOUR_TOKEN>"

Requires: Authorization header

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

Only the endpoint of migration-to-aws responded at the last daily 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

The marketplaces of Provision Stack publish no settings it asks for, so we do not compare settings.

What it can do: migration-to-aws · What it can do: Provision Stack · Compare two other plugins

Data comes from the public marketplace file https://github.com/anthropics/claude-plugins-official/blob/HEAD/.claude-plugin/marketplace.json. 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