Does AudioEye have an MCP server?
AudioEye maintains an official MCP server.
Local only and needs an AudioEye account with Testing SDK access.
- Access
- Built into the product
- Endpoint
- Local server: npm install -g @audioeye/testing-sdk-mcp, then audioeye-mcp setup
- Category
- Developer Tools
Ships inside AudioEye's own product rather than as a standalone server. Documented at developer.audioeye.com.
Ships inside the vendor's own app or CLI rather than as a standalone download.
Add it from the terminal, then restart your session:
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.
Open Settings → Developer → Edit Config and add the server to claude_desktop_config.json:
{
"mcpServers": {
"audioeye": {
"command": "npx",
"args": [
"-y",
"<package-from-readme>"
],
"env": {
"API_KEY": "…"
}
}
}
}Restart Claude Desktop after saving.
Add to .cursor/mcp.json in your project, or ~/.cursor/mcp.json for
every project:
{
"mcpServers": {
"audioeye": {
"command": "npx",
"args": [
"-y",
"<package-from-readme>"
],
"env": {
"API_KEY": "…"
}
}
}
}A green dot in Settings → MCP means it connected.
Add to .vscode/mcp.json:
{
"servers": {
"audioeye": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"<package-from-readme>"
]
}
}
}Then pick the server from the tools menu in Copilot's agent mode.
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.
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.