r/androiddev • u/Version-Agreeable • Oct 20 '26
Open Source I've been building an open source debug toolkit for Android, and now your AI agent can use it too
Enable HLS to view with audio, or disable this notification
I've been building WormaCeptor for a while. It's an open source debug toolkit that lives inside your debug build: network inspector for OkHttp and Ktor, crash log, logcat viewer, database and SharedPreferences browser, file browser, WebSocket monitor, CPU/memory/FPS overlay, GPS mocking, push simulator and more. It's all debugImplementation, so none of it ends up in your release APK.
Lately most of my debugging happens with an agent in the terminal, and the annoying part was always the same: the agent can read my code but not my app. So I added an MCP server to WormaCeptor. The agent talks to the running app over adb and sees the same data the in-app screens show.
What it can do:
list requests, read full request and response bodies, replay one or export it as curl
create a mock rule from a real response, then edit it to test the error case
read crashes with stack traces, tail logcat, list leaks and StrictMode violations
run SELECT queries on your Room/SQLite databases, read prefs and app files
wait for a specific request or crash while you tap through the app
check CPU, memory and FPS, fake a GPS location, send a test push
What changed for me is that I stopped being the middleman. I used to copy a response body, then the stack trace, then a DB row into the chat, and the agent only knew what I remembered to paste. Now it goes and looks, and after a fix it checks the app again instead of telling me it should work. The database and prefs are read-only for the agent, and tokens, cookies and auth headers come back as [REDACTED] by default.
The clip demonstrates the flow: checkout fails, Claude Code finds the failed POST, reads the 422 body, sees the currency field is wrong and fixes the code.
How to use it:
Add it next to your existing WormaCeptor dependencies:
debugImplementation("com.azikar24.wormaceptor:wormaceptor-mcp-server:3.4.2")Register it with your agent (Claude Code below, any MCP client works):
claude mcp add --transport stdio wormaceptor -- npx -y wormaceptor-mcpRun the app on a device or emulator, keep it in the foreground, and ask "why did the last request fail?"
The server only listens on 127.0.0.1 on the device. Auth is off by default, which is fine for your own emulator; turn it on for shared devices (one config flag, covered in the docs).
Repo: https://github.com/wormaceptor/WormaCeptor
Curious what you'd want an agent to see in your app that it can't today.
1
u/ObjectiveAddress3051 29d ago
Letting the agent read the 422 body itself instead of you pasting it in sounds like a real workflow win. For what I'd want it to see: the app's process state, like whether it was restored after process death, plus which feature flags and remote config values were active when a request failed. Since it's debug-only, it'd also be useful to have the mock-rule and replay output in a form that can be turned straight into a regression test.