Skip to main content
Glama
atom2ueki

MCP Server for iOS Simulator

launch-app

Launch an iOS app on a simulator by specifying the session ID and bundle ID, enabling programmatic control through the MCP Server for iOS Simulator.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
bundleIdYes
sessionIdYes

Implementation Reference

  • Registers the 'launch-app' MCP tool, including input schema (sessionId, bundleId) and handler function that delegates to simulatorManager.launchApp
    this.server.tool(
      'launch-app',
      {
        sessionId: z.string(),
        bundleId: z.string()
      },
      async ({ sessionId, bundleId }) => {
        fileLogger.info(`Launching app on simulator: ${sessionId}`, { bundleId });
        try {
          const success = await simulatorManager.launchApp(sessionId, bundleId);
          
          if (!success) {
            return {
              content: [{
                type: 'text',
                text: `Failed to launch app on session: ${sessionId}`
              }],
              isError: true
            };
          }
          
          return {
            content: [{
              type: 'text',
              text: `App launched on session: ${sessionId}`
            }]
          };
        } catch (error) {
          fileLogger.error(`Failed to launch app on session: ${sessionId}`, { error });
          return {
            content: [{
              type: 'text',
              text: `Error: ${error instanceof Error ? error.message : String(error)}`
            }],
            isError: true
          };
        }
      }
    );
  • Handler function for the launch-app tool that logs the action, calls simulatorManager.launchApp, and returns success/error response
    async ({ sessionId, bundleId }) => {
      fileLogger.info(`Launching app on simulator: ${sessionId}`, { bundleId });
      try {
        const success = await simulatorManager.launchApp(sessionId, bundleId);
        
        if (!success) {
          return {
            content: [{
              type: 'text',
              text: `Failed to launch app on session: ${sessionId}`
            }],
            isError: true
          };
        }
        
        return {
          content: [{
            type: 'text',
            text: `App launched on session: ${sessionId}`
          }]
        };
      } catch (error) {
        fileLogger.error(`Failed to launch app on session: ${sessionId}`, { error });
        return {
          content: [{
            type: 'text',
            text: `Error: ${error instanceof Error ? error.message : String(error)}`
          }],
          isError: true
        };
      }
    }
  • Zod input schema for launch-app tool: requires sessionId (string) and bundleId (string)
    {
      sessionId: z.string(),
      bundleId: z.string()
  • SimulatorManager.launchApp helper method that retrieves the simulator session and calls the underlying appium-ios-simulator library's launchApp(bundleId) method
    /**
     * Launches an app on the simulator
     */
    async launchApp(sessionId: string, bundleId: string): Promise<boolean> {
      const session = this.sessions.get(sessionId);
      if (!session) {
        fileLogger.warn(`Session not found: ${sessionId}`);
        return false;
      }
    
      try {
        await session.simulator.launchApp(bundleId);
        fileLogger.info(`App launched on simulator for session: ${sessionId}`);
        return true;
      } catch (error) {
        fileLogger.error(`Failed to launch app for session: ${sessionId}`, { error });
        return false;
      }
    }
Behavior1/5

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

Tool has no description.

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

Conciseness1/5

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

Tool has no description.

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

Completeness1/5

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

Tool has no description.

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

Parameters1/5

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

Tool has no description.

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

Purpose1/5

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

Tool has no description.

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

Usage Guidelines1/5

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

Tool has no description.

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/atom2ueki/mcp-server-ios-simulator'

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