Xcode Index MCP
Related Servers
Alternatives to Xcode Index MCP
No user-submitted related servers found.
Related Servers
- FlicenseNot gradedqualityCmaintenanceBridges Xcode and Cursor to provide real-time access to build errors, warnings, and debug output from Xcode's DerivedData, enabling automated error analysis and fixes directly within Cursor.-
- AlicenseNot gradedqualityBmaintenanceIndexes a codebase into a live symbol graph and serves it via MCP to AI coding tools for context-aware code queries.9 npm1MIT
- AlicenseAqualityCmaintenanceEnable Claude Code, Cursor, or your favorite LLM to interact with Xcode, building your projects the same way you do, and seeing the same errors. Greatly increases productivity when working on iOS, iPadOS, macOS, visionOS, tvOS projects & Swift packages - or any time you might use Xcode.29441 PyPI5MIT
- FlicenseNot gradedqualityAmaintenanceProvides a local-first code indexing and search engine for coding agents via MCP, enabling precise codebase queries, symbol lookup, and freshness-aware retrieval.-
- AlicenseNot gradedqualityAmaintenanceAn 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 repositoriesMIT
- FlicenseAqualityCmaintenanceIndexes a workspace and exposes code-navigation tools to Codex, enabling symbol lookup, reference finding, dependency analysis, and security audit for local codebases.10-
TDQS
Scored across 4 tools
The tools have distinct primary purposes: loading an index, searching by pattern, retrieving by USR, and looking up by file location. However, get_occurrences and symbol_occurrences could be slightly confused as both retrieve symbol occurrences, though they use different input parameters (USR vs. file location).
All tool names follow a consistent snake_case verb_noun pattern (e.g., load_index, search_pattern, get_occurrences, symbol_occurrences). The naming is predictable and readable throughout the set.
With 4 tools, the count is reasonable for an index query server, covering core operations like loading, searching, and retrieving symbols. It might be slightly thin if advanced features like filtering or batch operations are needed, but it's well-scoped for basic functionality.
The tools cover key index operations: loading, pattern search, and symbol retrieval by USR or location. However, there are notable gaps, such as no ability to update or delete index data, list available projects, or handle errors more granularly, which could limit agent workflows in complex scenarios.