cdviz vs io.github.HalidSaglam/saglitzdesign-mcp
cdviz is no longer listed on any marketplace we read: these are its last known data, as of 2026‑10‑15.
cdviz is a plugin bundle for AI coding tools published by CDviz team. No marketplace we read lists it any more. io.github.HalidSaglam/saglitzdesign-mcp is an MCP server published by HalidSaglam. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-27. A plugin in this pair is no longer listed on any marketplace we read, so search engines are asked not to index the page.
Where each is published
| Marketplace |  io.github.HalidSaglam/saglitzdesign-mcp | |
|---|---|---|
| Community marketplace cdviz-dev/cdviz-site | Removed on 2026-10-15 Version: not stated Forks (GitHub): 0 Stars (GitHub): 0 Not marked · First seen |
Not listed |
| Official MCP Registry | Not listed | Listed Version: 0.19.1 Downloads/month (npm): 598 Downloads/week (npm): 81 Forks (GitHub): 3 Stars (GitHub): 6 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 | cdvizno longer listed · | io.github.HalidSaglam/saglitzdesign-mcp |
|---|---|---|
| Marketplaces that list it (differs) | 0 | 1 |
| Stars (GitHub) (differs) | 0 | 6 |
| Forks (GitHub) (differs) | 0 | 3 |
| Last release | Not published | Not published |
| Where it runs (differs) | Installs as a plugin bundle | On your machine (saglitzdesign-mcp) |
| Transport (differs) | Not stated | stdio |
| Tools it declares | Not published | Not published |
| Environment variables it asks for | Not published | Not published |
| Parts of the bundle (differs) | 2 | Not a bundle |
| Licence (differs) | Apache-2.0 | MIT |
| Repository (differs) | github.com/cdviz-dev/cdviz-site | github.com/halidsaglam/saglitzdesign-mcp |
| Changes in the last 7 days | 0 | 0 |
| First seen (differs) | 2026-10-14 | 2026-10-11 |
Lines where the two differ have a tinted background and bold values. No value is marked better or worse: a plugin no marketplace lists any more is shown with its last known data, which we do not rank against current figures.
What to use instead of cdviz
Plugins still listed whose own names, descriptions, tools and skills are closest in meaning to it. Comparable, not endorsed.
-
frontend-designer
Build accessible, responsive, and performant frontend components with design system best practices, modern CSS, and framework-agnostic patterns.
-
Web development tools including frontend design workflows
-
Design system toolkit: tokens, components, accessibility, and framework integrations
-
All in one skills about software design, UI/UX
-
The design taste pack: a five-stage UI pipeline (direction, system, motion, critique, verification) that stops generic AI-looking interfaces, plus pointers to five specialist…
-
Builds comprehensive design systems and design bibles with production-ready CSS. Expert in design tokens, component libraries, CSS architecture. Use for design system creation…
What each says it does
cdviz
CDviz design system (cdviz-design) and writing rules for docs, articles and copy (cdviz-writing)
io.github.HalidSaglam/saglitzdesign-mcp
Expert design & marketing MCP: UI/UX, design languages, SEO/GEO, tokens, a11y, recipes.
How to run each
cdviz
No data for an automatic command: what its marketplaces declare does not say unambiguously how to connect it.
io.github.HalidSaglam/saglitzdesign-mcp As a local MCP server: npm package
claude mcp add --transport stdio saglitzdesign-mcp -- npx -y saglitzdesign-mcpCommands 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
Neither one's marketplaces publish the settings it asks for.
What it can do: cdviz · What it can do: io.github.HalidSaglam/saglitzdesign-mcp · 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. Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.