XcodeMCPWrapper

MCP.Pizza Chef: SoundBlaster

This server bridges Xcode 26.3's MCP tools to work smoothly with strict MCP clients like Cursor. It fixes a compatibility issue by adding required response fields that Xcode omits, enabling your AI assistant in Cursor or similar apps to interact with Xcode's development tools. Setup requires a Mac with Xcode 26.3+, Python 3.9+, and enabling Xcode's Tools MCP server. It supports advanced features like broker mode for sharing sessions and a web UI for monitoring.

Coding
Other

Use This MCP server To

Make Xcode 26.3 MCP tools compatible with Cursor Run Xcode MCP tools in strict MCP clients without errors Enable multi-client MCP sessions with broker mode Monitor MCP server status via a web dashboard Reduce Xcode connection prompts during development Share one MCP bridge session across multiple editors

README

XcodeMCPWrapper - mcpbridge-wrapper

Version

Python 3.9+ License: MIT Coverage

MCP Registry

A Python wrapper that makes Xcode 26.3's MCP bridge compatible with Cursor and other strict MCP-spec-compliant clients.

The Problem

Xcode's mcpbridge returns tool responses in the content field but omits the required structuredContent field when a tool declares an outputSchema. According to the MCP specification, when outputSchema is declared, responses must include structuredContent.

  • ✅ Claude Code and Codex CLI work (they have special handling for Apple's responses)
  • ❌ Cursor strictly follows the spec and rejects non-compliant responses

The Solution

mcpbridge-wrapper intercepts responses from xcrun mcpbridge and copies the data from content into structuredContent, making Xcode's MCP tools fully compatible with all MCP clients.

┌─────────────┐    MCP Protocol    ┌──────────────────┐   MCP Protocol   ┌────────────┐    XPC    ┌─────────┐
│   Cursor    │ ◄────────────────► │ mcpbridge-wrapper│ ◄──────────────► │ mcpbridge  │ ◄───────► │  Xcode  │
│ (MCP Client)│                    │  (This Project)  │                  │  (Bridge)  │           │  (IDE)  │
└─────────────┘                    └──────────────────┘                  └────────────┘           └─────────┘

XcodeMCPWrapper FAQ

Can I use this to make Xcode 26.3 MCP tools work with Cursor?
Yes — it fixes compatibility so Cursor can use Xcode MCP tools without errors.
Does this require an API key or account?
No — it runs locally on your Mac and connects directly to Xcode's MCP tools.
What apps does this work with?
It is designed for Cursor and other MCP clients that strictly follow the MCP spec.
How hard is it to set up?
It requires developer-level setup on macOS with Xcode 26.3+, including enabling Xcode Tools MCP and running a Python wrapper.
Can I use this with other MCP clients besides Cursor?
Yes — any strict MCP-spec-compliant client can work with this wrapper.
What do I need to run this?
A Mac with Xcode 26.3 or later, Python 3.9+, and the Xcode Tools MCP Server enabled.