Ext Ops Panel
Open dashboard
Comparison

awesome-statusline vs Tailwind Shades

awesome-statusline is a plugin bundle for AI coding tools published by AwesomeJun. Marketplaces we read that list it: 1 (Community GitHub marketplaces). Tailwind Shades is an MCP server published by bourhaouta. Marketplaces we read that list it: 2 (Official MCP Registry, npm registry (MCP servers)). As of our marketplace pass on 2026-10-25. 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
Marketplaceawesome-statuslineTailwind Shades
Community marketplace awesomezun/cc-statusline Listed
Version: 3.3.4
Forks (GitHub): 18
Stars (GitHub): 201
Not marked · First seen
Not listed
Official MCP Registry Not listed Listed
Version: 1.6.0
Downloads/month (npm): 1 265
Downloads/week (npm): 453
Forks (GitHub): 6
Stars (GitHub): 78
Not marked · First seen
npm registry (MCP servers) Not listed Listed
Version: 1.6.0
Downloads/month (npm): 1 265
Downloads/week (npm): 453
Forks (GitHub): 6
Stars (GitHub): 78
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

awesome-statusline vs Tailwind Shades
Factawesome-statuslineTailwind Shades
Marketplaces that list it (differs)1 (worse)2 (better)
Stars (GitHub) (differs)201 (better)78 (worse)
Forks (GitHub) (differs)18 (better)6 (worse)
Last release (differs)2026-10-18 (better)2026-10-14 (worse)
Where it runs (differs)Installs as a plugin bundleRemote server or your machine
Transport (differs)Not statedStreamable HTTP
Tools it declaresNot publishedNot published
Environment variables it asks forNot publishedNot published
Parts of the bundle (differs)1Not a bundle
Licence (differs)Not statedMIT
Repository (differs)github.com/awesomezun/cc-statuslinegithub.com/bourhaouta/vscode-tailwindshades
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 26 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

awesome-statusline

In its own words, on Community GitHub marketplaces:

A Claude Code statusline that shows reasoning effort and thinking. 5 presets (xsmall-xlarge), Catppuccin, no Node/Nerd Font, native PowerShell on Windows.

Tailwind Shades

In its own words, on Official MCP Registry:

Tailwind CSS palettes (50-950) from any color, the closest Tailwind color, and Tailwind's defaults

How to run each

awesome-statusline As a Claude Code plugin

Claude Code
/plugin marketplace add awesomezun/cc-statusline
/plugin install awesome-statusline@awesome-statusline

Tailwind Shades As a remote MCP server

Claude Code
claude mcp add --transport http tailwindshades https://tailwindshades.bourhaouta.com/mcp

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

Only Tailwind Shades has a remote endpoint we check. How we check endpoints

Tools each declares

Neither the marketplaces of awesome-statusline nor its endpoint list any tools, so we do not compare tools.

Settings each asks for

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

What it can do: awesome-statusline · What it can do: Tailwind Shades · 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