{
"mcpServers": {
"xcodebridge": {
"command": "<see-readme>",
"args": []
}
}
}No install config available. Check the server's README for setup instructions.
Are you the author?
Add this badge to your README to show your security score and help users find safe servers.
A multiplexer and bridge for the Xcode MCP server
Is it safe?
No package registry to scan.
No authentication — any process on your machine can connect.
MIT. View license →
Is it maintained?
Last commit 61 days ago. 2 stars.
Will it work with my client?
Transport: stdio. Works with Claude Desktop, Cursor, Claude Code, and most MCP clients.
No automated test available for this server. Check the GitHub README for setup instructions.
No known vulnerabilities.
This server is missing a description. Tools and install config are also missing.If you've used it, help the community.
Add informationHave you used this server?
Share your experience — it helps other developers decide.
Sign in to write a review.
XcodeBuildMCP provides tools for Xcode project management, simulator management, and app utilities.
An open-source AI agent that brings the power of Gemini directly into your terminal.
The full-stack TypeScript framework to build, test, and deploy production-ready MCP servers and AI-native apps.
Open-source persistent memory for AI agent pipelines (LangGraph, CrewAI, AutoGen) and Claude. REST API + knowledge graph + autonomous consolidation.
MCP Security Weekly
Get CVE alerts and security updates for XcodeBridge and similar servers.
Start a conversation
Ask a question, share a tip, or report an issue.
Sign in to join the discussion.
XcodeBridge is a macOS menu bar app plus a CLI (xcbridge) that sits in front of Xcode's MCP bridge (xcrun mcpbridge).
This project exists to work around the repeated Xcode permission popups for MCP connections.
In practice, Xcode can prompt for approval per connecting process. That becomes a blocker for tools like the Codex app, which may spawn many codex CLI processes during one session. MCP access can stall until each process is approved.
XcodeBridge keeps one long-running bridge process connected to Xcode MCP, then lets other local clients connect through that bridge.
It provides:
XcodeBridge/XcodeBridge: SwiftUI menu bar appXcodeBridge/xcbridge: CLI sourceXcodeBridge/XcodeBridge.xcodeproj: Xcode projectXcodeBridge/XcodeBridge.xcodeproj.XcodeBridge scheme.From the menu bar extra:
Start Bridge / Stop BridgeCopy MCP Command (copies embedded xcbridge binary path)Open Log WindowUse Copy MCP Command each time after a rebuild, since the app-bundle path can change with DerivedData.
Build the CLI scheme:
xcodebuild -project XcodeBridge/XcodeBridge.xcodeproj -scheme xcbridge -configuration Debug build
The executable is xcbridge. It supports two modes:
serve: starts the local socket server and launches xcrun mcpbridge as backendconnect: bridges current stdin/stdout to the local socketExamples:
# Start server on default socket: ~/.xcode-bridge.sock
xcbridge serve
# Connect stdin/stdout to running bridge
xcbridge connect
# Use a custom socket
xcbridge serve --socket ~/tmp/xcode-bridge.sock
xcbridge connect --socket ~/tmp/xcode-bridge.sock
XCODE_BRIDGE_SOCKET: override socket pathUse the path copied by Copy MCP Command, and point your MCP client command to connect (not xcrun mcpbridge directly):
{
"command": "/path/to/XcodeBridge.app/Contents/Resources/xcbridge",
"args": ["connect"]
}
If your client expects a socket command, use the same connect mode and let xcbridge handle transport details.
Open Log Window shows live events, including:
client_in / client_outserver_in / server_outThe bridge emits MUXLOG events on stderr, which the app parses and renders in the log UI.