powhttp

powhttp-mcp is an MCP server that exposes a suite of tooling for analyzing HTTP traffic captured by powhttp. Once running, clients can connect to the MCP server using the mcp.json configuration or Claude/CLI integrations described in the README, and leverage tools to list sessions, inspect individual HTTP entries, generate fingerprints, cluster endpoints, and build scrapers from captured traffic. The server relies on POWHTTP_BASE_URL to reach the powhttp API and POWHTTP_PROXY_URL for proxy-enabled workflows, allowing you to compare browser vs program traffic, inspect TLS/JA3 fingerprints, and create API maps from real traffic. The included prompts guide workflows for base usage, API discovery, and scraper generation, making it straightforward to explore captured data and extract reusable artifacts such as PoC scrapers or GraphQL operation catalogs.

Prerequisites:

• Go installed (1.20+ is recommended) to build powhttp-mcp from source if a prebuilt binary is not available.
• Access to a running powhttp instance and its Data API as described in the README.

Installation steps (via Go):

1. Install the MCP server binary:

go install github.com/usestring/powhttp-mcp/cmd/powhttp-mcp@latest

2. Verify the binary is on your PATH:

powhttp-mcp --version

3. Run the MCP server with the required environment variables. Example (in a shell):

POWHTTP_BASE_URL=http://localhost:7777 \
POWHTTP_PROXY_URL=http://localhost:8888 \
LOG_LEVEL=info \
LOG_FILE="" \
powhttp-mcp

4. Optionally pin a specific version by replacing latest with a tag, e.g. v1.x.y:

go install github.com/usestring/powhttp-mcp/cmd/powhttp-mcp@v1.0.0

If you prefer a containerized deployment, build a container image with the binary and run it with the same environment variables mapped into the container.

Tips and notes:

• Ensure POWHTTP_BASE_URL points to the running powhttp Data API and POWHTTP_PROXY_URL is reachable by prompts that generate scrapers or debug workflows.
• The MCP server reads configuration from environment variables; you can override LOG_LEVEL and LOG_FILE to control logging output.
• If you see command not found: powhttp-mcp, ensure your PATH includes the directory where the binary was installed (commonly $GOPATH/bin or $HOME/go/bin).
• When integrating with Claude Desktop/Code, supply the same POWHTTP_BASE_URL and POWHTTP_PROXY_URL values in your mcp configuration to enable seamless data flow.
• If you update powhttp-mcp or powhttp, re-validate that the base URL and proxy URL remain accessible from your MCP host to avoid connectivity issues.
• Security: restrict access to the MCP endpoint in production and avoid exposing POWHTTP_BASE_URL/PROXY_URL to untrusted networks.