Skip to main content
Glama
kevinswint

Xcode-Studio-MCP

by kevinswint
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Local

Related Servers

Alternatives to Xcode-Studio-MCP

No user-submitted related servers found.

    Related Servers

    • SilbercueSwift by Silbercue

      SilbercueSwiftofficial

      Silbercue
      A
      license
      Not graded
      quality
      B
      maintenance
      High-performance MCP server for iOS development and test automation. Gives AI coding assistants direct access to iOS simulators with sub-20ms screenshots, UI interaction, building, testing, and an intelligent operator mode.
      8
      MIT

    • XCAutokit

      Ezra-Black
      A
      license
      Not graded
      quality
      B
      maintenance
      First-party MCP server and CLI for Xcode and iOS Simulator automation. Enables control of Xcode and iOS Simulator via MCP tools for tasks like building, testing, and automation.
      8 npm
      1
      MIT

    • mcp-baepsae

      oozoofrog
      A
      license
      Not graded
      quality
      C
      maintenance
      Local MCP server for iOS Simulator and macOS app automation with a TypeScript MCP layer and Swift native bridge. Enables UI inspection, input automation, and simulator control through unified generic tools.
      41 npm
      26
      MIT

    • ios-sim-mcp

      artmamedov
      A
      license
      Not graded
      quality
      D
      maintenance
      A Model Context Protocol (MCP) server for iOS Simulator automation. Enables AI assistants to visually interact with iOS apps running in the simulator.
      22 npm
      1
      MIT
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    A3.7/5.0

    Scored across 6 tools

    Disambiguation5/5

    Each tool targets a distinct action: building, running, and simulator interactions (screenshot, tap, type, describe) are clearly separated. There is no overlap in purpose, making it easy for an agent to select the correct tool.

    Naming Consistency3/5

    Tools are grouped into two clear namespaces: 'xcode_' for build/run and 'simulator_' for simulator interactions. However, the same verb 'run' is used for xcode_run (launch app) while the simulator tools use direct action verbs (tap, type, describe). The pattern is readable but not perfectly uniform.

    Tool Count5/5

    With only 6 tools, the set is well-scoped for core Xcode build/run and simulator interaction workflows. Each tool serves a distinct purpose, and no tool feels redundant or missing at this scale.

    Completeness4/5

    The set covers building, running, and basic UI interaction (via describe/tap/type). A minor gap is the lack of a tool to terminate the running app, and no way to list available simulators, but agents can work around this for common tasks.

    Maintenance

    ActivityInactive
    ResponsivenessUnresponsive

    Resources