Xcode: MCP Bridge Wrapper for Cursor — Cursor MCP server
A Python proxy linking strict MCP clients like Cursor to Apple's xcrun mcpbridge. It repairs malformed responses and pools editor connections via a shared broker.
claude mcp add mcpbridge-wrapper -- uvx mcpbridge-wrapperWhat Xcode: MCP Bridge Wrapper for Cursor does
Apple provides xcrun mcpbridge to let external coding assistants communicate with Xcode. However, some Xcode responses specify an outputSchema while dropping the required structuredContent field. Strict MCP clients fail. This wrapper intercepts the traffic and patches payloads so clients process them without crashes.
The tool works in direct mode or as a shared broker daemon. Running with --broker lets multiple editors talk to Xcode through one persistent background process. This avoids repeated permission popups across editor reboots. It exposes whatever tools your local Xcode installation provides, including 54 tools detected in Xcode 27.0.
Prerequisites include macOS, Xcode 26.3 or 27.0, and uv. You must turn on external agent access inside Xcode settings before connecting. Note that a green connection dot in your editor only proves the handshake succeeded. Tool calls will still fail until you confirm the permission prompt inside Xcode.
What it helps with
- Connect Cursor and Claude Code to Apple's native
xcrun mcpbridge - Fix schema parsing crashes caused by missing
structuredContentfields - Share a single Xcode session across editors to cut down permission popups
- Trigger Xcode builds and test runs directly from an AI chat
Example prompts for the agent
- Inspect
/Users/dev/Workspace/App.xcworkspaceand list the available build targets. - Run all unit tests in the current scheme and report any build failures.
- Read the localization keys from
Localizable.xcstringsusing Xcode tools.
How to install Xcode: MCP Bridge Wrapper for Cursor
Platform CLI
claude mcp add mcpbridge-wrapper -- uvx mcpbridge-wrapperuvx runs the command named after the package; if the README names another one, use uvx --from mcpbridge-wrapper <command>
Platform CLI
codex mcp add xcode-mcp-bridge-wrapper-for-cursor -- uvx mcpbridge-wrapperuvx runs the command named after the package; if the README names another one, use uvx --from mcpbridge-wrapper <command>
Config file
{
"mcpServers": {
"xcode-mcp-bridge-wrapper-for-cursor": {
"command": "uvx",
"args": [
"mcpbridge-wrapper"
]
}
}
}uvx runs the command named after the package; if the README names another one, use uvx --from mcpbridge-wrapper <command>
Config file
{
"servers": {
"xcode-mcp-bridge-wrapper-for-cursor": {
"type": "stdio",
"command": "uvx",
"args": [
"mcpbridge-wrapper"
]
}
}
}uvx runs the command named after the package; if the README names another one, use uvx --from mcpbridge-wrapper <command>
Platform CLI
gemini mcp add xcode-mcp-bridge-wrapper-for-cursor uvx mcpbridge-wrapperuvx runs the command named after the package; if the README names another one, use uvx --from mcpbridge-wrapper <command>
Step by step, with commands for each platform: How to add an MCP server to Claude Code, Codex, Cursor, VS Code, Gemini CLI and more
Questions about Xcode: MCP Bridge Wrapper for Cursor
How do I install Xcode: MCP Bridge Wrapper for Cursor in Claude Code?
Run claude mcp add mcpbridge-wrapper -- uvx mcpbridge-wrapper in your terminal. You can also name the server explicitly using claude mcp add xcode-mcp-bridge-wrapper-for-cursor -- uvx mcpbridge-wrapper.
What problem does this wrapper solve?
Xcode's native bridge returns responses that trigger protocol errors in strict clients like Cursor. The wrapper adjusts these messages to fit the expected MCP specification and provides a broker daemon for multiple editors.
Why do tool calls fail even when the MCP status indicator is green?
A green indicator simply signals an active MCP handshake. Xcode requires separate user approval for the broker Python process before granting access to files or project actions.
