An MCP server that gives AI assistants X-ray vision into HTTP traffic captured by powhttp.
Most browser automation work still happens through a UI a human drives. Powhttp MCP MCP server moves it into the conversation instead. An MCP server that gives AI assistants X-ray vision into HTTP traffic captured by powhttp.
The server publishes 14 tools. What each one is for:
powhttp_sessions_list — List all sessions with entry countspowhttp_session_active — Get the currently active sessionpowhttp_search_entries — Search entries with filters and free textpowhttp_get_entry — Get full details of a specific entrypowhttp_get_tls — Get TLS handshake events for a connectionpowhttp_get_http2_stream — Get HTTP/2 frame details for a streampowhttp_fingerprint — Generate HTTP, TLS, and HTTP/2 fingerprintspowhttp_diff_entries — Compare two entries to find detection differencespowhttp_extract_endpoints — Cluster entries into endpoint groupspowhttp_describe_endpoint — Generate detailed endpoint descriptionpowhttp_trace_flow — Trace related requests around a seed entrypowhttp_validate_schema — Validate entry bodies against a schemaConfiguration is passed through the environment: POWHTTP_BASE_URL, POWHTTP_PROXY_URL. Treat anything key-shaped as a real credential — scope it to the minimum the server needs, and rotate it if it ever lands in a shared config.
Setup follows the usual MCP pattern — install or clone the server, register it in your client's configuration file, restart the client. The configuration blocks on this page cover the common clients.
Plenty of browser automation servers cover similar ground. The differences that matter in practice are scope of access and how much setup stands between you and a working tool call. Powhttp MCP's toolset — powhttp_sessions_list, powhttp_session_active, powhttp_search_entries and 11 more — is a fair guide to whether it matches your workflow. It is maintained by usestring; worth a glance at recent repository activity before you build anything load-bearing on it.
SyncDev reviews every entry in this directory against the project's own documentation before publishing, and revisits them as servers change.
| Tool | What it does |
|---|---|
| powhttp_sessions_list | List all sessions with entry counts |
| powhttp_session_active | Get the currently active session |
| powhttp_search_entries | Search entries with filters and free text |
| powhttp_get_entry | Get full details of a specific entry |
| powhttp_get_tls | Get TLS handshake events for a connection |
| powhttp_get_http2_stream | Get HTTP/2 frame details for a stream |
| powhttp_fingerprint | Generate HTTP, TLS, and HTTP/2 fingerprints |
| powhttp_diff_entries | Compare two entries to find detection differences |
| powhttp_extract_endpoints | Cluster entries into endpoint groups |
| powhttp_describe_endpoint | Generate detailed endpoint description |
| powhttp_trace_flow | Trace related requests around a seed entry |
| powhttp_validate_schema | Validate entry bodies against a schema |
| powhttp_query_body | Extract specific fields from bodies using JQ expressions |
| powhttp_infer_schema | Infer merged schema from multiple entry bodies with field statistics |
{
"mcpServers": {
"powhttp": {
"command": "powhttp-mcp",
"env": {
"POWHTTP_BASE_URL": "http://localhost:7777",
"POWHTTP_PROXY_URL": "http://localhost:8888"
}
}
}
}Configuration as documented by the project. Restart the client after saving.
| Variable | Description | Required |
|---|---|---|
| POWHTTP_BASE_URL | Endpoint or connection string the server talks to. | Yes |
| POWHTTP_PROXY_URL | Endpoint or connection string the server talks to. | Yes |
Microsoft's official browser automation server — drive a real browser through the accessibility tree, no screenshots needed.
Industrial-strength web extraction — render, scrape, crawl and search entire sites into clean markdown.
The original Chromium automation reference server — simple, screenshot-driven browser control.
Give your coding agent the full DevTools toolbox: traces, network, console, heap snapshots and Lighthouse.
Puppeteer-powered browser control that drives pages from the accessibility tree instead of pixels.
Cloud browsers for AI agents — automation sessions that run in Browserbase's fleet, not on your machine.