Skip to main content
Glama
devyhan

Xcode MCP Server

by devyhan
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

Related Servers

Alternatives to Xcode MCP Server

No user-submitted related servers found.

    Related Servers

    • Xcode MCP Server

      PolarVista
      A
      license
      B
      quality
      F
      maintenance
      A Model Context Protocol server that enables AI assistants to build and test Xcode projects directly through a standardized interface, with capabilities for running tests, monitoring progress, and accessing logs in real-time.
      18
      146 npm
      53
      MIT

    • MCP Xcode Server

      chacebot
      A
      license
      Not graded
      quality
      D
      maintenance
      An MCP server that provides tools for programmatically interacting with Xcode projects, enabling users to manage targets, schemes, and files. It supports essential development tasks including building, testing, and cleaning projects through the Xcode command-line tools.
      107 npm
      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

    • simctl-mcp

      ambar
      A
      license
      B
      quality
      D
      maintenance
      A Model Context Protocol server implementation for iOS Simulator control, providing tools for device management, app operations, permissions, system features, and certificate handling.
      29
      7 npm
      20
      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

    D1.8/5.0

    Scored across 9 tools

    Disambiguation4/5

    Most tools have clearly distinct purposes targeting different Xcode workflows (building, testing, archiving, etc.), though 'simctl-manager' and 'run-on-device' could potentially overlap in device-related operations. The lack of descriptions makes it harder to fully assess boundaries, but the naming suggests reasonable separation.

    Naming Consistency3/5

    There's a mixed naming convention: most tools use a consistent 'xcode-' prefix with snake_case (e.g., 'xcode-build'), but 'simctl-manager', 'swift-package-manager', and 'run-on-device' deviate from this pattern. This inconsistency reduces predictability, though the names remain generally readable.

    Tool Count5/5

    With 9 tools, the count is well-scoped for an Xcode development server, covering key operations like building, testing, and project management. Each tool appears to serve a distinct function, avoiding both bloat and thin coverage for the domain.

    Completeness3/5

    The tools cover core development workflows (build, test, archive, etc.) but lack descriptions make it hard to assess gaps fully. Based on naming, there might be missing operations like code editing, debugging, or version control integration, which are common in Xcode environments, suggesting moderate incompleteness.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources