Inspect a running Android debug app: network traffic, crashes, logs, databases and preferences
MCP Server: com.wormaceptor/wormaceptor
This MCP server inspects a running Android debug app. It focuses on examining runtime artifacts including network traffic, crashes, logs, databases, and preferences, based on the server description.
🛠️ Key Features
Inspects network traffic from a running Android debug app
Captures and reviews crash information
Retrieves and inspects logs
Examines databases accessed by the app
Reads and inspects app preferences
🚀 Use Cases
Debugging Android applications by reviewing runtime network activity
Investigating crashes and associated log output
Auditing or validating local data stored in databases
Checking persisted configuration in app preferences
⚡ Developer Benefits
Centralizes access to debug-time signals (traffic, crashes, logs, databases, preferences) for a running app
Supports iterative inspection during Android debugging workflows
⚠️ Limitations
Described scope is limited to a running Android debug app and the listed data types.
Your AI agent can read your code. Now it can read your running Android app.
WormaCeptor puts network traffic, crashes, logs, databases and preferences one tool call away for Claude Code, Cursor and other MCP clients, and on screen for you. No proxy, no certificates. Ships only in debug builds through Gradle's debugImplementation, so nothing reaches production. Set up the agent in two lines.
Demo
An agent finds and fixes a failing checkout by reading the app's network traffic through WormaCeptor:
An AI agent calls WormaCeptor, reads the 422 response body, and fixes the currency field
Network inspection, system tools, and performance monitoring side by side:
You can also enable the shake gesture with WormaCeptorApi.startActivityOnShake(activity). Using Ktor? See the Ktor guide.
Features
Network: Intercept HTTP/HTTPS via OkHttp or Ktor, monitor WebSocket connections and WebView requests, copy URLs or export as cURL, JSON and HAR, throttle with the rate limiter, and mock responses with Mock Rules (turn any captured request into a mock with Add to Mock)
Performance: Track FPS, memory, and CPU in real time with a live overlay, catch memory leaks and StrictMode thread violations, spot excessive Compose recompositions
System: Browse SQLite databases, edit SharedPreferences, inspect DataStore and encrypted storage, explore files, view loaded native libraries and Gradle dependencies, read device info and logcat, capture crash reports
Testing: Fire test push notifications, manage FCM tokens, mock GPS locations, encrypt/decrypt and hash with the crypto tool
AI agents: An optional MCP server lets Claude Code, Cursor, and other MCP clients query the running debug app: 44 tools for transactions, crashes, logs, performance, storage, mock rules, request replay, and actions. See AI Agents (MCP)
Every feature is its own module. Enable exactly what you need at init time, disable the rest. See Feature Toggles.
How It Works
Your release APK never sees debug code. Here's why:
wormaceptor-client ships in all build types. It contains only interfaces and a reflection-based lookup, no debug logic.
wormaceptor-persistence (or wormaceptor-imdb) ships only in debug via debugImplementation. It registers itself through classpath discovery.
In release builds, no implementation exists on the classpath. wormaceptor-client falls back to a no-op automatically. No ProGuard rules, no runtime checks, no dead code.
Register the bridge with your client (needs Node.js 18+, Java 17+ and adb; the launcher downloads the matching bridge jar and checks its SHA-256):
bash
claude mcp add --transport stdio wormaceptor -- npx -y wormaceptor-mcp@3.5.0
No Node? Download wormaceptor-mcp-bridge.jar from the latest release and run it with java -jar.
The server listens on an abstract Unix socket that only adb, root and the app itself can connect to, and the bridge reaches it through adb forward. Bearer-token auth is available and off by default; read Security before using it on a shared device. Setup, all 44 tools, and configuration: docs/MCP.md. Walkthrough: docs/MCP_TUTORIAL.md.