Skip to main content
Glama
twodoorsdev

React Native Debugger MCP

by twodoorsdev

getConnectedApps

Retrieve connected apps in a React Native project by specifying the Metro server port. Simplify debugging with actionable insights into active app connections.

Instructions

Get the connected apps

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
metroServerPortYesThe port number of the Metro server

Implementation Reference

  • Handler function that fetches connected apps via Metro server's inspector endpoint, returns formatted app JSON or error.
    handler: async ({ metroServerPort }: GetConnectedAppsSchema) => {
    	const metroServerOrigin = `http://localhost:${metroServerPort}`;
    	try {
    		const apps = await queryAllInspectorAppsAsync(metroServerOrigin);
    
    		if (!apps || apps.length === 0) {
    			throw new Error(
    				'No connected apps found, please ensure that Metro is running',
    			);
    		}
    
    		return {
    			content: apps.map((app) => ({
    				type: 'text',
    				text: JSON.stringify(app, null, 2),
    			})),
    		};
    	} catch (error) {
    		return {
    			content: [
    				{
    					type: 'text',
    					text: `Error: ${(error as Error).message}`,
    				},
    			],
    			isError: true,
    		};
    	}
    },
  • Zod schema defining the input: metroServerPort (number). Includes TypeScript type export.
    export const getConnectedAppsSchema = z.object({
    	metroServerPort: z.number().describe('The port number of the Metro server'),
    });
    
    export type GetConnectedAppsSchema = z.infer<typeof getConnectedAppsSchema>;
  • Primary tool registration object defining name, description, input schema, and handler reference.
    export const getConnectedAppsTool: ToolRegistration<GetConnectedAppsSchema> = {
    	name: 'getConnectedApps',
    	description: 'Get the connected apps',
    	inputSchema: makeJsonSchema(getConnectedAppsSchema),
    	handler: async ({ metroServerPort }: GetConnectedAppsSchema) => {
    		const metroServerOrigin = `http://localhost:${metroServerPort}`;
    		try {
    			const apps = await queryAllInspectorAppsAsync(metroServerOrigin);
    
    			if (!apps || apps.length === 0) {
    				throw new Error(
    					'No connected apps found, please ensure that Metro is running',
    				);
    			}
    
    			return {
    				content: apps.map((app) => ({
    					type: 'text',
    					text: JSON.stringify(app, null, 2),
    				})),
    			};
    		} catch (error) {
    			return {
    				content: [
    					{
    						type: 'text',
    						text: `Error: ${(error as Error).message}`,
    					},
    				],
    				isError: true,
    			};
    		}
    	},
    };
  • Tool is imported and registered in the central createTools function, wrapping the handler.
    {
    	...getConnectedAppsTool,
    	// biome-ignore lint/suspicious/noExplicitAny: All tools validate their input schemas, so any is fine.
    	handler: (args: any) => getConnectedAppsTool.handler(args),
    },
Behavior2/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

No annotations are provided, so the description carries the full burden of behavioral disclosure. 'Get' implies a read operation, but the description doesn't specify permissions, rate limits, or what 'connected apps' entails (e.g., format, scope). It lacks critical behavioral details for a tool with no annotation coverage.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single, efficient sentence with no wasted words, making it appropriately sized. However, it's front-loaded with minimal content, which could be seen as under-specified rather than optimally concise.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given no annotations, no output schema, and a single parameter with full schema coverage, the description is incomplete. It doesn't explain what 'connected apps' are, the return format, or behavioral aspects, leaving significant gaps for the agent to understand the tool's context and usage.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The input schema has 100% description coverage, with the parameter 'metroServerPort' clearly documented. The description adds no parameter semantics beyond the schema, so it meets the baseline of 3 for high schema coverage without compensating value.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description 'Get the connected apps' states a clear verb ('Get') and resource ('connected apps'), but it's vague about what 'connected apps' means in this context and doesn't distinguish it from the sibling tool 'readConsoleLogsFromApp'. It provides a basic purpose but lacks specificity.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No guidance is provided on when to use this tool versus the sibling 'readConsoleLogsFromApp' or any alternatives. The description offers no context, prerequisites, or exclusions, leaving the agent with no usage direction.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Related Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/twodoorsdev/react-native-debugger-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server