"How to test a React app" matching MCP servers:

. A good description should be concise and describe what the server enables users to do, e.g. * Enables to interact with WordPress sites...' Then a huge block? Actually the user message includes the README content inside tags, then after the readme, there is a large block of text starting with '{

An MCP server designed for React Native and Expo development that provides specialized tools for project scaffolding, architectural best practices, and troubleshooting. It enables AI assistants to guide users through setup, navigation configuration, and CI/CD processes using modern stacks like NativeWind and Zustand.

Lets coding agents manage apps in App Store Connect through workflow-level tools: shipping TestFlight builds, managing testers and groups, editing listings, replacing and reordering screenshots, handling subscriptions, replying to reviews, downloading sales reports, and submitting for App Review. It is read-only unless writes are explicitly enabled, and destructive actions run as dry runs until confirmed.

Enables users to upload Android .aab files to Google Play test tracks and iOS .ipa files to TestFlight, then promote or release them to production through fastlane. Also supports rollout updates, release status checks, and confirmation-gated publishing actions.

Enables test execution and management through MCP clients, allowing retrieval of projects, listing tests, executing tests with browser selection, and monitoring results.

Lets Claude and other AI agents work with Apple's developer API to manage app metadata, versions, review submissions, builds, TestFlight, customer reviews, reports, Xcode Cloud, devices, and team members, with optional read-only safeguards.

It enables AI agents and CI to run profile-driven SOAP/REST service tests with automatic login/session handling, test-customer locking, masked transaction-log/HAR catalog import, and cross-environment scenario execution.

Enables interaction with Apple's App Store Connect API through natural language to manage apps, beta testing, localizations, analytics, sales reports, and CI/CD workflows for iOS and macOS development.

MCP server for end-to-end QA automation: generates test scenarios, discovers Playwright locators, creates TypeScript test code, executes tests, and creates GitHub issues for failures.

Heimdall — MCP server for the Apple App Store Connect API & App Store Server API (StoreKit 2). 982 tools generated from Apple's official OpenAPI spec. Client-agnostic: Claude, Codex, Cursor, and any MCP client.

Enables management of App Store Connect resources including app reviews, TestFlight crashes, analytics reports, and Xcode Cloud workflows through natural language or AI agents.

Gives AI assistants complete, spec-driven access to Apple's App Store Connect API through 1300+ tools covering the full surface — apps and versions, TestFlight, Xcode Cloud, Game Center, App Clips, in-app purchases and subscriptions, pricing, review submissions, provisioning, analytics, sales and finance reports. It lets users automate submission workflows, manage multi-account credentials, and orchestrate builds and releases across any MCP client.

Enables remote interaction with the App Store Connect API via a stateless Cloudflare Worker, supporting app, build, beta group, review, and sales report management with bring-your-own-key authentication.

An MCP server that adds engineering discipline to AI-assisted development, enforcing evidence-gated TDD, security review, backup strategy, and deployment generation to turn AI-generated code into production-ready software.

A test harness for MCP servers that validates server JSON, tool schemas, performs golden file diffing and schema drift detection, and generates signed test reports with Shields.io badges.

Enables management of App Store Connect apps including registration, listing, IPA upload, store listing updates, and in-app purchase creation via natural language.

An end-to-end test MCP server built with FastMCP that exposes a REST API as a set of tools for AI agents. It enables LLMs to perform CRUD operations on an upstream API by mapping HTTP methods to MCP tools.

Enables automated analysis of test suite traces to identify timing races and state pollution, helping detect flaky test non-determinism in CI/CD workflows such as Datadog CI or Trunk.

Auto-generated MCP server that enables interaction with the Firebase App Distribution API, allowing users to manage distribution of pre-release app builds to testers through natural language commands.

Provides AI assistants with access to Capawesome documentation and Cloud management tools, enabling app, build, and deployment operations via API token authentication.

Enables coding agents to read Squally CI data, including test results, flakiness, and failure diagnostics.

Enables a coding agent to answer "is this iOS release ready?" by running read-only App Store Connect checks: build processing, App Review state, a 13-point submission preflight, release-notes policy linting, and App Store Server Notification reconciliation. The lone write capability is a dry-run-first, seven-gate submission tool that always requires explicit confirmation.

Connects AI coding assistants to Gaffer test history and coverage data to analyze project health, debug failures, and identify untested code areas. It enables tools to track test stability, cluster failures by root cause, and monitor code coverage trends across projects.

StorePilot is an MCP server that unifies app portfolio management across Google Play and App Store Connect, with tools for installs, earnings, reviews, cross-store parity, and gated releases.

Enables AI assistants to summarize Playwright test runs, identify flaky tests, heuristically triage failures, generate Playwright test stubs, and retrieve recent GitHub CI status through MCP tool calls.

Enables AI coding tools to validate local projects and publish or update applications to Bedengan App Hub via API, with automated checks and live deployment without manual approval.

Enables scanning Python repos for dead code and automatically drafting a branch + PR for the safe subset (unused single-name imports) after running the repo's full test suite. All other findings are reported without modification, and a human always merges.

Automates the full setup and deployment of Ballerina + Apache ActiveMQ integrations inside a WSO2 Integrator workspace, from broker validation to a runnable BI-low-code-ready project.

Record an agent's MCP tool-call workflow once, replay it deterministically for zero tokens, and get a receipt — a snapshot-testing and deterministic-execution layer for Agent Skills.

Stops your AI from re-introducing bugs, leaking provider keys, or weakening tests. Bug fixes become permanent regression guards; blocked mistakes become AI lessons the agent reads and learns from before its next edit.