The Composable HTTP Debugger Stack rules to mock, intercept, and rewrite traffic — combine any actions, reuse anywhere.

Visualize how every HTTP/HTTPS request flows through HTTPeep's composable rule engine — from capture to response delivery.
Eight Core Features
Not just a pile of features — each one solves real development and debugging scenarios
Rule-based request forwarding with file-based configuration. Version control, save, reuse, and chain execution. Multi-condition matching + action pipeline + three resolve exits.
Pause before request, intercept before response—debug HTTP like code. Modify in real-time then pass or abort.
Map requests to local files, changes take effect immediately. Support JSON, JS scripts, any static resources.
Route production traffic to local services without code changes or hosts file modifications.
Latency, bandwidth limiting, random failures—simulate real network conditions and reproduce production issues locally.
Partial modifications on real responses instead of full mocks. Keep real data, only change what you want to test.
TUI with full feature parity—rule configuration, traffic capture, breakpoint debugging, all in your terminal. Perfect for SSH/remote servers.
File-based debugging configurations that can be saved, exported, and shared. Rules become reusable debugging assets.
Based on a deterministic pipeline architecture: Match → Actions → Resolve → Response. Front-end Mocking, environment isolation, anomaly simulation — one rule for each scenario, freely combining various actions without backend cooperation.

Pause before requests, intercept before responses—full control over every network interaction

Built-in MCP Server, AI agents like Claude/Cursor/Copilot can directly query session data, generate Mock rules, and analyze abnormal requests. Combined with the CLI, automated debugging workflows are at your fingertips.
Debugging configuration is based on files, which can be saved, exported, and shared with teams. Rules become reusable debugging assets.
~/.httpeep/rules/ ├── rule.yaml # Rule Configuration ├── bypass.yaml # Bypass Configuration ├── dns_override.yaml # DNS Override Configuration ├── external_proxy.yaml # External Proxy Configuration └── rate_limit.yaml # Rate Limit Configuration
# rule.yaml - Main Rule Configuration Example
- id: rule_mnhi5xkt
description: "Frontend Mock API"
enabled: true
builtin: false
stopAfterMatched: false
match:
domains:
- type: exact
value: api.example.com
originProtocol: https
requestActions: []
resolve:
type: map_local_dir
filePath: /Users/chris/mocks/api
headers:
x-httpeep-debug: '1'
responseActions:
- type: delay_response
id: action_1775140499860
enabled: true
delayMs: 500
- type: throttle_response
id: action_1775591855867
enabled: true
speed:
max: 384
burst: 768Manage each environment/project independently
Track modification history
Share rule configurations
Quick migration and backup
Multi-environment DNS configuration management, say goodbye to frequent hosts file modifications

Capture → Rule → Modify → Done
Download and use, start capturing and debugging traffic in minutes
Choose platform to install, one-click install Root CA to system trust, enable HTTPS decryption.
macOS 10.15+ · Windows 10+ · glibc 2.31+
Start the proxy, browser or system traffic automatically goes through HTTPeep, real-time list display.
Supports Chrome, Terminal, Docker, mobile devices
Set up forwarding, Mock, and breakpoint rules; configure once for permanent effect, exportable for team sharing.
Map Local · Breakpoint · Delay · Reject
Intercept target requests, modify data in real-time, observe application reaction after release, and locate issues.
Edit · Continue · Abort · Replay
Explore our collection of ready-to-use rule templates for mocking, intercepting, and rewriting HTTP traffic.
Explore Rule TemplatesFree to download. No installation required.