Conorluddy Xclaude Plugin
conorluddy-xclaude-plugin is a Claude Code plugin for the Build phase that exposes modular Xcode and IDB MCP servers tuned for iOS workflows and lighter context use.
by conorluddy · github.com/conorluddy/xclaude-plugin
Give Claude Code modular Xcode and IDB MCP access for iOS simulator work without loading every Apple tool into context at once.
Add it to Claude Code
Install the plugin in Claude Code. One command, paste-ready.
/plugin install conorluddy-xclaude-plugin@conorluddy/xclaude-pluginBuilt to be called by your agent
Skillselion is itself an MCP server. Your agent can pull this entry and a paste-ready install config straight from the API - no copy-paste.
Retrieve this entry with skillselion.get_details("plugin:conorluddy/xclaude-plugin") and the paste-ready config with skillselion.get_install_config("plugin:conorluddy/xclaude-plugin").
What it does
conorluddy-xclaude-plugin is a Claude Code plugin for solo builders shipping iOS apps who want agent help without drowning sessions in every Xcode and IDB command at once. It packages modular MCP servers that align with common mobile workflows—build, simulator, testing, and accessibility—so you turn on the integration slice that matches what you are doing right now. That workflow-specific grouping is the main value: fewer irrelevant tools in context, more predictable token use, and clearer handoffs when Claude needs to act on a real project in Xcode. It fits indie and small-team iOS work where you already use Claude Code on macOS and want first-class bridge tooling instead of ad-hoc shell scripts. It is not a replacement for Apple documentation or CI; it is the agent-facing control plane for local iOS iteration.
Highlights
- Modular MCP servers grouped by iOS workflow so you enable only the tool set you need
- Xcode and IDB-oriented tools for simulator control, builds, and device-side automation
- Designed for mindful token and context usage when driving large Apple tool surfaces
- Supports accessibility and UI testing flows across the simulator suite
- Single-plugin bundle focused on Claude Code + iOS development
Why builders use it
Driving Xcode and IDB from Claude Code often wastes context and tokens when every Apple tool is exposed at once.
After install, you enable workflow-scoped MCP modules so the agent can run the right simulator, build, and test actions with a smaller, clearer tool surface.
At a glance
- Type - Plugin in Development Tools.
- Adoption - 0 installs, 128 stars, 0 votes.
FAQ
Who is conorluddy-xclaude-plugin for?
It is for indie and small-team iOS builders who use Claude Code on Mac and want MCP bridges to Xcode and IDB without loading the entire tool catalog every session.
When should I use conorluddy-xclaude-plugin?
Use it during active iOS build and test work—simulator runs, accessibility checks, and workflow-specific automation—when you want the agent to call Apple tooling through scoped MCP servers.
How do I add conorluddy-xclaude-plugin to my agent?
Install the plugin from the conorluddy/xclaude-plugin repository into Claude Code, configure the MCP modules for your current workflow, and ensure Xcode and IDB prerequisites are available on your Mac.
Comments
Share how you use conorluddy-xclaude-plugin, gotchas, or tips for other indie builders.
No comments yet - be the first to share how you use it.