Description
Proxyman's GUI already exposes the client/device associated with each captured flow and allows filtering by client. It would be great if the MCP server could expose the same information.
A possible implementation could be:
- Add a
client (or clientName) filter to filter_flows
- Include the client/device information in
get_flows
- Include the same field in
get_flow_detail
This would keep the MCP API consistent with the existing GUI functionality.
Why this feature/change is important?
When using Proxyman as a shared proxy for multiple devices, MCP queries currently return flows from every connected client. Since client information isn't exposed, there's no reliable way to scope requests to a single device.
Being able to filter by client would make MCP integrations much more practical for automated testing, AI assistants, and other tooling that needs to analyze traffic from one specific device or session.
Description
Proxyman's GUI already exposes the client/device associated with each captured flow and allows filtering by client. It would be great if the MCP server could expose the same information.
A possible implementation could be:
client(orclientName) filter tofilter_flowsget_flowsget_flow_detailThis would keep the MCP API consistent with the existing GUI functionality.
Why this feature/change is important?
When using Proxyman as a shared proxy for multiple devices, MCP queries currently return flows from every connected client. Since client information isn't exposed, there's no reliable way to scope requests to a single device.
Being able to filter by client would make MCP integrations much more practical for automated testing, AI assistants, and other tooling that needs to analyze traffic from one specific device or session.