Local developer preview · Public review not yet submitted

Color intelligence,
inside the conversation.

Ask ChatGPT or Codex for an accessible theme, semantic design tokens, implementation-ready CSS, or an exact WCAG contrast audit. The plugin calls the same deterministic engine used by the CLI and live playground.

What works

Two focused, read-only tools

Compile an accessible color theme

Give the plugin one locked brand color and an optional canvas. It returns eleven semantic tokens, nine WCAG 2.2 pair audits, token-level provenance, CSS custom properties, and a visual interface preview.

Audit one exact contrast pair

Provide a foreground and background. The plugin returns the precise ratio plus normal-text, large-text, and non-text results.

No accounts. No write actions.

The developer preview does not sign users in, modify external services, or store color projects.

Architecture

One engine, another adapter

Your request in ChatGPT or Codex
              ↓
       read-only MCP tool
              ↓
  @tejsolpro/color core compiler
              ↓
tokens + evidence + provenance + CSS
              ↓
 optional in-chat visual result

The model does not invent the accessibility result. The plugin validates hexadecimal inputs, calls the shared compiler, and returns structured evidence the model can explain.

Try locally

Developer preview setup

  1. Clone the repository and run pnpm install.
  2. Start the server with pnpm --filter @tejsolpro/color-mcp dev.
  3. In ChatGPT Plugins, choose Add custom MCP server.
  4. Enter http://localhost:8787/mcp and choose no authentication.
  5. Create the personal plugin and test: “Create an accessible interface theme from #635BFF.”

This localhost flow is for development only. Public directory submission requires a stable HTTPS endpoint; that deployment is the next release step.

Boundaries

What it does not claim

  • It does not extract colors from uploaded images yet.
  • It does not generate dark mode yet.
  • It does not make unsupported color-psychology claims.
  • It does not replace human design review.
  • It is not yet published in the public plugin directory.

These boundaries keep the first plugin useful, testable, and honest.