agentleFS
joshuayoesjoshuayoes/ios-simulator-mcp/CLAUDE.md

ios-simulator-mcp

CLAUDE.md2.2k starsChanged 10 months agoMITView on GitHub

This is the iOS Simulator MCP (Model Context Protocol) server - a tool that enables AI assistants to interact with iOS simulators through MCP. The project follows an intentionally simple single-file architecture where all logic is contained in src/index.ts. npm is the default; pnpm is also supported (a pnpm-lock.yaml, derived from package-lock.json via pnpm import, is committed). Substitute pnpm for npm in any command below. The entire server implementation is in src/index.ts (single file by design). The server: - Uses…

  • Installs packages

We split this CLAUDE.md into the rules it gives an agent

2 rules. About 0 are common, 1 is distinctive, and 1 is very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈1

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 1

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Real use cases only: Don't add hypothetical features

    line 76
  2. Very specific:

    Security first: Always use -- separator for user inputs, validate with Zod

    line 77

≈ “Common” is an estimate: at least 1 in 5 of the 25,680 CLAUDE.md files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
CLAUDE.md

CLAUDE.md

This file provides guidance to Claude Code (claude.ai/code) when working with code in this repository.

Project Overview

This is the iOS Simulator MCP (Model Context Protocol) server - a tool that enables AI assistants to interact with iOS simulators through MCP. The project follows an intentionally simple single-file architecture where all logic is contained in src/index.ts.

Build and Development Commands

npm is the default; pnpm is also supported (a pnpm-lock.yaml, derived from package-lock.json via pnpm import, is committed). Substitute pnpm for npm in any command below.

# Install dependencies
npm install

# Build the TypeScript project (compiles to build/)
npm run build

# Development with automatic rebuild on changes
npm run watch

# Run the MCP inspector for testing
npm run dev

# Start the compiled server
npm start

Architecture

The entire server implementation is in src/index.ts (single file by design). The server:

  • Uses the MCP SDK to expose tools for iOS simulator interaction
  • Wraps xcrun simctl and Facebook's idb commands
  • Validates all inputs with Zod schemas
  • Implements security best practices with -- argument separation
  • Supports environment-based tool filtering via IOS_SIMULATOR_MCP_FILTERED_TOOLS
  • Handles output paths with IOS_SIMULATOR_MCP_DEFAULT_OUTPUT_DIR environment variable

Available MCP Tools

The server provides these tools (can be filtered via environment variables):

  • get_booted_sim_id - Get the currently booted simulator ID
  • open_simulator - Open the iOS Simulator application
  • ui_describe_all - Get accessibility info for the entire screen
  • ui_tap - Tap at coordinates
  • ui_type - Input text
  • ui_swipe - Swipe gesture
  • ui_describe_point - Get element at specific coordinates
  • ui_find_element - Search accessibility tree for elements by label, identifier, or type
  • ui_view - Get compressed screenshot as base64 JPEG
  • screenshot - Save screenshot to file
  • record_video - Start video recording
  • stop_recording - Stop video recording
  • install_app - Install an app bundle (.app or .ipa) on the simulator
  • launch_app - Launch an app by bundle identifier
  • terminate_app - Terminate a running app by bundle identifier
  • open_url - Open a URL or deep link in the simulator
  • list_apps - List all installed apps with their bundle IDs and display names

Testing

This project requires manual testing on macOS with:

  • Xcode and iOS simulators installed
  • Facebook IDB tool installed
  • An MCP client (like Cursor) configured to use the server

Test changes by:

  1. Building with npm run build
  2. Configuring your MCP client to point to build/index.js
  3. Running through the test cases in QA.md

Important Design Principles

  • Keep it simple: Single file, minimal dependencies, standard tooling (npm/tsc)
  • Real use cases only: Don't add hypothetical features
  • Security first: Always use -- separator for user inputs, validate with Zod
  • No architecture changes without discussion - the single-file design is intentional

Additional Documentation

For more detailed information, refer to these documentation files:

  • README.md - Complete project documentation including installation instructions, available tools, configuration options, and usage examples
  • CONTRIBUTING.md - Contribution guidelines, development setup, dependency management, and the project's philosophy of intentional simplicity
  • QA.md - Manual quality assurance test cases for validating functionality
  • TROUBLESHOOTING.md - Common issues and their solutions, including IDB installation help
  • SECURITY.md - Security policy and information about fixed vulnerabilities
  • CONTEXT.md - Reference links for MCP documentation, iOS simulator commands, IDB commands, and security best practices

Download now (ZIP)

Trending

Quiet since June.thin dataabout the whole repository

Dec 2025: 0 mentionsJan 2026: 0 mentionsFeb 2026: 2 mentionsMar 2026: 1 mentionApr 2026: 1 mentionMay 2026: 0 mentionsJun 2026: 1 mentionJul 2026: 0 mentionsAug 2026: 0 mentionsSep 2026: 0 mentionsOct 2026: 0 mentionsNov 2026: 0 mentions
Dec 2025Jun 2026Nov 2026
Mentions a month of the joshuayoes/ios-simulator-mcp repository that our weekly crawl found: only 10 in all, so this is a hint, not a trend. There is no adoption data for this file yet.

Who's talking about joshuayoes/ios-simulator-mcp

The biggest 5 of 10 mentions linking to the repository that our crawl found. Each line is their own headline.

See all 10

Talked about on GitHub, Bluesky and Hacker News (10 times).

On GitHub · 6

1 more on GitHub

On Hacker News · 1

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.