carter-mcp
Related Servers
Alternatives to carter-mcp
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityBmaintenanceTouchBridge is a local-first MCP server for iOS simulators and physical devices, enabling AI to see, control, test, and redesign iPhone screens through a structured screenshot bridge and tool surface.5MIT
- AlicenseNot gradedqualityCmaintenanceEnables compatible AI apps to observe and control a locally connected iPhone through stdio MCP tools for screenshots, taps, swipes, long presses, text entry, key and button presses, app listing, and app launching, all reusing the console's device session.GPL 3.0
- AlicenseNot gradedqualityBmaintenanceEnables AI coding tools to connect and authorize local game projects, then drive source edits, validation, preview, version saving, and mode-based creation workflows.Apache 2.0
- AlicenseAqualityDmaintenanceTurns AI coding hosts into a guided mobile-UI design tool with design interviews, token contracts, linters, and local browser preview.86 npmMIT
- AlicenseAqualityBmaintenanceEnables AI agents to drive a running Roblox Studio in real time over a single WebSocket, executing whole Luau programs, installing in-engine controllers, hot-patching scripts during live playtests, and receiving errors, assertions and other events as pushes. It also reaches Roblox Open Cloud for the open place and answers visual questions via a vision sidecar, exposing all of this through nine MCP tools.91MIT
- AlicenseBqualityDmaintenanceEnables AI assistants to control iOS simulators through WebDriverAgent, supporting taps, swipes, typing, screenshots, recording, and app actions with a real-time dashboard for visual feedback.36Apache 2.0
TDQS
Scored across 57 tools
Many tools have overlapping purposes, e.g., multiple ways to add controls (add_control, insert_example, customize_on_phone) and multiple push/save layout functions (push_buffer, push_layout, save_buffer, save_layout). The descriptions help but the high number of similar tools makes it confusing for an agent to select the correct one.
Most tools follow a consistent snake_case verb_noun pattern (e.g., add_control, remove_control, update_control, push_buffer). Minor deviations exist, such as 'autotune_gauge' and 'customize_on_phone', but the overall pattern is predictable and clear.
With 57 tools, the server has an excessive number for its domain (a layout editor for a device). Many tools could be consolidated (e.g., multiple push/save functions, multiple validation/linting tools). This overpopulation adds unnecessary complexity.
The tool set covers the full lifecycle: layout creation and editing (add, remove, move, update controls), device connection, data probing, validation, generation (adapter, service, theme), testing (simulate, run_scenario), and chat interaction. There are no obvious gaps for the intended purpose.