Skip to main content
Glama

Related Servers

Alternatives to axint

  • A
    license
    A
    quality
    C
    maintenance
    An MCP server providing curated Swift and SwiftUI best practices from leading iOS developers, including patterns and real-world code examples from Swift by Sundell, SwiftLee, and other trusted sources.
    4
    57 npm
    12
    MIT
  • F
    license
    A
    quality
    C
    maintenance
    Enables control of the iOS Simulator using the xcrun simctl command-line utility. It allows users to manage devices, install and launch apps, send push notifications, and simulate device features like GPS location.
    12
    -

Related Servers

  • A
    license
    A
    quality
    D
    maintenance
    Unified MCP server for Xcode + iOS Simulator — build, deploy, screenshot, and interact with your iOS app from Claude Code, Cursor, or any MCP client. Built in Swift. Single binary. No Node/Python runtime required.
    6
    9
    MIT
  • A
    license
    Not graded
    quality
    B
    maintenance
    Blitz-mcp gives AI agents full control over iOS/macOS development — boot simulators, interacts with physical iPhones, browse databases, trigger builds, and submit apps to App Store Connect via 30+ MCP tools.
    1,751
    Apache 2.0
  • A
    license
    Not graded
    quality
    F
    maintenance
    MCP server that provides semantic-level analysis of Swift codebases to AI agents by integrating with Apple's SourceKit-LSP, enabling compiler-grade code understanding and cross-file navigation.
    334 PyPI
    126
    Academic Free v1.1
  • 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.
    76 npm
    26
    MIT

TDQS

A4/5.0

Scored across 36 tools

Disambiguation4/5

Most tools have distinct purposes and clear descriptions, but some overlap exists between validation tools (axint.validate vs axint.swift.validate vs axint.cloud.check) and run-related tools (axint.run vs axint.run.status), which could cause minor confusion.

Naming Consistency5/5

All tool names follow a consistent dot-separated pattern with lowercase and underscore style, clearly indicating domain and action (e.g., axint.compile, axint.workflow.check). No mixing of conventions.

Tool Count3/5

36 tools is on the high side for an MCP server, covering many sub-domains. While each tool serves a specific purpose, the sheer number could overwhelm agents and users, making it borderline for appropriate scope.

Completeness4/5

The tool set covers the full lifecycle of Apple-native development with Axint: setup, compilation, validation, repair, templates, design tokens, and session management. Minor gaps like deployment are outside the stated purpose.

Maintenance

ActivityActive
ResponsivenessWithin a week