Are you the author? Sign in to claim
MCP server exposing mitmproxy + mitmproxy2swagger for REST API reverse-engineering from HTTP captures.
MCP server for REST API reverse engineering from HTTP traffic captures. Wraps mitmproxy for live capture and mitmproxy2swagger for spec derivation.
| Tool | What it does |
|---|---|
check_mitm | Confirm mitmdump is on PATH |
start_capture | Spawn mitmdump in the background |
stop_capture | Stop a previously-started capture |
parse_flows | Read a mitmproxy flow file |
har_to_swagger | Convert HAR → OpenAPI 3.0 spec (with path templating) |
flow_to_swagger | mitmproxy2swagger on a flow file → OAS |
filter_flows | Filter flows by method/host/path/status/content-type |
extract_secrets | Heuristically find tokens, JWTs, API keys |
pip install mitmproxy mitmproxy2swagger
pip install -e ./servers/re-mitm2swagger
Most mobile apps and SPAs talk to a REST API. The fastest way to understand the API surface is to capture traffic, then derive the spec. mitmproxy handles the capture, mitmproxy2swagger handles the spec — this server glues them together with secrets detection and filtering.
Run Claude Code as an MCP server so any agent can delegate coding tasks to it
@microsoft✓ OfficialBrowser automation using accessibility snapshots instead of screenshots
@googleapis✓ OfficialGoogle's universal MCP server supporting PostgreSQL, MySQL, MongoDB, Redis, and 10+ databases
@github✓ OfficialOfficial GitHub integration for repos, issues, PRs, and CI/CD workflows