Skip to main content
Glama
getsentry

XcodeBuildMCP

by getsentry
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Related Servers

Alternatives to XcodeBuildMCP

No user-submitted related servers found.

    Related Servers

    • Xcode MCP Server

      devyhan
      A
      license
      D
      quality
      D
      maintenance
      A Model Context Protocol server that provides tools for Xcode-related operations, making it easier to work with iOS project management, building, testing, archiving, and deploying apps to both simulators and physical devices.
      9
      19 npm
      9
      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

    • xcode-mcp

      onmyway133
      A
      license
      Not graded
      quality
      D
      maintenance
      MCP server for interacting with Xcode build tools, iOS Simulator, and Apple notarization services.
      1 npm
      5
      MIT

    • ProwlKit MCP

      ProwlLabs
      A
      license
      Not graded
      quality
      A
      maintenance
      An advanced Model Context Protocol (MCP) server for Xcode project introspection. It enables AI assistants to read schemes, build iOS/macOS projects, run tests, and check Git & SwiftLint info directly from local repositories
      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

    B3.2/5.0

    Scored across 83 tools

    Disambiguation2/5

    The tool set has significant overlap and ambiguity, particularly in build and test operations where multiple tools differ only by target (project vs. workspace) or identifier type (UUID vs. name). For example, there are 4 variants each for building, getting app paths, and testing on simulators, making it easy for an agent to misselect. While descriptions clarify parameters, the sheer number of similar tools creates confusion.

    Naming Consistency4/5

    Tool names follow a consistent snake_case pattern with a clear verb_noun structure (e.g., build_dev_proj, list_sims, describe_ui). However, there are minor deviations like 'button' (noun only) and 'doctor' (no verb), and some names are overly verbose due to parameter distinctions (e.g., build_run_sim_name_ws). Overall, the naming is predictable but not perfectly uniform.

    Tool Count2/5

    With 83 tools, the count is excessive for the Xcode build and testing domain. Many tools are redundant variations (e.g., separate tools for project vs. workspace, UUID vs. name), leading to bloat. A more streamlined set with parameterized options would be more appropriate, as the current size overwhelms and complicates agent decision-making.

    Completeness5/5

    The tool set comprehensively covers Xcode development workflows, including building, testing, simulator management, UI automation, logging, and Swift package operations. It supports CRUD-like actions (e.g., create projects via scaffold, run/stop apps) across multiple platforms (iOS, macOS) with no obvious gaps, enabling end-to-end automation without dead ends.

    Maintenance

    ActivityActive
    ResponsivenessWithin a week

    Resources