Primitiv
Related Servers
Alternatives to Primitiv
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityBmaintenanceEnables AI agents to write AI-generated designs into design-tool canvases (MasterGo, Penpot) as native editable layers, and to read canvas selections back out as HTML + Tailwind, design tokens, and SVG assets. Runs locally with progressive tool disclosure and structurally truncated results so large design files stay within an agent's context budget.Apache 2.0
- AlicenseNot gradedqualityAmaintenanceEnables AI coding agents to read the live state of an open Figma file — variables, modes, components, prototype edges and assets — and to export design tokens and code packages for web, iOS, Android, React, Django and Tauri through a user-run loopback bridge with separate read and write gates.2MIT
- AlicenseNot gradedqualityAmaintenanceEnables AI agents to score live URLs against a 40-check design contract, validate DTCG tokens and Lottie animations, audit accessibility, and retrieve design-system contracts, catalogs, and review rubrics.43 npmMIT
- AlicenseNot gradedqualityBmaintenanceEnables coding agents to query a workspace's design system before writing UI and validate generated code against the same system afterward, using configurable token and component sources.10 npmMIT
- AlicenseNot gradedqualityBmaintenanceProvides coding agents with local tools to inspect project UI inventories, propose and compare visual direction boards, compile versioned design contracts and DTCG tokens, retrieve section-specific blueprints, and audit running interfaces with browser evidence including screenshots, accessibility findings, and overflow measurements.MIT
- AlicenseAqualityBmaintenanceProvides deterministic, read-only design knowledge for AI coding agents to help them choose visual directions, plan UI states, and compose design tokens, all without network access.6264 npm4MIT
TDQS
Scored across 6 tools
Each tool targets a clearly distinct concern: token lookup, design context overview, component lookup, conflict pagination, inferred rules, and violations. Even the overlapping get_token and get_design_context are explicitly differentiated with guidance on when to use each.
All tools follow a consistent get_<noun> pattern (get_token, get_component, get_conflicts, get_violations). The two compound names (get_design_context, get_inferred_rules) still follow the same verb_noun convention and fit the pattern cleanly.
Six read-only tools is well-scoped for a design system introspection server. Each tool represents a distinct query surface with no redundancy or bloat.
The surface covers token lookup, component lookup, design context overview, conflict discovery, inferred rules, and hardcoded-value violations — a coherent read-only audit toolkit. A minor gap is the lack of a write/update path, but the tool set is explicitly read-only by design, so this is acceptable.