Ext Ops Panel
Open dashboard
Comparison

AWS AppSync vs firebase-development

AWS AppSync is an MCP server published by awslabs. Marketplaces we read that list it: 1 (Docker MCP Catalog). firebase-development is a plugin bundle for AI coding tools published by 2389-research. Marketplaces we read that list it: 1 (Community GitHub marketplaces). As of our marketplace pass on 2026-10-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
MarketplaceAWS AppSyncfirebase-development
Docker MCP Catalog Listed
Version: sha256:5fc57706f27b
Forks (GitHub): 1 805
Pulls (Docker Hub): 12 862
Stars (Docker Hub): 0
Stars (GitHub): 9 776
Not marked · First seen
Not listed
Community marketplace 2389-research/claude-plugins Not listed Listed
Version: 1.0.1
Forks (GitHub): 0
Stars (GitHub): 2
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

AWS AppSync vs firebase-development
FactAWS AppSyncfirebase-development
Marketplaces that list it11
Stars (GitHub) (differs)9 776 (better)2 (worse)
Pulls (Docker Hub) (differs)12 862No figure on Docker Hub
Forks (GitHub) (differs)1 805 (better)0 (worse)
Last releaseNot publishedNot published
Where it runs (differs)On your machine (mcp/aws-appsync-mcp-server)Installs as a plugin bundle
Transport (differs)stdioNot stated
Tools it declares (differs)10Not published
Environment variables it asks for (differs)5, secrets among them: 2Not published
Parts of the bundle (differs)Not a bundle5
Licence (differs)Apache-2.0Not stated
Repository (differs)github.com/awslabs/mcpgithub.com/2389-research/firebase-development
Changes in the last 7 days (differs)02
First seen (differs)2026-10-112026-10-14

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

AWS AppSync

In its own words, on Docker MCP Catalog:

Manage applications powered by AWS AppSync.

firebase-development

In its own words, on Community GitHub marketplaces:

Firebase project workflows including setup, features, debugging, and validation

How to run each

AWS AppSync As a local MCP server: Docker image

Claude Code
claude mcp add --env "AWS_SECRET_ACCESS_KEY=<YOUR_AWS_SECRET_ACCESS_KEY>" --env "AWS_SESSION_TOKEN=<YOUR_AWS_SESSION_TOKEN>" --transport stdio aws-appsync -- docker run -i --rm -e AWS_SECRET_ACCESS_KEY -e AWS_SESSION_TOKEN mcp/aws-appsync-mcp-server

Requires: AWS_SECRET_ACCESS_KEY (secret), AWS_SESSION_TOKEN (secret)

firebase-development As a Claude Code plugin

Claude Code
/plugin marketplace add 2389-research/claude-plugins
/plugin install firebase-development@2389-research

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

Tools each declares

The marketplaces of firebase-development publish no list of tools, so we do not compare tools.

Settings each asks for

The marketplaces of firebase-development publish no settings it asks for, so we do not compare settings.

What it can do: AWS AppSync · What it can do: firebase-development · Compare two other plugins

Data comes from the Docker MCP Catalog (desktop.docker.com/mcp/catalog) and Docker Hub. Data comes from public marketplace files in GitHub repositories of their authors. 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