Xcode: MCP Bridge Wrapper For Cursor
Run Xcode’s MCP bridge from strict MCP clients like Cursor by adding a Python stdio wrapper that normalizes protocol behavior.
Overview
mcpbridge-wrapper is a MCP server for the Build phase that makes Xcode’s MCP bridge work with strict MCP clients such as Cursor via a Python stdio wrapper.
What is this MCP server?
- Python mcpbridge-wrapper via uvx (--from mcpbridge-wrapper)
- Adapts Xcode MCP bridge for strict clients including Cursor
- stdio MCP transport from PyPI package
- Registry version 0.1.6
- Published from SoundBlaster/XcodeMCPWrapper on GitHub
- stdio transport via PyPI identifier mcpbridge-wrapper
- uvx runtime hint with --from mcpbridge-wrapper
Community signal: 18 GitHub stars.
What problem does it solve?
Xcode’s MCP bridge often fails to connect in picky MCP clients, so your agent cannot drive Apple toolchain actions from Cursor.
Who is it for?
Solo mobile developers using Cursor (or similar) who need Xcode MCP integration without patching clients manually.
Skip if: Pure web or backend builders with no Xcode install, or teams already using a client that accepts the raw Xcode bridge.
What do I get? / Deliverables
After uvx registration, strict clients can speak MCP to the wrapper and reach Xcode bridge capabilities more reliably.
- Working stdio MCP path from your agent client toward Xcode bridge tools
- Reduced connection failures when invoking Xcode-backed MCP actions
Recommended MCP Servers
Journey fit
How it compares
Protocol compatibility shim MCP, not a Swift codegen skill or App Store launch checklist.
Common Questions / FAQ
Who is mcpbridge-wrapper for?
Indie iOS/macOS builders on MCP agents—especially Cursor—who need Xcode bridge tools to register and respond correctly.
When should I use mcpbridge-wrapper?
Use it during Build when configuring agent-tooling and the native Xcode MCP bridge errors or disconnects under your strict MCP client.
How do I add mcpbridge-wrapper to my agent?
Install with uvx using --from mcpbridge-wrapper, add the stdio server block to your MCP config, and ensure Xcode and the upstream bridge are available locally.