AccessLint Color Contrast MCP

A designer is mid-sentence in Claude, working through a brand refresh. She's just decided on a new accent color and she wants to know — right now, in the same conversation — whether it passes contrast against her existing background palette. The usual answer is "open a separate browser tab, paste the hex codes into a contrast checker, copy the result back, and continue." The AccessLint MCP server replaces that whole detour with a single tool call.

AccessLint exposes programmatic color contrast analysis, calculated against WCAG 2.1, directly to Claude Desktop and other MCP-compatible clients. You hand the AI two colors. The AI hands them to AccessLint. AccessLint returns the contrast ratio, the AA and AAA pass/fail for normal text and large text, and a clear answer the AI can use in its next sentence. No tab switching, no copy-paste, no "let me look that up for you."

The usefulness compounds. Once the contrast tool is in the conversation, you can ask the AI to walk through your whole palette systematically: which combinations pass for body text, which only pass for headlines, which fail entirely. You can ask it to suggest the smallest hue adjustment that would push a near-miss into compliance. You can hand it a screenshot, get the hex codes pulled out, and check them all in one go.

The audience is designers and design system owners who live half their week in an AI conversation and don't want accessibility checks to be the one thing that breaks their flow. It's also useful for content writers picking link colors, marketing teams checking ad mockups, and developers verifying button states.

Made by the AccessLint team. The <span class="whitespace-nowrap">a-gnt</span> Community catalogs it because color contrast is the single most common WCAG failure shipped to production, and the cheaper it is to check, the less of it survives.

Pair with Accessible Color System for the deeper palette design, or Color Contrast Fix for one-shot remediation.