Ext Ops Panel
Open dashboard
Comparison

StarryKit vs QR Branding

StarryKit is a plugin bundle for AI coding tools published by StarryKit. Marketplaces we read that list it: 1 (Community GitHub marketplaces). QR Branding is an MCP server published by quartzondev. Marketplaces we read that list it: 2 (Official MCP Registry, npm registry (MCP servers)). 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
MarketplaceStarryKitQR Branding
Community marketplace starrykit/starrykit-plugin Listed
Version: 0.4.0
Forks (GitHub): 4
Stars (GitHub): 102
Not marked · First seen
Not listed
Official MCP Registry Not listed Listed
Version: 0.2.8
Downloads/month (npm): 1 490
Downloads/week (npm): 1 223
Forks (GitHub): 0
Stars (GitHub): 0
Not marked · First seen
npm registry (MCP servers) Not listed Listed
Version: 0.2.8
Downloads/month (npm): 1 490
Downloads/week (npm): 1 223
Forks (GitHub): 0
Stars (GitHub): 0
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

StarryKit vs QR Branding
FactStarryKitQR Branding
Marketplaces that list it (differs)1 (worse)2 (better)
Stars (GitHub) (differs)102 (better)0 (worse)
Forks (GitHub) (differs)4 (better)0 (worse)
Last release (differs)Not published2026-11-14
Where it runs (differs)Remote server (mcp.starrykit.com/mcp)Remote server or your machine
TransportStreamable HTTPStreamable HTTP
Tools it declaresNot publishedNot published
Environment variables it asks for (differs)Not published2, secrets among them: 1
Parts of the bundle (differs)2Not a bundle
LicenceMITMIT
Repository (differs)github.com/starrykit/starrykit-plugingithub.com/quartzondev/qr-branding-mcp
Changes in the last 7 days (differs)016
First seen (differs)2026-11-072026-10-11
Endpoint at the last check (differs)Responded 2 h agoResponded 17 h 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

StarryKit

In its own words, on Community GitHub marketplaces:

Create editable presentations, posters, social graphics, art, and visual design documents from prompts and references.

QR Branding

In its own words, on Official MCP Registry:

Generate branded, scan-validated QR codes (manual, AI, templates, Wi-Fi, vCard, geo).

How to run each

StarryKit As a Claude Code plugin

Claude Code
/plugin marketplace add starrykit/starrykit-plugin
/plugin install starrykit-plugin@starrykit

QR Branding As a remote MCP server

Claude Code
claude mcp add --transport http qr-branding https://qr-branding.com/mcp --header "X-API-Key: <YOUR_X_API_KEY>"

Requires: QR_BRANDING_API_KEY (secret), X-API-Key header

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

Both endpoints 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 StarryKit publish no settings it asks for, so we do not compare settings.

What it can do: StarryKit · What it can do: QR Branding · 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. Package data comes from the public npm registry (registry.npmjs.org). 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