React Native Debugger MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
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 |
|---|---|
| getConnectedAppsC | Get the connected apps |
| readConsoleLogsFromAppA | Reads console logs from a connected React Native app through the debugger WebSocket |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 2 tools
The two tools have clearly distinct purposes: one retrieves a list of connected apps, while the other reads console logs from a specific app. There is no overlap or ambiguity between them, making it easy for an agent to select the correct tool based on the task.
The tool names follow a consistent verb_noun pattern (getConnectedApps, readConsoleLogsFromApp), with both using camelCase. However, the second tool name is quite long and descriptive, which slightly deviates from the simplicity of the first, but the overall naming convention is clear and predictable.
With only two tools, the server feels thin for a React Native debugger domain, which typically involves more operations like inspecting elements, setting breakpoints, or managing app state. This limited set may not cover essential debugging workflows, indicating an under-scoped tool surface.
The tool set is severely incomplete for a debugger server. It lacks basic debugging operations such as inspecting app components, setting breakpoints, evaluating expressions, or controlling app execution. This creates significant gaps that will likely cause agent failures in comprehensive debugging tasks.