Skip to content
Back to search

Pepper

iOS dynamic library MCP for agents

Safety scan

A static text scan, not a guarantee. Select the badge to see what was scanned and every finding.

Checked today
Badge for your README
findsafeskills safety rating

Markdown

[![findsafeskills safety rating](/api/listings/skwallace36--pepper/badge.svg)](/listings/skwallace36--pepper)

HTML

<a href="/listings/skwallace36--pepper"><img src="/api/listings/skwallace36--pepper/badge.svg" alt="findsafeskills safety rating" /></a>

Install

i

Install instructions from the README

As written by the repo's author. findsafeskills has not verified these steps.

Requires macOS 14+, Python 3.10+, and an iOS Simulator runtime.

pip install pepper-ios
pepper-ctl deploy            # inject into the frontmost simulator app
pepper-ctl look              # see what's on screen

Then ask your agent:

> "Tap through the onboarding flow and make sure every screen looks right"

That's it. The agent uses Pepper's MCP tools to see, tap, and inspect — no extra config needed.

<details> <summary>Other MCP clients (Cursor, Claude Desktop, etc.)</summary>

{
  "mcpServers": {
    "pepper": {
      "command": "pepper-mcp"
    }
  }
}

</details>

<details> <summary>Homebrew</summary>

brew install --HEAD skwallace36/pepper/pepper

Tap: [`skwallace36/homebrew-pepper`](https://github.com/skwallace36/homebrew-pepper)

</details>

What was scanned

The files the safety scan read, as written by the repository's author and shown as plain text. Lines with a finding are marked.

README.md · README · 105 lines

View this file on GitHub (read at the repository's current version: the scan did not record which commit it read)

  1. # Pepper
  2. Pepper gives AI agents eyes and hands inside iOS Simulator apps.
  3. It injects a shared library into any running simulator app — no source changes, no SDK, no build step. Your agent sees the screen as structured data, taps buttons, inspects live objects, intercepts network calls, reads the heap, and debugs layout issues. Dylib injection requires the simulator; device support uses a different mechanism.
  4. https://github.com/user-attachments/assets/42ab3f1b-21f8-48e6-820f-7ca4012fb03b
  5. *Claude navigating and inspecting [Ice Cubes](https://github.com/Dimillian/IceCubesApp) (Mastodon client) with zero source access.*
  6. Works with Claude Code · Cursor · Claude Desktop · any [MCP](https://modelcontextprotocol.io) client
  7. ## Quickstart
  8. Requires macOS 14+, Python 3.10+, and an iOS Simulator runtime.
  9. ```bash
  10. pip install pepper-ios
  11. pepper-ctl deploy # inject into the frontmost simulator app
  12. pepper-ctl look # see what's on screen
  13. ```
  14. Then ask your agent:
  15. > "Tap through the onboarding flow and make sure every screen looks right"
  16. That's it. The agent uses Pepper's MCP tools to see, tap, and inspect — no extra config needed.
  17. <details>
  18. <summary>Other MCP clients (Cursor, Claude Desktop, etc.)</summary>
  19. ```json
  20. {
  21. "mcpServers": {
  22. "pepper": {
  23. "command": "pepper-mcp"
  24. }
  25. }
  26. }
  27. ```
  28. </details>
  29. <details>
  30. <summary>Homebrew</summary>
  31. ```bash
  32. brew install --HEAD skwallace36/pepper/pepper
  33. ```
  34. Tap: [`skwallace36/homebrew-pepper`](https://github.com/skwallace36/homebrew-pepper)
  35. </details>
  36. ## What It Does
  37. ```
  38. $ pepper-ctl look
  39. Screen: navigation_stack (9 interactive, 4 text)
  40. seg "Trending" → tap text:"Trending"
  41. btn "Sheryl Weikal, Right wing tech bros: we love St..."
  42. → tap text:"Sheryl Weikal, Right wing tech bros: we ..."
  43. seg "Settings" → tap text:"Settings"
  44. $ pepper-ctl tap --text "Settings"
  45. Action: Tapped Settings
  46. Screen: navigation_stack Title: "Settings" (15 interactive, 3 text)
  47. btn "App Icon" → tap text:"App Icon"
  48. btn "Display Settings" → tap text:"Display Settings"
  49. ...
  50. ```
  51. Every element comes with its tap command. The agent sees the screen, acts, and gets the new state back in one round trip.
  52. ### Things you can ask your agent
  53. These work against any app — no setup beyond `deploy`.
  54. > "Why is this list empty? Check the network request and see what the API returned"
  55. > "What objects are holding a reference to DeviceActuationService? I think it's leaking"
  56. > "Switch to dark mode and look for any text that's invisible against the background"
  57. > "The login button isn't responding — check the responder chain and see what's intercepting taps"
  58. > "Profile the scroll performance on the feed. Is anything hitching?"
  59. > "Read what's in the keychain after logout — nothing should be left"
  60. > "Turn off the feature flag for new-nav and make sure the old flow still works"
  61. View hierarchy, network interception, heap inspection, console capture, crash logs, performance profiling, accessibility audits, constraint debugging, keychain/UserDefaults/CoreData access, locale and orientation control, feature flags, push notifications — 60+ tools in total. Parameter docs are built into every tool; your MCP client surfaces them automatically.
  62. ## How It Works
  63. Pepper uses macOS's dynamic linker (`DYLD_INSERT_LIBRARIES`) to load a dylib into the simulator process at launch. The dylib starts a WebSocket server on a local port. `pepper-mcp` connects to that WebSocket and translates MCP tool calls into commands executed inside the app.
  64. Because it runs in-process, Pepper has access to the full view hierarchy, the ObjC runtime, live object graphs, network delegates, and the HID event system. All touch input goes through native input events (IOHIDEvent) — the same path real fingers take. No private APIs, no entitlements — just `dyld`.
  65. ## Development
  66. [`dylib/DYLIB.md`](dylib/DYLIB.md) — architecture and adding commands · [`tools/TOOLS.md`](tools/TOOLS.md) — MCP tool layer · [`docs/TROUBLESHOOTING.md`](docs/TROUBLESHOOTING.md) — common issues

Ratings and comments

Sign in to rate this skill.

Sign in

Free to use. If it’s helped, pass it on.