A
licenseNot graded
qualityC
maintenanceToken-efficient MCP reimplementation with progressive tool discovery, result handling, and compact wire encoding, reducing token usage by up to 89% on tool definitions.
1
MIT
XC-MCP: XCode CLI wrapper
by conorluddy
Related Servers
Alternatives to XC-MCP: XCode CLI wrapper
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityFmaintenanceToken-efficient GitLab MCP server that delivers 167 tools through 3 meta-tools with progressive disclosure, field projection, server-side file trimming, and keyset pagination for agent context budgets.116 npm3MIT
- AlicenseNot gradedqualityDmaintenanceUniversal MCP server for executing TypeScript and Python code with progressive disclosure, reducing token usage by 98% by enabling on-demand access to all other MCP tools through code execution rather than loading tool definitions directly.15 npm130MIT
- AlicenseNot gradedqualityBmaintenanceEnables clients of tool-heavy MCP aggregators to find and use upstream tools on demand through four fixed bridge tools (search, describe, call, refresh), cutting per-turn tool context from ~180k tokens to ~2–3k. It merges multiple upstream servers behind sticky sessions and a local lexical BM25 index, so only the schemas actually needed are retrieved.6MIT
- AlicenseNot gradedqualityAmaintenanceA proxy server that wraps existing MCP servers to significantly reduce token consumption by compressing tool descriptions into a two-step interface. It enables users to integrate extensive toolsets without exceeding context limits or incurring high API costs.128Apache 2.0
- AlicenseNot gradedqualityNot gradedmaintenanceA drop-in MCP proxy that aggregates multiple backend servers into two meta-tools for efficient tool discovery and execution. It enables AI clients to access hundreds of tools while minimizing context window usage through searchable indexing.1 npm-
TDQS
A3.7/5.0
Scored across 77 tools
Disambiguation2/5
Family prefixes (xcodebuild-, simctl-, idb-) help, but the set contains several overlapping groups: simctl-launch/install/terminate mirror idb-launch/install/terminate, workflow-build-and-run overlaps workflow-fresh-install, and simctl-io overlaps screenshot for capture duties. Boundaries between simctl-get-app-container vs simctl-container and idb-ui-describe vs idb-ui-find-element vs accessibility-quality-check also blur, so agents must read deep documentation to avoid misselection.
Naming Consistency3/5
Most tools follow a readable {prefix}-{verb}-{object} pattern with consistent family prefixes like simctl-boot, cache-get-stats, and persistence-enable. However, there are notable exceptions: standalone names (screenshot, rtfm), noun-only resources (idb-targets), operation-parameter objects (simctl-status-bar), and inconsistent ordering (xcode-model-inspect, workflow-tap-element, localization-audit). The conventions are mixed but still broadly predictable.
Tool Count2/5
At 77 tools, this is far beyond the well-scoped range and imposes a heavy selection overhead on agents; the mirrored simctl/idb surfaces and multiple composite workflow tools inflate the count unnecessarily. The genuinely broad Xcode/simulator/idb domain justifies a larger-than-average surface, which keeps it from being a total mismatch, but it remains excessive.
Completeness4/5
The surface covers the full test-automation lifecycle—build, clean, test, simulator lifecycle, app install/launch, UI automation, screenshots, logs, crash analysis, permissions, keychain, appearance, location, and push—plus useful extras like localization audit, visual diff, and hang detection. Notable gaps remain: no xcodebuild archive/export for distribution, no signing or provisioning profile management, and no build-settings query.
Maintenance
ActivityMaintained
ResponsivenessResponsive