Two ways to connect
A stdio client can spawn the process, or you point it at an HTTP endpoint. Either works.
Let AI capture for you; you just give the orders.
"Capture this app for me, find the failed requests, replay them." Say it to your AI agent and it does the whole thing for you inside Trace Eagle.
MCP is an open protocol that lets AI agents call external tools. Trace Eagle ships a real MCP server: it can start a capture on any path (NIC, system-level, app injection, browser launch, mobile device or remote), enumerate devices and processes to target, then inspect flows, decode bytes, craft and replay requests, and run the network toolbox. Over 40 capabilities, exposed as tools an agent uses directly, without you clicking through each step.
Local, same permissions
Runs on loopback and honors the app’s own access rules. Convenience for your AI, not a backdoor.
Drives the whole capture, end to end
From starting a capture (NIC, system, app, launch, mobile or remote) through reading flows to replay, codegen and diagnostics: the tools you use by hand are open to your agent.
Tools your AI can call directly
Start a capture
start_nic_capturestart_system_capturestart_app_capturestart_launch_capturestart_mobile_capturestart_remote_capturelist_deviceslist_appsProxy & session control
proxy_startset_rulesset_interceptresume_breakpointadd_key_sourceset_block_http3list_sessionsstop_captureInspect & craft
list_flowsget_flowdecode_bytessend_requestreplay_flowgenerate_codeopenapi_from_flowsNetwork toolbox
dns_lookuptls_auditip_intelweb_fingerprintdns_leak_testlist_connectionsnet_pingnet_diagnose