Skills and helpers for driving the Inspector MCP bridge from Claude Code.
- v2.7 (2026-04-18) — Adds
refresh_handle+subtree. Handles become refreshable for exploration, and app-owned subtrees can be fetched in one call. Additive, no breaking changes. - v2.6 (2026-04-18) — Adds
save_scenario/list_scenarios/delete_scenario/diff_scenario. Named semantic baselines for broken-state debugging and regression comparison. Additive, no breaking changes. - v2.5 (2026-04-18) — Adds
list_actions+perform_action. Generic semantic action discovery/invocation over Inspector's existing action model. Additive, no breaking changes. - v2.4 (2026-04-18) — Adds
list_properties+set_property. Typed property mutation reusing Inspector property handlers. Additive, no breaking changes. - v2.3 (2026-04-18) — Adds
taptool. Semantic activation for exact-handle, button-likeUIControls. Additive, no breaking changes. - v2.1 (2026-04-17) — Adds
inspecttool. Open the Inspector UI focused on a handle. Additive, no breaking changes. - v2 (2026-04-17) — snapshot returns
pngPath(disk file) instead ofpngBase64. Requires restarting MCP clients after upgrading Inspector. Seedocs/superpowers/specs/2026-04-17-snapshot-disk-path-design.md. - v1 — initial release.
inspector-mcpskill — registerInspectorMCPServerfor a consumer Xcode project, then usequery/resolve/refresh_handle/subtree/snapshot/inspect/tap/list_actions/perform_action/list_properties/set_property/capture_state/diff_states/save_scenario/list_scenarios/delete_scenario/diff_scenarioon the live UIKit hierarchy. Includesscripts/find_inspector_package.pyto locate the Inspector Swift package under DerivedData.inspector-mcp-consumerskill — patch a consumer iOS app so it exposes the bridge: pick the right lifecycle entry point, setenableMCPBridge = truewithsnapshotExpiration = 300/snapshotMaxCount = 8beforeInspector.start().inspector-implementationskill — work on the Inspector library itself: runtime behavior, panels, libraries, macros, Example-app dogfooding, and verification.inspector-integrationskill — integrate Inspector the library into a consumer app even when MCP is not the main goal: startup wiring, configuration, customization, and debug-only registration patterns.templates/— drop-in shell wrapper and Codex MCP config for consumer apps. Seetemplates/README.md.
Both skills reference ${CLAUDE_PLUGIN_ROOT} so paths stay portable across machines.
From the Claude Code prompt:
/install-local-plugin /Users/pedro/Developer/Inspector/Plugins/inspector-mcp
That symlinks this directory into the Claude Code plugin cache so skill auto-discovery picks it up. Restart the Claude Code session after installing.
Claude Code activates each skill by description match. Typical triggers:
- "set up Inspector MCP for this app" →
inspector-mcp-consumer - "inspect the live hierarchy of the Simulator app" →
inspector-mcp
This plugin ships skills plus templates, not the MCP server itself. Registration stays per-app since it needs an Xcode project, scheme, and bundle id. Options:
- In the Inspector repo (dogfooding): the project-local
.mcp.jsonalready points atTools/mcp/run-inspector-mcp.sh. - In another consumer app: follow step 4 of the
inspector-mcpskill, or copytemplates/run-inspector-mcp-template.shinto the consumer and register a per-app wrapper.
Plugins/inspector-mcp/
├── plugin.json
├── README.md
├── skills/
│ ├── inspector-mcp/
│ │ ├── SKILL.md
│ │ ├── references/
│ │ │ ├── consumer-app-setup.md
│ │ │ └── inspection-patterns.md
│ │ └── scripts/
│ │ └── find_inspector_package.py
│ ├── inspector-implementation/
│ │ ├── SKILL.md
│ │ └── references/
│ │ └── architecture.md
│ ├── inspector-integration/
│ │ ├── SKILL.md
│ │ └── references/
│ │ └── integration-patterns.md
│ └── inspector-mcp-consumer/
│ ├── SKILL.md
│ └── references/
│ ├── entry-points.md
│ └── verification.md
└── templates/
├── README.md
├── codex-inspector-mcp.json
└── run-inspector-mcp-template.sh
