AudioEye Accessibility Testing

com.audioeyePublished by audioeye.comv6.2.0Updated Oct 27, 2026

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

VerifiedSTDIODesktop onlyBrowser AutomationDeveloper Tools

Overview

AI-generated overview

AudioEye's local MCP server that scans live pages for accessibility issues and maps them back to JSX source files.

What you can do
  • Scan live pages with the AudioEye rules engine and report accessibility issues.
  • Map detected issues to the matching JSX source in the workspace.
  • Use source-context tools rooted at a configured workspace directory.
  • Discover project settings from a .audioeye-mcp.json file.
When to use it
Useful when you are fixing web accessibility problems in a React/JSX codebase and want an assistant to point from live-page violations to the source that causes them.
Requirements
Runs locally over stdio via npx (Node.js). Needs an AudioEye testing-SDK license: AUDIOEYE_TESTING_SDK_CLIENT_ID and AUDIOEYE_TESTING_SDK_CLIENT_TOKEN. Optionally set AUDIOEYE_MCP_WORKSPACE to the repo root; it defaults to the server's working directory. Desktop only.
Before you install
Requires AudioEye license credentials as environment variables; without them scans fail closed. The server reads source files under the configured workspace root, so point AUDIOEYE_MCP_WORKSPACE only at the intended repository. Page scans send the target URLs to AudioEye's service.

Installation

In SourceWeft

  1. Open AudioEye Accessibility Testing in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

README

This repository has no README.

Tools

0
SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

2
  1. v6.2.0LatestOct 2, 2026
  2. v6.1.0Sep 16, 2026

Score

25% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 days25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • License10 pts

    Declare a license in the repository or the registry entry.