Paletteget MCP Server

paletteget-mcp

An MCP server for the PaletteGet color palette library: 90 palettes across App, Web and Mini App UIs, each organized into 10 design roles and checked against WCAG contrast requirements.

It exists so your AI coding tool stops inventing hex values. Instead of guessing, the model calls a tool and gets the real role colors, the measured contrast ratios, and the pairing advice that ships with the palette.

No API key, no sign-up.

Use the hosted endpoint (nothing to install)

https://paletteget-mcp.y7206062.workers.dev/mcp

{
  "mcpServers": {
    "paletteget": {
      "type": "http",
      "url": "https://paletteget-mcp.y7206062.workers.dev/mcp"
    }
  }
}

ChatGPT: Settings → Connectors → Add custom connector → paste the URL.

The hosted server embeds the dataset at deploy time, so it never depends on the site being reachable and answers in a few milliseconds.

Or run it locally (stdio)

git clone https://github.com/yang7206/paletteget-mcp.git
cd paletteget-mcp
npm install

{
  "mcpServers": {
    "paletteget": {
      "command": "node",
      "args": ["/absolute/path/to/paletteget-mcp/index.mjs"]
    }
  }
}

The stdio server fetches live data from the public JSON endpoints and caches it for 10 minutes.

Tools

Example call and result:

suggest_palette { "query": "dark finance dashboard", "limit": 2 }

- Ink Blue Night / 墨蓝夜（app，分 94）
  slug: mo-lan-ye　主色: #4c8df6
  场景: Finance & analytics apps (dark mode)
  命中: 标签:dark, 场景:finance

Environment variables (stdio server)

Behind a firewall, Node's built-in fetch ignores the usual proxy variables, so set PALETTEGET_PROXY explicitly.

Test

npm run smoke

The smoke test speaks the MCP stdio protocol directly and exercises every tool against a local fixture, so it runs offline. Point PALETTEGET_API at the live site to test against production.

Maintaining the hosted worker

The worker (worker.mjs) is a hand-written, stateless subset of MCP Streamable HTTP (initialize, tools/list, tools/call, ping) with no SDK dependency, which keeps it small and Workers-native.

# 1. Regenerate the embedded dataset (run both locales)
SITE_URL=https://paletteget.com SITE_LOCALE=zh node --import ./alias-loader.mjs build-data.mjs
SITE_URL=https://paletteget.com SITE_LOCALE=en node --import ./alias-loader.mjs build-data.mjs

# 2. Local check
npx wrangler dev          # POST JSON-RPC to http://127.0.0.1:8787/mcp

# 3. Deploy (needs CLOUDFLARE_API_TOKEN with Workers Scripts:Edit)
npx wrangler deploy

build-data.mjs reuses the site's own i18n modules through alias-hooks.mjs, so names, scenes and advice stay identical to the published site. data/ is generated at build time and never committed.

Data and license

Code is MIT (see LICENSE). Palette data comes from paletteget.com and may be reused freely in personal and commercial projects; a credit link is appreciated.

Machine-readable forms of the same data, if you would rather skip MCP entirely:

• Full dataset: https://paletteget.com/api/index.json
• One palette: https://paletteget.com/palette-list/{platform}/{slug}/index.json
• CSS variables: https://paletteget.com/palette-list/{platform}/{slug}/index.css
• Agent guide: https://paletteget.com/llms.txt