Add Network Logs tools to dart_mcp_server

[davidmigloz]

The Dart MCP server doesn’t currently expose network logs from the connected app, which makes it hard for agents to debug network traffic. It'd be great to have a network.* tool family that enables/reads network traffic, similar to the Network View tool.

Use cases

• Agent debugging of network failures: Let AI agents diagnose “why did this request fail?” without switching contexts.
• Reproducible bug reports: Export a sharable HAR.
• Performance analysis: Let AI agents measure latency, payload sizes, and headers over time to spot regressions or bottlenecks.
• etc.

Proposed tools

• network.start_capture: Enable HTTP timeline logging.
• network.get_logs: Fetch recent HTTP requests with filters and (optionally) bodies.
  • since
  • limit
  • filters: { urlContains, method, statusMin, statusMax, failedOnly }
  • includeBodies (default: false)
• network.dump_har: Return a HAR snapshot for easy sharing/analysis.
• network.clear: Clear profiler buffers.
• network.stop_capture: Disable HTTP timeline logging.

Inspiration

• Chrome Tools MCP
• AgentDesk BrowserTools MCP

Open questions

• How to make these tools seamlessly work in non-web (Dart VM service) and web (Chrome DevTools) apps?

[jakemac53]

Note that we should be able to use the devtools network page as an example of how to capture these requests.

We may want to consider just making a single tool, with separate sub-commands, similar to how flutter driver is set up. This generally scales better for the LLMs than a large number of top level tools, in theory at least.

[jakemac53]

Specifically see https://pub.dev/documentation/vm_service/latest/vm_service/DartIOExtension.html for the dart:io related vm service functionality.