tesserai
NPM · @TESSERAI/CLI
Your project's design system for coding agents: tokens, components, contrast checks, guidelines.
Available components
Last scanned (9 hours ago)
Scores higher than 76% of npm servers
Category Developer Tools
How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →
Supply Chain Security100
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- No install/post-install scripts declared.Pass
- No production dependencies, so there is no dependency health to assess. View diagnostics → Pass
Provenance & Transparency45
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 38 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability71
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 2486 tokens (~146/item across 17 items; 17 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
- No destabilizing schema changes in the last 30 days.Pass
Tool Coverage88
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 65% of tool parameters carry a description.Partial
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 17 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 18 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 3 Nov 26 +1
- Stability: 0.97 → pass security
- 2 Nov 26 −1
- Security disclosure: unverified → fail ▼ functional
- Stability: pass → 0.97 functional
- 1 Nov 26 0
- Security disclosure: fail → unverified ▼ functional
- 27 Oct 26 +1
- Stability: 0.97 → pass security
- 25 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 90 to 93. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 28 at this one. The score rises as the window fills, whether or not the server changes.
- 23 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.
- 20 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 73 to 77. That category is still filling its 30-day observation window: 22 days of observed history at the previous scan, 23 at this one. The score rises as the window fills, whether or not the server changes.
- 18 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 67 to 70. That category is still filling its 30-day observation window: 20 days of observed history at the previous scan, 21 at this one. The score rises as the window fills, whether or not the server changes.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 5 Nov 2026 · Analysed npm/@tesserai/cli@0.2.2
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | npm |
Background: How many MCP packages publish verified provenance →
Dependencies 0 packages
| Packages resolved | 0 |
|---|---|
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
apply_changes Apply changes ~98
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 version is written beside them. With preview: true, nothing is written and the result says what would change.
| Name | Type | Req | Description |
|---|---|---|---|
| ops | array | yes | – |
| preview | boolean | – | – |
| summary | string | – | One sentence saying what the change does |
No output schema declared.
No examples provided.
check_contrast Check contrast ~21
Run the contrast checks and list failing pairs with suggested fixes.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
component_guide Component guide ~97
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 and class prefix). Use it before writing UI, so new code uses the components rather than hand-styled elements.
| Name | Type | Req | Description |
|---|---|---|---|
| component | string | – | A component id, e.g. button, field, select |
No output schema declared.
No examples provided.
describe_operation Describe an operation ~24
One operation's input, as JSON Schema.
| Name | Type | Req | Description |
|---|---|---|---|
| name | string | yes | – |
No output schema declared.
No examples provided.
example_page Example page ~63
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 forms).
| Name | Type | Req | Description |
|---|---|---|---|
| page | string | yes | – |
No output schema declared.
No examples provided.
explain Explain a token ~51
Follow a token's references to its final value, in light or dark.
| Name | Type | Req | Description |
|---|---|---|---|
| path | string | yes | A token path, e.g. intent.primary.solid or button.height.md |
| scheme | string | – | – |
No output schema declared.
No examples provided.
get_component Get a component ~31
Read one component's full definition: parts, axes, and every recipe layer.
| Name | Type | Req | Description |
|---|---|---|---|
| component | string | yes | – |
No output schema declared.
No examples provided.
get_tokens Get tokens ~52
Read the tokens under a path prefix: values, per-mode values, and whether they were set by hand.
| Name | Type | Req | Description |
|---|---|---|---|
| prefix | string | yes | Path prefix, e.g. color.brand, intent.primary, space, button |
No output schema declared.
No examples provided.
guidelines Design guidelines ~275
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 a guideline speaks to.
| Name | Type | Req | Description |
|---|---|---|---|
| topic | string | yes | color: Palettes, color roles and scale steps, meaning colors, color alone; contrast: Text and UI contrast ratios, in light and dark; type: Type scale, sizes, line height, line length, weights; spacin… |
No output schema declared.
No examples provided.
import_design_system Import a design system ~1,049
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, then call this once with what you found. This tool already reads stylesheets (CSS variables, Tailwind v4 @theme, Sass/Less variables, plain rules), design-token files, next/font and Tailwind v3 configs by itself. Add what lives in code: - antd: the ConfigProvider theme / ThemeConfig.token (colorPrimary, colorError, colorSuccess, colorWarning, colorBgBase, colorTextBase, colorBorder, borderRadius, fontFamily, fontSize). - MUI: createTheme palette (primary.main, primary.contrastText, error.main, background.default and .paper, text.primary, divider, per mode), typography.fontFamily/fontSize, shape.borderRadius, spacing. - Chakra: extendTheme colors, fonts, radii, semanticTokens (default / _dark), and components' defaultProps colorScheme: a solid button is the scheme's 500 with white text in light, 200 with gray.800 text in dark. - Tailwind v3: tailwind.config theme.extend (colors, fontFamily, borderRadius) and the CSS variables it points at. - styled-components, Emotion, Theme UI: the theme objects given to ThemeProvider; follow imports to the palette they name. - Homegrown: color constants and the inline styles of buttons, cards, inputs and the page body. - Fluent UI v9: createLightTheme(brand) / createDarkTheme(brand) take a 16-step ramp; the primary button is brand[80] in light and brand[70] in dark (cite those ramp entries), plus any overrides spread over the theme. - Radix Themes: <Theme accentColor grayColor radius>; the primary is the accent scale's step 9 with --<accent>-contrast on it, text is gray-12, secondary text gray-a11; a custom palette file overrides those scales. Radix's own panel and surface colors aren't the app's card: leave card out unless the app sets one. - Angular Material (M3): mat.theme / a generated palette file gives tonal pa…
| Name | Type | Req | Description |
|---|---|---|---|
| dryRun | boolean | – | Only report what would come across |
| into | string | – | A system imported before (its link, /systems/<id>): update it with what the code changed, for the person to review, instead of making a new one |
| name | string | – | The system's name (default: from package.json) |
| notes | array | – | What the person should know that isn't a value, e.g. 'Dark mode comes from antd's darkAlgorithm, so it's filled in.' |
| tokens | object | yes | A DTCG document of the look you found, every token with $extensions['tesserai.source'] = 'path:line' |
No output schema declared.
No examples provided.
list_operations List operations ~52
Every operation apply_changes accepts, by group, with what it does. describe_operation gives one operation's exact input.
| Name | Type | Req | Description |
|---|---|---|---|
| group | string | – | Only this group, e.g. palette, intent, type, component |
No output schema declared.
No examples provided.
list_overrides List overrides ~21
What has been customised compared with tesserai's defaults.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
outline Design system outline ~68
A compact outline of the design system: palettes, meanings (intents), surfaces, type, spacing, radius, and every component with its parts and options.
| Name | Type | Req | Description |
|---|---|---|---|
| refresh | boolean | – | Wait for a fresh remote check (up to 5s). Omit for immediate local context and background freshness. |
No output schema declared.
No examples provided.
scan Scan the project ~141
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, class, style or sx restyling a component, by what they change; placement isn't counted); suggestions where the same override repeats; generated files edited by hand; and hard-coded colors and sizes with the token to use. Act on it: a suggestion is a change to propose to the system (a variant, a size, the component's corners), not to the app; confirm with the person before removing options or components.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
sync Sync the design system ~92
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 the developer edited are kept; the new version goes beside them. Call it before building UI when outline says the design changed.
| Name | Type | Req | Description |
|---|---|---|---|
| dryRun | boolean | – | Show the planned file changes without writing. |
No output schema declared.
No examples provided.
upload_scan Upload a scan ~80
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 edited generated files. Needs the project to follow its system's account link and a CLI login. Only when the person asks.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
usage Token usage ~31
What depends on a token: the tokens that reference it and the components it styles.
| Name | Type | Req | Description |
|---|---|---|---|
| path | string | yes | – |
No output schema declared.
No examples provided.
How do I install the tesserai MCP server?
tesserai runs locally as an npm package, launched with npx -y @tesserai/cli. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · @tesserai/cli
claude mcp add design-tesserai-tesserai -- npx -y @tesserai/cli
What is the tesserai MCP server?
tesserai is an MCP server listed in the public MCP registry as design.tesserai/tesserai. Your project's design system for coding agents: tokens, components, contrast checks, guidelines. This page covers its npm package (@tesserai/cli).
Is the tesserai MCP server safe to use?
tesserai scores 83 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 5 November 2026. It declares no install or post-install scripts. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the tesserai MCP server expose?
tesserai exposes 17 tools: import_design_system, outline, get_tokens, get_component, explain, and 12 more. Their descriptions and schemas cost roughly 2,246 tokens of context every time the server is loaded.
Is the tesserai MCP server still maintained?
tesserai is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What licence is the tesserai MCP server under?
tesserai declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.