Does AudioEye have an MCP server?

Yes Official

AudioEye maintains an official MCP server.

Local only and needs an AudioEye account with Testing SDK access.

Verified 2026-09-29 against vendor docs
Access
Built into the product
Endpoint
Local server: npm install -g @audioeye/testing-sdk-mcp, then audioeye-mcp setup
The receipts
In-product Local server: npm install -g @audioeye/testing-sdk-mcp, then audioeye-mcp setup

Ships inside AudioEye's own product rather than as a standalone server. Documented at developer.audioeye.com.

Connect it

Ships inside the vendor's own app or CLI rather than as a standalone download.

Add it from the terminal, then restart your session:

terminal
claude mcp add audioeye -- npx -y <package-from-readme>

Swap in the exact package and flags from the package page — most servers need an API key passed as an environment variable.

Add --scope user to make it available in every project.

Setup sponsor · open Put your product right here, under the setup steps of all 645 verdict pages. One sponsor at a time. $149 first month, then $399/mo →
Questions
Does AudioEye have an official MCP server?

Yes. AudioEye maintains an official MCP server.

How do I connect AudioEye to Claude?

Run the server locally and register it in Claude's MCP config. In Claude Code that's a single "claude mcp add" command; in Claude Desktop you add it to claude_desktop_config.json.

How is this verdict verified?

Published to the MCP Registry under AudioEye's verified namespace com.audioeye as the npm package @audioeye/testing-sdk-mcp (maintained by audioeye.com accounts); developer.audioeye.com/mcp documents install, sign-in and its scan and fix tools. GitHub metadata is refreshed every six hours.

How we know

Published to the MCP Registry under AudioEye's verified namespace com.audioeye as the npm package @audioeye/testing-sdk-mcp (maintained by audioeye.com accounts); developer.audioeye.com/mcp documents install, sign-in and its scan and fix tools.

  • github data refreshed 2026-09-29, then every 6 hours
  • vendor docs verified on 2026-09-29

Spotted something out of date? Tell us — corrections ship same-day.

Also in Developer Tools

See all Developer Tools servers →