Testing and QA MCP Servers

11 testing and qa MCP servers are cataloged, 1 with verified current-spec support.

MCP servers that drive testing and quality assurance: UI and device automation, end-to-end and API testing platforms, and test generation tools.

• agent-device - Earlier Revision

  Callstack's CLI and MCP server for driving iOS, Android, TV, desktop, and web apps from coding agents, run locally via agent-device mcp over stdio. Its hand-rolled MCP implementation hard-codes protocol revision 2025-11-25 in the initialize handshake; 2026-07-28 support is not implemented.

• Appium MCP - Earlier Revision

  The Appium project's own MCP server for driving mobile automation sessions on iOS and Android, including test creation tools. Published from the appium GitHub organization; npm and the registry agree on 1.92.2 (2026-08-13). No project surface names a supported MCP revision. Resolved from the published package: appium-mcp 1.92.4 depends on @modelcontextprotocol/sdk@1.30.0, whose artifact implements 2025-11-25. This records what the artifact implements, not what a deployment negotiates.

• Argent - Earlier Revision

  Distributed as npm:@swmansion/argent. Resolved from the published package: @swmansion/argent 0.21.0 depends on @modelcontextprotocol/sdk@1.30.0, whose artifact implements 2025-11-25. This records what the artifact implements, not what a deployment negotiates.

• BrowserStack MCP Server - Earlier Revision

  BrowserStack's official MCP server for its testing platform, run locally from the @browserstack/mcp-server npm package with BrowserStack account credentials. No vendor documentation surface names a supported MCP revision. npm's latest (1.2.36, 2026-08-11) is well ahead of the registry record (1.0.0, 2025-10-28). Resolved from the published package: @browserstack/mcp-server 1.2.36 depends on @modelcontextprotocol/sdk@1.30.0, whose artifact implements 2025-11-25. This records what the artifact implements, not what a deployment negotiates.

• mobile-mcp - Earlier Revision

  Mobile Next's MCP server for iOS and Android automation across simulators, emulators, and real devices, run locally over stdio. No vendor documentation surface names a supported MCP revision. Resolved from the published package: @mobilenext/mobile-mcp 1.0.2 depends on @modelcontextprotocol/sdk@1.26.0, whose artifact implements 2025-11-25. This records what the artifact implements, not what a deployment negotiates.

• PageSpeed Insights MCP - Spec Support Unverified

  Wraps Google's PageSpeed Insights and Chrome UX Report APIs in six workflow tools for auditing web performance, replacing an earlier set of nineteen endpoint-shaped tools in a breaking rewrite shipped 2026-08-26. It is distributed as the npm package pagespeed-insights-mcp and runs over stdio only, launched via npx. Callers must supply their own Google API key through the required GOOGLE_API_KEY environment variable; the server has no MCP-level authentication of its own. No README, changelog or docs page names a supported MCP specification revision, so spec_status is unknown. The maintainer is an individual Ukraine-based developer publishing under a personal npm account, not Google, which sets the authority as community rather than first_party.

• Playwright MCP - Spec Support Unverified

  Microsoft's Playwright MCP server: browser automation through structured accessibility snapshots rather than screenshots, run locally over stdio via npx @playwright/mcp. Hand check 2026-08-25: no MCP revision statement in the README or linked docs; @modelcontextprotocol/sdk ^1.25.2 appears only as a devDependency, so the SDK chain cannot ground a revision. Runs stdio by default, HTTP with --port.

• postman-mcp-server - Earlier Revision

  Listed with a remote endpoint. Resolved from the published package: @postman/postman-mcp-server 2.12.0 depends on @modelcontextprotocol/sdk@1.30.0, whose artifact implements 2025-11-25. This records what the artifact implements, not what a deployment negotiates.

• Shiplight MCP - Spec Support Unverified

  Distributed as npm:@shiplightai/mcp. First-party: the ai.shiplight registry namespace is domain-verified and the server fronts Shiplight's own agent-testing platform. No public repository; the registry record and npm package carry no repo URL. No MCP revision statement found (checked 2026-08-27) on shiplight.ai or in the package README.

• SmartBear MCP - Current Spec Verified

  Two product-specific remote endpoints are listed in the registry, for Bugsnag and for Zephyr. Both require authorization, so the spec revision is not yet verified. Resolved from the published package: @smartbear/mcp 0.37.0 depends on @modelcontextprotocol/server@2.0.0, whose artifact implements 2026-07-28. This records what the artifact implements, not what a deployment negotiates.

• Storybook MCP Addon - Spec Support Unverified

  Storybook addon that serves an MCP endpoint from the Storybook dev server (default http://localhost:6006/mcp) so agents can read component docs, generate stories, and run story tests. AI features are in preview and React-only per Storybook's docs. Hand check 2026-08-25: no MCP revision statement in the monorepo README, addon README or changelogs. The addon migrated from @modelcontextprotocol/sdk to the third-party tmcp library (addon 0.7.0 depends on tmcp ^1.19.4), which the SDK chain does not cover.