
Network monitor and debug toolkit streaming debug-build network traffic to a local companion, with searchable history, request mocking, breakpoints, replay, and AI-queryable insights.
See every request your mobile app makes — live, on your desktop, without a proxy.
App Monitor is a network monitor and debug toolkit for Android, iOS and Kotlin Multiplatform apps. A small SDK inside your debug build streams traffic to a desktop app (macOS, Linux, Windows) on the same network. The desktop keeps a searchable history, lets you mock, hold and replay requests, and answers your AI agent's questions about the traffic over a local MCP server.
[!IMPORTANT] For debug builds only. App Monitor captures every request and response, bodies included, and sends them over your local network. Release builds never carry it: on Android the Gradle plugin gives them no-op artifacts and fails a release build that would still hold the SDK; on iOS the Run Script fails an optimized build that links it.
flowchart LR
subgraph device["Device / emulator / simulator"]
app["Your app (debug)"]
ios["sdk-ios<br/>Swift"]
android["sdk-android<br/>OkHttp"]
ktor["sdk-ktor<br/>KMP"]
app --- ios & android & ktor
end
subgraph desktop["Desktop app — Compose Multiplatform"]
server["WebSocket server<br/>+ mDNS"]
db[("SQLite")]
ui["UI"]
mcp["MCP server<br/>127.0.0.1"]
server --> db --> ui
db --> mcp
end
ios & android & ktor -- "Protobuf over WebSocket" --> server
mcp --> agent["AI agent<br/>(Claude Code, …)"]_appmonitor._tcp).10.0.2.2 on the
Android emulator, 127.0.0.1 on the iOS simulator.Desktop packages are not published yet. Until they are, run it from the repository, with JDK 21:
git clone https://github.com/christianalexandre/app-monitor
cd app-monitor
make desktopMore in the desktop guide.
Apply the plugin in the app module. It adds the SDK to debug builds and
captures every OkHttpClient (Retrofit, Apollo, Ktor's OkHttp engine…):
// app/build.gradle.kts
plugins {
id("io.github.christianalexandre.appmonitor") version "0.1.0"
}Start it in Application.onCreate:
import appmonitor.sdk.core.AppMonitor
import appmonitor.sdk.core.AppMonitorOptions
AppMonitor.start(this, AppMonitorOptions(appName = "My App"))The plugin is on Maven Central: pluginManagement in settings.gradle.kts
must list mavenCentral(). New Android Studio projects already do. Details
and options are in the Android guide.
Add the package. File → Add Package Dependencies…,
https://github.com/christianalexandre/app-monitor, Up to Next Minor
Version from 0.1.0, product AppMonitor, to the app target.
Start it in App.init or application(_:didFinishLaunchingWithOptions:):
#if DEBUG
import AppMonitor
#endif
#if DEBUG
AppMonitor.start(AppMonitorOptions(appName: "My App"))
#endifExclude it from release builds. In the target's Build Settings, for
every configuration that ships (Release, …):
EXCLUDED_SOURCE_FILE_NAMES = AppMonitor*.
Paste the Run Script from the iOS guide as the target's last build phase. It adds the keys a physical iPhone needs and fails a build that would ship the SDK.
Every URLSession is captured, with no further code. gRPC Swift 2 and
troubleshooting are in the iOS guide.
Follow the Android steps and the iOS steps, nothing more: they capture Ktor's OkHttp engine on Android and its Darwin engine on iOS. With another engine (CIO, Java…), see the KMP guide.
Open the app and accept it in the desktop the first time it connects; the answer is remembered. Its traffic then streams in. The emulator and the simulator need nothing else.
[!TIP] On a physical device, the phone and the computer must be on the same Wi-Fi. Android 17+ and iOS ask once for local network access: allow it. From then on, the device keeps to that desktop. The rest is in Physical devices.
The desktop serves its history over MCP on 127.0.0.1. With Claude Code, open
the desktop's settings, MCP server, click Copy command and paste it in a
terminal. Then ask, for example, "why did checkout fail in the last run?".
Other clients and the list of tools are in the MCP guide.
App Monitor is the successor of app-network-monitor, an iOS-only tool built to replace netfox in a large retail app.
MIT.
See every request your mobile app makes — live, on your desktop, without a proxy.
App Monitor is a network monitor and debug toolkit for Android, iOS and Kotlin Multiplatform apps. A small SDK inside your debug build streams traffic to a desktop app (macOS, Linux, Windows) on the same network. The desktop keeps a searchable history, lets you mock, hold and replay requests, and answers your AI agent's questions about the traffic over a local MCP server.
[!IMPORTANT] For debug builds only. App Monitor captures every request and response, bodies included, and sends them over your local network. Release builds never carry it: on Android the Gradle plugin gives them no-op artifacts and fails a release build that would still hold the SDK; on iOS the Run Script fails an optimized build that links it.
flowchart LR
subgraph device["Device / emulator / simulator"]
app["Your app (debug)"]
ios["sdk-ios<br/>Swift"]
android["sdk-android<br/>OkHttp"]
ktor["sdk-ktor<br/>KMP"]
app --- ios & android & ktor
end
subgraph desktop["Desktop app — Compose Multiplatform"]
server["WebSocket server<br/>+ mDNS"]
db[("SQLite")]
ui["UI"]
mcp["MCP server<br/>127.0.0.1"]
server --> db --> ui
db --> mcp
end
ios & android & ktor -- "Protobuf over WebSocket" --> server
mcp --> agent["AI agent<br/>(Claude Code, …)"]_appmonitor._tcp).10.0.2.2 on the
Android emulator, 127.0.0.1 on the iOS simulator.Desktop packages are not published yet. Until they are, run it from the repository, with JDK 21:
git clone https://github.com/christianalexandre/app-monitor
cd app-monitor
make desktopMore in the desktop guide.
Apply the plugin in the app module. It adds the SDK to debug builds and
captures every OkHttpClient (Retrofit, Apollo, Ktor's OkHttp engine…):
// app/build.gradle.kts
plugins {
id("io.github.christianalexandre.appmonitor") version "0.1.0"
}Start it in Application.onCreate:
import appmonitor.sdk.core.AppMonitor
import appmonitor.sdk.core.AppMonitorOptions
AppMonitor.start(this, AppMonitorOptions(appName = "My App"))The plugin is on Maven Central: pluginManagement in settings.gradle.kts
must list mavenCentral(). New Android Studio projects already do. Details
and options are in the Android guide.
Add the package. File → Add Package Dependencies…,
https://github.com/christianalexandre/app-monitor, Up to Next Minor
Version from 0.1.0, product AppMonitor, to the app target.
Start it in App.init or application(_:didFinishLaunchingWithOptions:):
#if DEBUG
import AppMonitor
#endif
#if DEBUG
AppMonitor.start(AppMonitorOptions(appName: "My App"))
#endifExclude it from release builds. In the target's Build Settings, for
every configuration that ships (Release, …):
EXCLUDED_SOURCE_FILE_NAMES = AppMonitor*.
Paste the Run Script from the iOS guide as the target's last build phase. It adds the keys a physical iPhone needs and fails a build that would ship the SDK.
Every URLSession is captured, with no further code. gRPC Swift 2 and
troubleshooting are in the iOS guide.
Follow the Android steps and the iOS steps, nothing more: they capture Ktor's OkHttp engine on Android and its Darwin engine on iOS. With another engine (CIO, Java…), see the KMP guide.
Open the app and accept it in the desktop the first time it connects; the answer is remembered. Its traffic then streams in. The emulator and the simulator need nothing else.
[!TIP] On a physical device, the phone and the computer must be on the same Wi-Fi. Android 17+ and iOS ask once for local network access: allow it. From then on, the device keeps to that desktop. The rest is in Physical devices.
The desktop serves its history over MCP on 127.0.0.1. With Claude Code, open
the desktop's settings, MCP server, click Copy command and paste it in a
terminal. Then ask, for example, "why did checkout fail in the last run?".
Other clients and the list of tools are in the MCP guide.
App Monitor is the successor of app-network-monitor, an iOS-only tool built to replace netfox in a large retail app.
MIT.