axint
Related Servers
Alternatives to axint
- AlicenseAqualityCmaintenanceAn 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.457 npm12MIT
- FlicenseAqualityCmaintenanceEnables 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-
- AlicenseNot gradedqualityCmaintenanceAI-native SwiftUI component library with full-stack recipes — connect via MCP for instant access.3,222MIT
Related Servers
- AlicenseAqualityDmaintenanceUnified 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.69MIT

blitz-mcpofficial
AlicenseNot gradedqualityBmaintenanceBlitz-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,751Apache 2.0- AlicenseNot gradedqualityAmaintenanceApp Store Connect MCP server — lets AI agents manage iOS releases, TestFlight builds, screenshots, and review submissions directly from App Store Connect.44 npmMIT
- AlicenseNot gradedqualityDmaintenanceMCP server and CLI for iOS development — build, test, automate, and diagnose from any AI agent or terminal.1MIT
- AlicenseNot gradedqualityFmaintenanceMCP 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 PyPI126Academic Free v1.1
- AlicenseNot gradedqualityCmaintenanceLocal 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 npm26MIT
TDQS
Scored across 36 tools
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.
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.
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.
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.