Everything the server exposes: 18 tools, 1 resource, and 5 prompts. You rarely call these by hand, since your assistant picks them, but knowing what exists helps you ask for the right thing.
The remote server returns data and instructions; the host assistant performs local file edits and commands.
Every project-scoped tool takes a projectId (a UUID from find-project, or the projectId in your repo's bezel.json).
Guided setup
| Tool | Parameters | What it does |
|---|
setup-project | None | Returns a resumable setup workflow: CLI installation, project selection, output folder, token fetching/generation, app integration, and optional live preview with Crystal. The host performs local actions. Also available as a prompt. |
Discovery
| Tool | Parameters | What it does |
|---|
find-project | query? | With no query, every project you own as name + ID. A name (case-insensitive) or UUID resolves one project; ambiguous or missing names return candidates to choose from |
get-project-manifest | projectId | Structure without values: groups, token counts, types, contexts |
Repo sync
| Tool | Parameters | What it does |
|---|
get-design-tokens-file | projectId, version? | The exact design-tokens.json the app's Download button produces, for writing to disk, plus project name and version. version is latest (default) or a published semver; an unpublished one returns the available versions |
Reading tokens
| Tool | Parameters | What it does |
|---|
query-tokens | projectId, groupPath?, tokenType?, search?, exportName?, contextKey?, resolveAliases? | The workhorse: filter tokens by any combination |
get-token-by-path | projectId, tokenPath, contextKey?, resolveAliases? | One token by dot-path, with every context value and alias detail |
get-token-bundle | projectId, intent | Curated set for a task. Intents: theming-setup, button, card, input, form, auth-page, dashboard-shell |
Contexts and themes
| Tool | Parameters | What it does |
|---|
get-project-contexts | projectId | Context groups and their values: theme modes, platforms, brands |
resolve-context | projectId, contextGroup, contextValue | Validate a context name, returning the canonical value or a structured error |
Generating code
| Tool | Parameters | What it does |
|---|
export-tokens | projectId, format, groupPath?, tokenType?, search?, exportName?, contextKey?, prefix?, includeAll? | Emit css-variables, js-object, or ts-object. Aliases resolved. Only tokens with an export name are emitted unless includeAll is true, which adds the rest by kebab-cased path (base-color-primary-500) |
get-framework-overrides | projectId, framework, version?, groupPath?, tokenType?, search?, contextKey? | Config for tailwind (v3, v4), shadcn (v0, v2), or mantine (v7) |
Color and unit math
Deterministic: computed by the server, not estimated by the model.
| Tool | Parameters | What it does |
|---|
contrast-check | foreground, background | WCAG ratio, grade (AAA / AA / AA Large / Fail), and recommendations |
color-convert | color, targetFormat, manipulation?, mixColor? | Between hex, rgb, hsl, oklch; optional lighten, darken, saturate, desaturate, mix |
color-ramp | baseColor, steps, endColor?, colorSpace? | Evenly-spaced scale, 2–20 steps, in rgb, hsl, lab, lch, or oklch |
unit-convert | value, fromUnit, toUnit, rootFontSize?, parentFontSize? | Between px, rem, em. Needs an explicit root size for px↔rem |
Review
| Tool | Parameters | What it does |
|---|
design-review | projectId, componentDescription, tokenPathsUsed?, contextKey? | Reviews spacing, typography, color, states, and accessibility against your tokens |
Chat history
| Tool | Parameters | What it does |
|---|
get-chat-history | projectId | Past user and assistant messages in chronological order. Sensitive data redacted |
search-chat-history | projectId, query | Keyword search across those messages, each match labeled by role |
Resources
Readable by URI in editors that support MCP resources.
| URI | Contents |
|---|
bezel://projects | Your projects, with IDs and names |
Prompts
Prompts are optional, reusable instructions for clients that support MCP prompts. In Claude Code they appear as slash commands like /mcp__bezel__manifest-first-workflow.
You can also ask in plain language. setup-project is available as a regular tool, so setup does not require prompt support.
| Prompt | Contents |
|---|
setup-project | /mcp__bezel__setup-project [project] [version]. Pick a project, then complete the missing Quick Start steps in this repo. See Workflows |
sync-project | /mcp__bezel__sync-project [project] [version]. Pull design-tokens.json for the project in bezel.json and run bezel build. See Workflows |
manifest-first-workflow | The recommended path: manifest, then groups, then targeted queries |
context-resolution | Working with contexts and themes |
safe-usage-guide | Staying inside context limits and citing token paths |