Burp MCP: LLM-assisted traffic review
Tip
Learn & practice AWS Hacking:
HackTricks Training AWS Red Team Expert (ARTE)
Learn & practice GCP Hacking:HackTricks Training GCP Red Team Expert (GRTE)
Learn & practice Az Hacking:HackTricks Training Azure Red Team Expert (AzRTE)
Support HackTricks
- Check the subscription plans!
- Join the 💬 Discord group or the telegram group or follow us on Twitter 🐦 @hacktricks_live.
- Share hacking tricks by submitting PRs to the HackTricks and HackTricks Cloud github repos.
Overview
Burp’s MCP Server extension can expose intercepted HTTP(S) traffic to MCP-capable LLM clients so they can reason over real requests/responses for passive vulnerability discovery and report drafting. The intent is evidence-driven review (no fuzzing or blind scanning), keeping Burp as the source of truth.
Architecture
- Burp MCP Server (BApp) listens on
127.0.0.1:9876and exposes intercepted traffic via MCP. - MCP proxy JAR bridges stdio (client side) to Burp’s MCP SSE endpoint.
- Optional local reverse proxy (Caddy) normalizes headers for strict MCP handshake checks.
- Clients/backends: Codex CLI (cloud), Gemini CLI (cloud), or Ollama (local).
Setup
1) Install Burp MCP Server
Install MCP Server from the Burp BApp Store and verify it is listening on 127.0.0.1:9876.
2) Extract the proxy JAR
In the MCP Server tab, click Extract server proxy jar and save mcp-proxy.jar.
3) Configure an MCP client (Codex example)
Point the client to the proxy JAR and Burp’s SSE endpoint:
# ~/.codex/config.toml
[mcp_servers.burp]
command = "java"
args = ["-jar", "/absolute/path/to/mcp-proxy.jar", "--sse-url", "http://127.0.0.1:19876"]
Then run Codex and list MCP tools:
codex
# inside Codex: /mcp
4) Fix strict Origin/header validation with Caddy (if needed)
If the MCP handshake fails due to strict Origin checks or extra headers, use a local reverse proxy to normalize headers (this matches the workaround for the Burp MCP strict validation issue).
brew install caddy
mkdir -p ~/burp-mcp
cat >~/burp-mcp/Caddyfile <<'EOF'
:19876
reverse_proxy 127.0.0.1:9876 {
# lock Host/Origin to the Burp listener
header_up Host "127.0.0.1:9876"
header_up Origin "http://127.0.0.1:9876"
# strip client headers that trigger Burp's 403 during SSE init
header_up -User-Agent
header_up -Accept
header_up -Accept-Encoding
header_up -Connection
}
EOF
Start the proxy and the client:
caddy run --config ~/burp-mcp/Caddyfile &
codex
Using different clients
Codex CLI
- Configure
~/.codex/config.tomlas above. - Run
codex, then/mcpto verify the Burp tools list.
Gemini CLI
The burp-mcp-agents repo provides launcher helpers:
source /path/to/burp-mcp-agents/gemini-cli/burpgemini.sh
burpgemini
Ollama (local)
Use the provided launcher helper and select a local model:
source /path/to/burp-mcp-agents/ollama/burpollama.sh
burpollama deepseek-r1:14b
Example local models and approximate VRAM needs:
deepseek-r1:14b(~16GB VRAM)gpt-oss:20b(~20GB VRAM)llama3.1:70b(48GB+ VRAM)
Prompt pack for passive review
The burp-mcp-agents repo includes prompt templates for evidence-driven analysis of Burp traffic:
passive_hunter.md: broad passive vulnerability surfacing.idor_hunter.md: IDOR/BOLA/object/tenant drift and auth mismatches.auth_flow_mapper.md: compare authenticated vs unauthenticated paths.ssrf_redirect_hunter.md: SSRF/open-redirect candidates from URL fetch params/redirect chains.logic_flaw_hunter.md: multi-step logic flaws.session_scope_hunter.md: token audience/scope misuse.rate_limit_abuse_hunter.md: throttling/abuse gaps.report_writer.md: evidence-focused reporting.
Optional attribution tagging
To tag Burp/LLM traffic in logs, add a header rewrite (proxy or Burp Match/Replace):
Match: ^User-Agent: (.*)$
Replace: User-Agent: $1 BugBounty-Username
Safety notes
- Prefer local models when traffic contains sensitive data.
- Only share the minimum evidence needed for a finding.
- Keep Burp as the source of truth; use the model for analysis and reporting, not scanning.
References
- Burp MCP + Codex CLI integration and Caddy handshake fix
- Burp MCP Agents (workflows, launchers, prompt pack)
- Burp MCP Server BApp
- PortSwigger MCP server strict Origin/header validation issue
Tip
Learn & practice AWS Hacking:
HackTricks Training AWS Red Team Expert (ARTE)
Learn & practice GCP Hacking:HackTricks Training GCP Red Team Expert (GRTE)
Learn & practice Az Hacking:HackTricks Training Azure Red Team Expert (AzRTE)
Support HackTricks
- Check the subscription plans!
- Join the 💬 Discord group or the telegram group or follow us on Twitter 🐦 @hacktricks_live.
- Share hacking tricks by submitting PRs to the HackTricks and HackTricks Cloud github repos.


