Ext Ops Panel
Open dashboard
Comparison

Design vs AudioEye Accessibility Testing

Design is a plugin bundle for AI coding tools published by Anthropic. Marketplaces we read that list it: 1 (Claude: knowledge-work-plugins). AudioEye Accessibility Testing is an MCP server published by audioeye.com. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-15. This pair was picked by a reader, not by our comparison rule, so search engines are asked not to index the page.

Where each is published

Where each is published
MarketplaceDesignAudioEye Accessibility Testing
Claude: knowledge-work-plugins Listed
Version: 1.2.0
Forks (GitHub): 3 361
Stars (GitHub): 29 647
Not marked · First seen
Not listed
Official MCP Registry Not listed Listed
Version: 6.2.0
Downloads/month (npm): 536
Downloads/week (npm): 73
Not marked · First seen

Each figure is the marketplace's own and is never added up across marketplaces. A marketplace that publishes no figure shows none: no number is not zero.

The facts side by side

Design vs AudioEye Accessibility Testing
FactDesignAudioEye Accessibility Testing
Marketplaces that list it11
Stars (GitHub) (differs)29 647No figure on GitHub
Forks (GitHub) (differs)3 361No figure on GitHub
Last releaseNot publishedNot published
Where it runs (differs)Installs as a plugin bundleOn your machine (@audioeye/testing-sdk-mcp)
Transport (differs)Not statedstdio
Tools it declaresNot publishedNot published
Environment variables it asks for (differs)Not published3, secrets among them: 2
Parts of the bundle (differs)16Not a bundle
LicenceNot statedNot stated
Repository (differs)github.com/anthropics/knowledge-work-pluginsgithub.com/audioeye/testing-sdk
Changes in the last 7 days00
First seen2026-10-112026-10-11

Lines where the two differ have a tinted background and bold values. Where the data itself says which value is better (more marketplaces, a larger figure of the same marketplace, a fresher release, a verified mark on a marketplace that lists both), the better one is also marked green with ▲ and the worse one red with ▼. Where it runs, the transport, the tools, the settings, hooks, the bundle's parts, the licence and the week's changes are marked only as different: more or fewer is not better in itself.

What each says it does

Design

In its own words, on Claude: knowledge-work-plugins:

Accelerate design workflows — critique, design system management, UX writing, accessibility audits, research synthesis, and dev handoff. From exploration to pixel-perfect specs.

AudioEye Accessibility Testing

In its own words, on Official MCP Registry:

Scans live pages with the AudioEye rules engine and maps accessibility issues to JSX source.

How to run each

Design As a Claude Code plugin

Claude Code
/plugin marketplace add anthropics/knowledge-work-plugins
/plugin install design@knowledge-work-plugins

AudioEye Accessibility Testing As a local MCP server: npm package

Claude Code
claude mcp add --env "AUDIOEYE_TESTING_SDK_CLIENT_ID=<YOUR_AUDIOEYE_TESTING_SDK_CLIENT_ID>" --env "AUDIOEYE_TESTING_SDK_CLIENT_TOKEN=<YOUR_AUDIOEYE_TESTING_SDK_CLIENT_TOKEN>" --transport stdio testing-sdk-mcp -- npx -y @audioeye/testing-sdk-mcp

Requires: AUDIOEYE_TESTING_SDK_CLIENT_ID (secret), AUDIOEYE_TESTING_SDK_CLIENT_TOKEN (secret)

Commands built only from what the marketplaces declare; the full set for every client is on each card.

Tools each declares

Neither one's marketplaces publish a list of tools, so there is nothing to compare.

Settings each asks for

The marketplaces of Design publish no settings it asks for, so we do not compare settings.

What it can do: Design · What it can do: AudioEye Accessibility Testing · Compare two other plugins

Data comes from the public marketplace file https://github.com/anthropics/knowledge-work-plugins/blob/HEAD/.claude-plugin/marketplace.json. Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.

Where the data comes from: how the catalog is built