Detox MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| DETOX_PROJECT_PATH | No | Path to React Native project | Current directory |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| detox_buildC | Build the app for Detox testing. Runs the build command from your Detox configuration. |
| detox_testC | Run Detox E2E tests with full options for configuration, retries, artifacts, and more. |
| detox_initC | Initialize Detox in a React Native project. Creates e2e folder structure and configuration. |
| detox_read_configC | Read and parse the current Detox configuration file (.detoxrc.js or similar). |
| detox_list_configurationsB | List all available Detox configurations (e.g., ios.sim.debug, android.emu.debug). |
| detox_validate_configB | Validate Detox configuration for errors and warnings. |
| detox_create_configC | Generate a new Detox configuration file for your React Native project. |
| detox_list_devicesC | List available iOS simulators and Android emulators. |
| detox_generate_testC | Generate a complete Detox test file from a description. |
| detox_generate_matcherC | Generate Detox matcher code for element selection (by.id, by.text, etc.). |
| detox_generate_actionC | Generate Detox action code (tap, typeText, scroll, etc.). |
| detox_generate_expectationC | Generate Detox expectation/assertion code (toBeVisible, toHaveText, etc.). |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| detox-test | Run Detox tests with smart defaults and formatted results |
| detox-generate | Generate Detox test code from a natural language description |
| detox-setup | Initialize and configure Detox in a React Native project |
| detox-debug | Debug a failing Detox test with screenshots and view hierarchy |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| Detox Configuration | Current Detox configuration from .detoxrc.js or similar |
| Available Devices | List of iOS simulators and Android emulators |
| Test Files | List of Detox test files in the e2e directory |
| Matchers API | Detox element matchers reference (by.id, by.text, etc.) |
| Actions API | Detox element actions reference (tap, typeText, etc.) |
| Expectations API | Detox assertions reference (toBeVisible, toExist, etc.) |
| Device API | Detox device control reference (launchApp, setLocation, etc.) |
TDQS
Scored across 12 tools
Every tool has a clearly distinct purpose with no ambiguity. The tools are well-organized around specific Detox operations like building, configuration management, code generation, testing, and device listing. Each tool name directly indicates its unique function, making it easy for an agent to select the correct one.
All tools follow a consistent 'detox_verb_noun' pattern throughout, such as detox_build, detox_create_config, and detox_generate_action. This uniform naming convention enhances readability and predictability, allowing agents to easily understand and navigate the toolset without confusion.
With 12 tools, the count is well-scoped and appropriate for a Detox testing server. Each tool serves a specific, necessary function in the E2E testing workflow, from setup and configuration to test generation and execution, ensuring comprehensive coverage without being overwhelming.
The toolset provides complete coverage of the Detox domain, including initialization, configuration management, code generation for actions/expectations/matchers/tests, device listing, building, and testing. There are no obvious gaps, and the tools support the full lifecycle of Detox E2E testing workflows.