Tune Your Theme in the Browser, Pull It into Claude Code Live
2026-10-08 · zhoujingkang · Founder
You spent twenty minutes tuning a theme in the browser: adjusted the primary, fixed three contrast warnings, checked it in colorblind simulation. Now your AI coding agent needs those exact colors — and your options are re-describing the palette in a prompt, exporting a file that goes stale, or hoping the agent guesses right. ColorwayKit's MCP server closes that loop: save the theme as a cloud project, and your agent pulls it live — with every pair still measured. This article shows the round trip.
The problem: exported files go stale
The DESIGN.md workflow solves the "agent invents colors" problem by baking a verified token contract into your repo. But the moment you tune a color in the browser — shift a primary, fix a contrast warning, adjust for colorblind distinguishability — the file in your repo is out of date. Re-export, re-commit, re-pull: three manual steps every time you change your mind.
And if you're working across multiple projects, each one needs its own file. The agent has no way to know which version is current — it just reads whatever was committed last.
The round trip: tune, save, pull
ColorwayKit's MCP server adds a live path. Tune in the browser, hit save, and the theme becomes a cloud project. Your agent then calls get_theme_by_project — no project ID needed if you only have one, or use list_projects to pick from several — and receives the same verified token set with every pair still measured.
The dual-standard report comes with it: every text/background pair carries both a WCAG 2.1 ratio and an APCA Lc value, plus a colorblind distinguishability chapter that re-measures all pairs under four types of color vision deficiency.
What the agent actually receives
get_theme_by_project returns the same structure as get_theme — 23 named semantic roles for light and dark, every pair with its WCAG ratio and APCA Lc, and fix suggestions that satisfy both standards simultaneously. The difference is the source: your saved cloud project instead of a freshly derived one.
Real numbers from a saved project (brand #d9480f): primary on background measures 4.12:1 — below the 4.5:1 body-text threshold, flagged as a contrast risk with a suggested fix. Under deuteranopia simulation, it drops further to 1.95:1. The report doesn't hide these — it surfaces them so your agent can adjust.
Free to start, Plus to export
MCP access comes with a free account: 5 calls per day on Free, 1,000 per month on Plus, unlimited on Pro. The colorblind distinguishability report export (Markdown and JSON) is a Plus benefit at 30 reports per month — unlimited on Pro.
Continue with a tool
References
FAQ
Do I need a project ID to pull my saved theme?
No — if your account has only one saved project, get_theme_by_project defaults to the most recently updated one. Use list_projects to get IDs when you have several.
Is my saved project data secure?
Yes — the MCP server enforces ownership server-side: an agent can only read projects belonging to the token's account. Projects are private to your ColorwayKit account.
What happens when I update the theme after the agent pulled it?
The next pull gets the latest version — the server always returns the current state of the saved project. If you want the agent to work from a frozen version, export a DESIGN.md instead and commit it.
Can multiple agents pull the same project?
Yes — any agent connected with a valid token from your account can read the same cloud projects. The quota is per-account, not per-agent.
Try it on your own brand color
Paste one hex into the Brand Theme Engine and get a full light & dark web theme — semantic tokens, contrast-checked, export-ready.
Open the Brand Theme Engine →