grayscale-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| generate_paletteA | Generate a grayscale luminance scale plus one palette per base color, exactly as grayscale.design/app does. Each shade matches the grayscale shade's luminance while keeping the base hue and saturation. Returns every swatch (label, hex, rgb, hsl, oklch, luminance) and a share link that opens the same palette on the site. |
| export_paletteA | Export palettes as the code the site's "Export Your Colors" and "Tailwind Auto-Dark Mode" sections produce: tailwind (theme colors object), radix (light + dark scales), css-vars, scss, less, stylus, auto-dark-css (CSS variables that flip in dark mode), auto-dark-tailwind (tailwind.config.js for those variables), svg (the "Export Svgs" swatch sheet) or json (raw swatch data). |
| luminance_scaleA | Return the grayscale luminance scale (step 1 on the site): luminance targets, shade labels and the gray for each shade. Use a preset, change the shade count, or pass custom targets. |
| color_infoA | Parse a color the way the site does and return hex, rgb, hsl, oklch, its luminance (the site's color value, 0-100), the site's auto name, and WCAG contrast ratios against white, black and an optional second color. |
| adjust_shadeA | Keep a color's hue and saturation and find the lightness that hits a target luminance, using the site's solver. This is how every palette shade is made. |
| suggest_colorsA | The site's suggested-color swatches: analogous (+-60), triadic (+-120) and complementary hues of a base color, all at luminance 40. |
| false_colorA | The site's /false-color tool: pick a gray (0-255) or a luminance, then get a color of any hue and saturation with that same luminance. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 7 tools
Most tools target clearly distinct operations: palette generation, exporting, color parsing, shade adjustment, suggestions, and false-color mapping. The closest overlaps are generate_palette vs. luminance_scale and adjust_shade vs. false_color, but their descriptions make the boundaries reasonably clear.
The set mixes verb_noun names such as export_palette, generate_palette, adjust_shade, and suggest_colors with noun-based names like luminance_scale, color_info, and false_color. The pattern is still readable, but it is not a single consistent convention.
Seven tools is well-scoped for a grayscale palette and color utility server. Each tool corresponds to a distinct site capability, and none feels redundant or extraneous.
The surface covers the apparent domain well: scale generation, palette generation, multiple export formats, color parsing, luminance adjustment, suggestions, and false-color exploration. There are no obvious dead ends for core palette workflows.