Skip to main content
Glama
atom2ueki

MCP Server for iOS Simulator

tap

Simulate touch interactions on iOS simulators by sending precise X and Y coordinates via the Model Context Protocol, enabling programmatic control for testing and development.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
sessionIdYes
xYes
yYes

Implementation Reference

  • The MCP tool handler function for the 'tap' tool. It validates input, calls the simulator manager's performTap method, and returns a success or error response.
    async ({ sessionId, x, y }) => {
      fileLogger.info(`Performing tap on simulator: ${sessionId}`, { x, y });
      try {
        const success = await simulatorManager.performTap(sessionId, x, y);
        
        if (!success) {
          return {
            content: [{
              type: 'text',
              text: `Failed to perform tap on session: ${sessionId}`
            }],
            isError: true
          };
        }
        
        return {
          content: [{
            type: 'text',
            text: `Tap performed at (${x}, ${y}) on session: ${sessionId}`
          }]
        };
      } catch (error) {
        fileLogger.error(`Failed to perform tap on session: ${sessionId}`, { error });
        return {
          content: [{
            type: 'text',
            text: `Error: ${error instanceof Error ? error.message : String(error)}`
          }],
          isError: true
        };
      }
    }
  • Zod schema defining the input parameters for the 'tap' tool: sessionId (string), x (number), y (number).
    {
      sessionId: z.string(),
      x: z.number(),
      y: z.number()
    },
  • Registration of the 'tap' tool using McpServer.tool() method, specifying name, input schema, and handler function.
    this.server.tool(
      'tap',
      {
        sessionId: z.string(),
        x: z.number(),
        y: z.number()
      },
      async ({ sessionId, x, y }) => {
        fileLogger.info(`Performing tap on simulator: ${sessionId}`, { x, y });
        try {
          const success = await simulatorManager.performTap(sessionId, x, y);
          
          if (!success) {
            return {
              content: [{
                type: 'text',
                text: `Failed to perform tap on session: ${sessionId}`
              }],
              isError: true
            };
          }
          
          return {
            content: [{
              type: 'text',
              text: `Tap performed at (${x}, ${y}) on session: ${sessionId}`
            }]
          };
        } catch (error) {
          fileLogger.error(`Failed to perform tap on session: ${sessionId}`, { error });
          return {
            content: [{
              type: 'text',
              text: `Error: ${error instanceof Error ? error.message : String(error)}`
            }],
            isError: true
          };
        }
      }
    );
  • Helper function in SimulatorManager that executes the actual tap gesture using the 'xcrun simctl io input tap' command on the target simulator UDID.
    async performTap(sessionId: string, x: number, y: number): Promise<boolean> {
      const session = this.sessions.get(sessionId);
      if (!session) {
        fileLogger.warn(`Session not found: ${sessionId}`);
        return false;
      }
    
      try {
        // Note: This is a simplified implementation
        // In a real-world scenario, you'd use more advanced methods from Appium
        await session.simulator.spawnProcess('xcrun', ['simctl', 'io', session.udid, 'input', 'tap', x.toString(), y.toString()]);
        fileLogger.info(`Tap performed at (${x}, ${y}) for session: ${sessionId}`);
        return true;
      } catch (error) {
        fileLogger.error(`Failed to perform tap 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