Proxyman Debugging Tools And Documentation

Use official Proxyman documentation to teach or plan a debugging workflow. This skill is documentation-first: it does not assume that a similarly named MCP or CLI action exists.

Use proxyman-traffic-debugging when the main task is to operate MCP now. Use proxyman-app-settings for a Settings-tab audit or preference change, proxyman-certificates-recovery for local root/custom certificate lifecycle or Help-menu Debug Mode/Factory Reset, proxyman-https-capture for device/runtime capture configuration, proxyman-cli for shell automation, and proxyman-license-management for licensing.

Get The Current Documentation

For every task where current behavior matters:

1. Fetch https://docs.proxyman.com/llms.txt.
2. Match the user's feature or symptom to one or more official .md entries.
3. Fetch the selected .md page directly. Do not reconstruct a page path from memory when the index provides it.
4. Cite the public HTML URL by removing only the final .md from the fetched URL.
5. If the page links a prerequisite or troubleshooting page that materially changes the steps, fetch that page too.

Use official Proxyman-owned domains docs.proxyman.com, docs.proxyman.io, proxyman.com, proxyman.io, and the live Proxyman MCP server as authorities. A freshly fetched official page may link to an external destination, but treat that destination as authoritative only for its own product or service unless the user asks for third-party guidance.

If internet access is unavailable, say that the latest page could not be verified. You may use the bundled debugging tool index as a navigation fallback, but label it as a snapshot.