WSL2 has a separate network stack from Windows. Burp's MCP server binds to
Windows 127.0.0.1:9876 and rejects non-loopback connections (403). The
fix is to run the Burp MCP proxy JAR natively on Windows via cmd.exe,
so its outbound connection uses Windows loopback. Stdio is bridged back to
Claude Code in WSL through cmd.exe.
xspatrian
/ BURP_MCP_SETUP.md
Created
May 19, 2026 14:34
# Burp Suite MCP — WSL Setup (direct, no REST)
xspatrian
/ BurpMCP.md
Last active
May 5, 2026 21:18
Burp Suite MCP Server Won't Connect from WSL? Here's the Fix Nobody Talks About
How a simple cmd.exe wrapper solved the localhost networking nightmare between WSL and Burp Suite's MCP Server
If you've been pulling your hair out trying to connect Claude Code, Gemini CLI, or any AI coding assistant to Burp Suite's MCP Server from WSL — and you keep hitting cryptic errors like 403 Forbidden, connection refused, or Blocked browser request without Origin header — this article is for you.
I spent hours debugging this. The fix took 30 seconds once I understood why it was failing.