Ext Ops Panel
Open dashboard
Comparison

css-development vs Systra Tools

css-development is a plugin bundle for AI coding tools published by 2389-research. Marketplaces we read that list it: 1 (Claude Code: claude-plugins-community). Systra Tools is an MCP server published by systra.tools. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-17. 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
Marketplacecss-developmentSystra Tools
Claude Code: claude-plugins-community Listed
Version: dbb92f1
Forks (GitHub): 8
Stars (GitHub): 97
Not marked · First seen
Not listed
Official MCP Registry Not listed Listed
Version: 1.0.0
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

css-development vs Systra Tools
Factcss-developmentSystra Tools
Marketplaces that list it11
Stars (GitHub) (differs)97 (better)0 (worse)
Forks (GitHub) (differs)8 (better)0 (worse)
Last releaseNot publishedNot published
Where it runs (differs)Installs as a plugin bundleRemote server (systra.tools/api/mcp)
Transport (differs)Not statedStreamable HTTP
Tools it declaresNot publishedNot published
Environment variables it asks forNot publishedNot published
LicenceNot statedNot stated
Repository (differs)github.com/2389-research/claude-pluginsgithub.com/roesmannamelie-alt/systra-tools-plugin
Changes in the last 7 days (differs)10
First seen2026-10-112026-10-11
Endpoint at the last check (differs)no remote endpoint we checkResponded 4 days 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

css-development

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

CSS development workflows with Tailwind composition, semantic naming, and dark mode by default

Systra Tools

In its own words, on Official MCP Registry:

Search and pull 500+ production-ready React + Tailwind sections and elements

How to run each

css-development As a Claude Code plugin

Claude Code
/plugin marketplace add anthropics/claude-plugins-community
/plugin install css-development@claude-community

Systra Tools As a remote MCP server

Claude Code
claude mcp add --transport http systra-tools https://systra.tools/api/mcp --header "Authorization: Bearer <YOUR_SYSTRA_MCP_KEY>"

Requires: Authorization header

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

Only Systra Tools 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: css-development · What it can do: Systra Tools · Compare two other plugins

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