githubEdit

Burp Suite

Burp MCP + Codex CLI

Everything is documented and updated at https://github.com/six2dez/burp-mcp-agentsarrow-up-right

This guide shows how to connect Burp Suite MCP Server to Codex CLI so that Codex can reason directly on your real HTTP traffic — no API keys, no scanning, no fuzzing.

You end up with a reasoning engine wired directly into your interception stack.


What you get

• Passive vuln discovery

• IDOR / auth bypass / SSRF / logic flaw detection

• Report writing from real Burp evidence

• No API keys

• Full local traffic control


1. Install Burp MCP Server

Install MCP Server from Burp’s BApp Store.

Once installed, open its tab and click:

Extract server proxy jar

This downloads:

This is the stdio MCP bridge Codex uses.


2. Configure Codex MCP

Edit:

Append:


3. Install Caddy reverse proxy

Burp MCP currently enforces strict Origin validation and rejects extra headers sent by Codex, which causes handshake failures see more herearrow-up-right.

We solve this with a local reverse proxy.

Install Caddy:


4. Create the Caddyfile

Create:

Paste:


5. Start everything

Verify:

You should see:


6. Test it

Examples:


7. One-command launcher (optional)

Add to your ~/.zshrc (check your paths first):

Run:


Tips

Proxy options

Append something to the user-agent

Match `^User-Agent: (.*)$`

Replace `User-Agent: $1 BugBounty-Username`

Preferred extensions

Private collaborator server

Burp macros

Collaborator SSRF explotation mindmaparrow-up-right

DOM Invader

Last updated

Was this helpful?