A side-by-side look at the Magic MCP and Xcode Studio MCP MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Magic MCP for developer tools work as a local process; choose Xcode Studio MCP for developer tools. You can also run both side by side in one mcpServers block.
TWENTY_FIRST_API_KEY, API_KEY_21ST.xcode_build, xcode_run, simulator_screenshot.Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Developer Tools | Developer Tools |
| Quality signal | 53/100 · Good | 45/100 · Fair |
| Install command | Confirmed | Not confirmed yet |
| Transport | Local subprocess (stdio) | — |
| Auth | API key required | No auth required |
| Pricing | Paid service | Free |
| Required env vars | TWENTY_FIRST_API_KEYAPI_KEY_21ST | None listed |
| Verified owner | Community listing | Community listing |
| GitHub stars | 5,997 | 9 |
| Directory activity | 16 views 1 installs 0 upvotes | 3 views 0 installs 0 upvotes |
| Tools | Not listed | 6 |
| Full listing | View Magic MCP | View Xcode Studio MCP |
No tool names declared yet. Check the project README from the listing page.
xcode_buildBuild an Xcode project with structured error output (file, line, column, severity, message)xcode_runBuild and launch an app in the iOS Simulatorsimulator_screenshotCapture the Simulator screen as a PNG imagesimulator_tapTap at x,y coordinates on the Simulator screensimulator_typeType text into the currently focused fieldsimulator_describeGet the accessibility tree of the current screen (JSON)Paste either block (or both) into your client config, e.g. claude_desktop_config.json or ~/.cursor/mcp.json. We only show a config when the install command is confirmed.
{
"mcpServers": {
"21st-dev-magic-mcp": {
"command": "npx",
"args": [
"-y",
"@21st-dev/cli@latest"
],
"env": {
"TWENTY_FIRST_API_KEY": "YOUR_TWENTY_FIRST_API_KEY_HERE",
"API_KEY_21ST": "YOUR_API_KEY_21ST_HERE"
}
}
}
}
No confirmed install command for Xcode Studio MCP yet — follow the setup steps linked from its listing page rather than a guessed package name.