gsc-mcp-tools vs designlang
gsc-mcp-tools is an MCP server published by FlorianBruniaux. Marketplaces we read that list it: 1 (PyPI (MCP servers)). designlang is an MCP server published by Manavarya09. Marketplaces we read that list it: 2 (Official MCP Registry, Community GitHub marketplaces). As of our marketplace pass on 2026-11-11. 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
| Marketplace | ||
|---|---|---|
| PyPI (MCP servers) | Listed Version: 1.6.0 Downloads/month (PyPI): 148 Downloads/week (PyPI): 734 Forks (GitHub): 4 Stars (GitHub): 24 Not marked · First seen |
Not listed |
| Official MCP Registry | Not listed | Listed Version: 13.4.1 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
| Fact | gsc-mcp-tools | designlang |
|---|---|---|
| Marketplaces that list it (differs) | 1 (worse) | 2 (better) |
| Stars (GitHub) (differs) | 24 (worse) | 5 037 (better) |
| Forks (GitHub) (differs) | 4 (worse) | 421 (better) |
| Last release (differs) | Not published | 2026-11-11 |
| Where it runs (differs) | On your machine (gsc-mcp-tools) | On your machine (designlang) |
| Transport (differs) | Not stated | stdio |
| Tools it declares | Not published | Not published |
| Environment variables it asks for (differs) | Not published | 1, secrets among them: 1 |
| Parts of the bundle (differs) | Not a bundle | 15 |
| Licence | MIT | MIT |
| Repository (differs) | github.com/florianbruniaux/google-search-console-mcp | github.com/manavarya09/design-extract |
| Changes in the last 7 days (differs) | 0 | 4 |
| First seen (differs) | 2026-10-12 | 2026-10-27 |
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
gsc-mcp-tools
96 MCP tools for Google Search Console, Bing, GA4 and CrUX: SEO audits, traffic diagnostics, local crawl evidence, guarded submissions and opt-in bounded native workflows
designlang
Measure any site's design system, score how generic a page looks, check UI against your brand.
How to run each
gsc-mcp-tools
No data for an automatic command: what its marketplaces declare does not say unambiguously how to connect it.
designlang As a local MCP server: npm package
claude mcp add --env "DESIGNLANG_BRAND_TOKEN=<YOUR_DESIGNLANG_BRAND_TOKEN>" --transport stdio designlang -- npx -y designlang mcp
Requires: DESIGNLANG_BRAND_TOKEN (secret)
Commands built only from what the marketplaces declare; the full set for every client is on each card.
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 gsc-mcp-tools publish no settings it asks for, so we do not compare settings.
What it can do: gsc-mcp-tools · What it can do: designlang · Compare two other plugins
Package data comes from the Python Package Index (pypi.org). Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. 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.