Reverse engineer REST API specs from captured HTTP traffic and live sessions.
Copy the install command and let the AI configure it · recommended for beginners
No copy-paste install info for "re-mitm2swagger" yet — see the docs or source repo.
Using this set of HTTP traffic captured via mitmproxy, reverse engineer the REST API and output as complete an OpenAPI 3.0 spec as possible, including paths, methods, parameters, request bodies, response schemas, and examples.
A draft OpenAPI specification inferred from real traffic, ready for documentation or API tools.
I intercepted API requests from an internal web app in a test environment. Organize all discovered endpoints by resource and identify authentication methods, common status codes, and likely data models.
A resource-grouped endpoint inventory and structured analysis to understand undocumented services.
Compare the existing OpenAPI document with the API definition inferred from captured traffic. Identify missing endpoints, parameters, response fields, and potentially outdated descriptions, then suggest revisions.
A documentation gap report highlighting coverage issues and update recommendations.
Capture, inspect, replay, and modify HTTP traffic for debugging and testing.
Analyze, intercept, and replay HTTP/HTTPS traffic for debugging and security testing
Parse API specs to expose endpoints, schemas, and auth details quickly.
Query and process large Swagger/OpenAPI docs to quickly find API details.
Convert any OpenAPI spec into an MCP server with endpoint tools.
Use natural language to explore, call, and test Swagger/OpenAPI APIs.