conorluddy/xclaude-plugin

COLLECTIONcommunity
conorluddyMITUpdated 8mo agoGitHub

iOS development ClaudeCode plugin for mindful token and context usage. Contains modular MCPs that group various Xcode/IDB tools based on your current workflow.

Modular iOS development automation for Claude Code Build, test, and automate iOS apps through natural conversation with Claude. 8 workflow-specific MCP servers with 24 tools across Xcode, Simulator, and IDB. Enable only what you need. Each MCP is purpose-built for specific workflows, keeping your context window lean. Plus, our tools intelligently encapsulate Xcode output (errors, test results,…

This collection bundles
8 skills277 MCP servers

⚠ The trust score below reflects the collection's repository only. The bundled units are not individually verified or scanned — review them before use.

Automatically indexed from public sources. Not yet verified by the developer on Forge.Claim this listing →
170GitHub stars
16Forks
8mo agoLast update
Package
Authorconorluddy
LicenseMIT
Sourcegithub
GitHubconorluddy/xclaude-plugin
SBOMCycloneDX 1.6 ↓
Trust Status
B
60/100Good
✓Listed in Forge index+10/10
—Publisher identity verified+0/30
→ Publisher: run `forge publish` from the repo to claim ownership
—Domain verification+0/10
→ Not currently available for this listing type — the domain-verification check only runs for npm-backed packages today, so this row cannot be earned here yet regardless of what's hosted at the domain.
✓Prompt-injection scan · clean+30/30
✓Obfuscation / exfil scan · clean+20/20
Paste into Claude Code, Cursor, or any AI assistant to fix all gaps
StatusCommunity-indexed
PublisherUnverified
SignatureUnsigned
Domain—
Provenance—
DependenciesNot audited
Tool surface24 tools · 1 privileged
Security scan✓ CleanvHEAD · 3mo agoHow well does this scan work?
EvalsNone
IndexedJun 14, 2026

Verification confirms publisher identity (repo ownership), not code safety. The security scan covers known CVEs and suspicious install scripts.

Tools

24 tools · 1 privileged
Statically extracted from the published packagevHEAD · 3mo ago

Read out of the source npm actually ships, at scan time. The package was never executed. Tools registered dynamically at runtime, or hidden inside bundled or minified code, can be missed — so this is a floor on the tool surface, not a complete census of it.

idb_check_qualityNo description published

This tool published no description. Forge does not invent one.

idb_describeNo description published

This tool published no description. Forge does not invent one.

idb_find_elementNo description published

This tool published no description. Forge does not invent one.

idb_gestureNo description published

This tool published no description. Forge does not invent one.

idb_inputNo description published

This tool published no description. Forge does not invent one.

idb_tapNo description published

This tool published no description. Forge does not invent one.

simulator_bootNo description published

This tool published no description. Forge does not invent one.

simulator_createNo description published

This tool published no description. Forge does not invent one.

simulator_deleteprivilegedNo description published

This tool published no description. Forge does not invent one.

simulator_get_app_containerNo description published

This tool published no description. Forge does not invent one.

simulator_health_checkNo description published

This tool published no description. Forge does not invent one.

simulator_install_appNo description published

This tool published no description. Forge does not invent one.

simulator_launch_appNo description published

This tool published no description. Forge does not invent one.

simulator_listNo description published

This tool published no description. Forge does not invent one.

simulator_openurlNo description published

This tool published no description. Forge does not invent one.

simulator_screenshotNo description published

This tool published no description. Forge does not invent one.

simulator_shutdownNo description published

This tool published no description. Forge does not invent one.

simulator_terminate_appNo description published

This tool published no description. Forge does not invent one.

xcode_buildNo description published

This tool published no description. Forge does not invent one.

xcode_cleanNo description published

This tool published no description. Forge does not invent one.

xcode_listNo description published

This tool published no description. Forge does not invent one.

xcode_testNo description published

This tool published no description. Forge does not invent one.

xcode_versionNo description published

This tool published no description. Forge does not invent one.

xcode_build_and_launchNo description published

This tool published no description. Forge does not invent one.

0 of 24 tools published a description.

Tool names and descriptions are written by the publisher and shown verbatim as inert text. They are the strings an MCP client passes to a model, so Forge scans them for prompt-injection patterns — any finding appears with the security scan above. “Privileged” is a keyword match on the tool name, not an audit of what the tool does: a benign-sounding name can still do anything.

About

Modular iOS development automation for Claude Code Build, test, and automate iOS apps through natural conversation with Claude. 8 workflow-specific MCP servers with 24 tools across Xcode, Simulator, and IDB. Enable only what you need. Each MCP is purpose-built for specific workflows, keeping your context window lean. Plus, our tools intelligently encapsulate Xcode output (errors, test results, build logs) so Claude processes structured JSON instead of raw 50+ line logs—saving significant tokens…

Keywords
agenticagentic-workflowclaudeclaude-codeclaude-code-pluginclaude-mcpclaude-pluginsclaudecodecontext-engineeringdeveloper-toolsiosllmmcpmcp-serverpluginswifttoolingxcodexcodebuildcollection
Alternatives
Comparing tool surfaces…

Tools exposed

24 tools · 1 privileged · observed by static extraction. A tool surface is what one scan read on one day, not a live capability list.

Linked names open Forge’s index of every entry observed exposing that tool. Browse all indexed tools.

No dependency coverage

This entry publishes no npm package, so Forge has no dependency tree for it. That is a gap in coverage — not a statement that it has no dependencies.