tailwindshades-mcp

Generate a Tailwind palette

generate_palette

Read-onlyIdempotent

Create a full Tailwind CSS 50-950 palette from any color and get ready-to-paste theme, config, or CSS output, with shades matching Tailwind's own.

Instructions

Generates a full Tailwind CSS palette (50-950) from one color, ready to paste. Call it whenever you add a color to a Tailwind theme (e.g. "add a brand color #db4d53"), instead of writing a single variable or inventing shades. The input color stays exactly at its best-fit shade, and the other shades follow the closest Tailwind color, so they look like Tailwind's own.

Input Schema

TableJSON Schema

Name	Required	Description
`name`	No	Color name used in the code, e.g. "brand". Defaults to the closest Tailwind color, which replaces Tailwind's own palette of that name (e.g. red), so pass a name unless that is what the user wants
`color`	Yes	Any CSS color: hex (#db4d53), rgb(), hsl(), oklch() or a named color
`format`	No	Color format. Defaults to oklch for v4 and hex for older versions
`output`	No	theme: a v4 @theme block for the main CSS file. config: an object for theme.extend.colors in tailwind.config.js. css: plain CSS variables. Defaults to theme for v4 and config for older versions
`tailwindVersion`	No	The project's Tailwind CSS major version. Defaults to 4

Output Schema

TableJSON Schema

Name	Required	Description
`code`	Yes	The palette as code, ready to paste
`name`	Yes
`format`	Yes
`output`	Yes
`shades`	Yes
`inputShade`	Yes	Shade that holds the input color unchanged, e.g. 500
`tailwindVersion`	Yes
`closestTailwindColor`	Yes	Tailwind color whose curve the palette follows
`replacesTailwindColor`	Yes	True when the code replaces a default Tailwind palette (default color name, theme or config output)

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Oct 1, 2026

TDQS

A4.5/5.0

Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already declare readOnlyHint, idempotentHint and a closed world, so the safety profile is covered. The description adds genuine behavioral context beyond that: the input color is preserved at its best-fit shade while the remaining shades are derived from the closest Tailwind color, so the agent knows output is deterministic and visually consistent.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three sentences, front-loaded with what is produced, then the trigger condition, then a behavioral guarantee. No filler or repetition of schema content.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

An output schema exists, so return-value shape need not be restated. For a single-shot, five-parameter generation tool with fully documented params and annotations, the description covers everything an agent needs to select and invoke it correctly.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, so every parameter (name, color, format, output, tailwindVersion) is already documented with defaults and enums in the schema itself. The description adds no syntax or format detail beyond that, so the baseline of 3 is appropriate.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource with scope: generates a full Tailwind CSS palette (50-950) from one color, ready to paste. It also contrasts the tool with the naive alternative (writing a single variable or inventing shades), so an agent can tell why this exists rather than reaching for closest_tailwind_color.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicit trigger: 'Call it whenever you add a color to a Tailwind theme' with a concrete example prompt. It names the anti-pattern to avoid ('instead of writing a single variable or inventing shades'), giving clear when-to-use and when-not-to-use guidance.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server