design.tesserai/tesserai · version 0.2.2 · 2,462 weekly npm downloads · audited 2026-11-03
Notes
No hidden-instruction or invisible-character findings in any tool, prompt, or resource description.
Checks the directory's published tool requirements that are visible from tools/list. Passing them does not guarantee acceptance.
| Name | Title | Hint | Description |
|---|---|---|---|
import_design_system | Import a design system | writes | Bring this project's existing design system (its look: colors for light and dark, fonts, body text size, corners, spacing, shadows) into tesserai as a new system. It never changes the project. Read the project first, the… |
outline | Design system outline | read-only | A compact outline of the design system: palettes, meanings (intents), surfaces, type, spacing, radius, and every component with its parts and options. |
get_tokens | Get tokens | read-only | Read the tokens under a path prefix: values, per-mode values, and whether they were set by hand. |
get_component | Get a component | read-only | Read one component's full definition: parts, axes, and every recipe layer. |
explain | Explain a token | read-only | Follow a token's references to its final value, in light or dark. |
usage | Token usage | read-only | What depends on a token: the tokens that reference it and the components it styles. |
check_contrast | Check contrast | read-only | Run the contrast checks and list failing pairs with suggested fixes. |
list_overrides | List overrides | read-only | What has been customised compared with tesserai's defaults. |
guidelines | Design guidelines | read-only | Design guidelines on a topic (WCAG, Apple, Material and settled practice, with sources): the rule, why it matters, where it comes from. Read it before answering how a design system should do something, or making a change… |
list_operations | List operations | read-only | Every operation apply_changes accepts, by group, with what it does. describe_operation gives one operation's exact input. |
describe_operation | Describe an operation | read-only | One operation's input, as JSON Schema. |
apply_changes | Apply changes | destructive | Change the design system with operations, applied in order, all or nothing, and checked before anything is written. Then the theme CSS and components are regenerated; files the developer edited are kept and the new versi… |
scan | Scan the project | read-only | How the app uses the design system: each component's uses and files, most used first, with each option's uses (a use without it counts for the default); components never used; options no use sets; overrides (className, c… |
upload_scan | Upload a scan | writes | Scan the app and keep the result with its design system in the builder (Pro), where the team sees usage beside the system and how it changes over time. Sends counts, kinds and class names only: no source, no paths but ed… |
sync | Sync the design system | destructive | Bring the project up to date with its design system: for a project that follows a tesserai link, pull the latest version first (the latest release of a private system); then regenerate the theme CSS and components. Files… |
component_guide | Component guide | read-only | How to build with the system's components. Without a component: each one with what it's for and its import. With one: its import, its props and their allowed values, and an example written for this project (its library a… |
example_page | Example page | read-only | A whole page written with this system's components, for this project (its library and class prefix): a pattern to follow when building similar UI. Pages: sign-in, settings, dashboard, data-list (sign-in and settings are … |
npx mcpvetter scan --liveAdd this to a README:
[](https://mcpvetter.com/servers/tesserai-cli)Get the MCPVetter verified badge, a re-audit within 24 hours of every npm release, and an email whenever tools, findings, or Claude directory readiness change. $29 per server per month. You prove ownership first, free.