About this integration
Python wrapper that makes Xcode's MCP bridge compatible with strict MCP clients like Cursor
- Transport
- stdio
- Authentication
- none
- Initial setup
- user-authorization
- Runtime
- unattended
- Evidence
- documented
- Version
- 0.1.6
- Package
- mcpbridge-wrapper
- Last compatibility test
- Not independently tested
Connect your agent
mcpbridge-wrapperPublisher README and manifest reviewed from pinned captures. Package and integration endpoints were not executed or independently security-audited. The local wrapper requires explicit operator approval for brokered connection requests.
Capabilities: Xcode MCP bridge brokering, connection approval flow, stdio bridge operation
Connected profiles
Additional details
io.github.SoundBlaster/mcpbridge-wrapper
Source ↗ · Checked 2026-09-170.1.6
Source ↗ · Checked 2026-09-17CC0-1.0; package licenses are separate
Source ↗ · Checked 2026-09-17pypi
Source ↗ · Checked 2026-09-17mcpbridge-wrapper
Source ↗ · Checked 2026-09-180.4.5
Source ↗ · Checked 2026-09-18Publisher documentation specifies: claude mcp add --transport stdio xcode -- uvx --from mcpbridge-wrapper mcpbridge-wrapper --broker
Source ↗ · Checked 2026-09-18Publisher documentation specifies: - **Why this mode exists:** Apple documents a Coding Intelligence known issue in Xcode 26.4 where external development tools may trigger repeated "Allow Connection?" dialogs during normal usage (`170721057`). Reusing one long-lived upstream session via broker mode can reduce reconnect churn that surfaces this prompt pattern. See Apple's official [Xcode 26.4 release notes](https://developer.apple.com/documentation/xcode-release-notes/xcode-26_4-release-notes).
Source ↗ · Checked 2026-09-18Publisher documentation specifies: claude mcp add --transport stdio xcode -- uvx --from mcpbridge-wrapper mcpbridge-wrapper --broker
Source ↗ · Checked 2026-09-18Publisher documentation reviewed; package and integration endpoint not executed or independently security-audited.
Source ↗ · Checked 2026-09-18