Color systems, callable.

The Clove Colors MCP server gives compatible agents the same deterministic engine as the browser. It is read-only, stateless, and requires no account.

Connect

Point your MCP client at /api/mcp. Replace the domain below with the deployed Clove Colors origin.

{
  "mcpServers": {
    "clove-colors": {
      "url": "https://colors.connorlove.com/api/mcp"
    }
  }
}

Local development uses http://localhost:3000/api/mcp.

Tools

  • generate_palette — deterministic colors from count, harmony, seed, and optional locks.
  • build_theme — ramps, semantic roles, light/dark modes, and pair-level contrast results.
  • check_contrast — WCAG 2.2 ratios for supplied foreground/background pairs.
  • search_palettes — original curated palettes by text and measurable properties.
  • export_tokens — CSS, Tailwind v4, DTCG 2025.10, or plain JSON.
generate_palette({
  "count": 5,
  "harmony": "analogous",
  "seed": 1847
})

Every result includes schemaVersion: 1, structured content, and a short text summary.

Resources

  • clove://palettes/{slug} — one curated palette with provenance.
  • clove://docs/color-model — the engine’s OKLCH, gamut, and contrast model.

Limits & privacy

Requests are capped at 64 KB and responses at 256 KB. Arrays, strings, numbers, and result counts are bounded. Tools make no external network calls and never write palettes to a database.

Clove Colors does not log palette payloads or full MCP request bodies. The hosting provider may still process ordinary request metadata such as IP address, timestamp, path, and response status. Deployments should enforce 60 requests per minute per IP for /api/mcp and return 429 when exceeded.