LABSCO SUMMARY
Burp's own vendor extension, so the integration is not a third-party guess at its internals.
The switch worth noticing is the separate toggle for configuration-editing tools: the default gives an assistant access to Burp without giving it the ability to change how Burp is configured.
What it is
A Java extension you load into Burp Suite. It hosts an MCP server inside Burp and ships a packaged stdio proxy for clients that cannot speak SSE, so the AI client talks to the Burp instance you already have open.
What you get
- A Burp extension that exposes Burp to MCP clients, configured from an
MCPtab in the Burp UI - An
Enabledcheckbox that controls whether the MCP server is running at all - A separate
Enable tools that can edit your configswitch, which decides whether tools that modify Burp configuration files are exposed - An automatic installer for Claude Desktop that writes the client configuration for you
- A packaged stdio proxy server for clients that only support stdio, alongside the SSE endpoint for clients that do not need it
Requirements
Burp Suite, plus Java and the jar command available on your PATH — verify with java --version and jar --version. Build the extension with ./gradlew embedProxyJar, which produces build/libs/burp-mcp-all.jar, then load it in Burp under Extensions > Add with the extension type set to Java. By default the MCP server listens on http://127.0.0.1:9876, and the host and port are configurable under Advanced options in the MCP tab. Claude Desktop currently supports stdio servers only, so it runs the packaged proxy jar with --sse-url pointing at your Burp MCP server URL; the extension's installer can extract that jar and write the config for you.
Setup effort
Build from source — git clone https://github.com/PortSwigger/mcp-server.git
USE CASES
01
Bringing an assistant into a Burp session
Load the extension, enable the server, and point a client at it — the assistant works against the instance you already have running.
02
Connecting Claude Desktop
Run the installer from the extension and it writes the Claude Desktop config, launching the packaged proxy against your Burp MCP URL.
03
Using a client that speaks SSE directly
Skip the proxy and give the client the server URL from the MCP tab.
04
Keeping the assistant out of your Burp settings
Leave the config-editing switch off; the tools that can modify Burp configuration files are then not exposed at all.
05
Adding your own tools
Tools are declared in Tools.kt as serializable data classes, with the tool name derived from the class and pagination available by extending the Paginated interface.
BEFORE YOU INSTALL
What to know first
Requires
- Burp Suite
- Java on your PATH (check with java --version)
- The jar command on your PATH (check with jar --version)
Where it runs
The documented client runs the server on your machine.
INSTALLATION
Connect your client
You clone and build this one yourself.
Server setup
TERMINAL
git clone https://github.com/PortSwigger/mcp-server.git
cd mcp-server
./gradlew embedProxyJarIn Burp Suite: Extensions tab -> Add -> Extension Type 'Java' -> select build/libs/burp-mcp-all.jar -> Next
In Burp's MCP tab, tick the Enabled checkbox to start the server (default http://127.0.0.1:9876)
MCP Clients
Claude Desktop
Burp's MCP tab has an installer that writes this entry into your Claude Desktop config for you. To add it by hand instead, use the installer option in the MCP tab to extract the proxy jar (mcp-proxy-all.jar), then add the block:
CLAUDE DESKTOP · JSON
{
"mcpServers": {
"burp": {
"command": "<YOUR_PATH_TO_JAVA_EXECUTABLE_PACKAGED_BURP>",
"args": [
"-jar",
"<YOUR_PATH_TO_MCP>/proxy/jar/mcp-proxy-all.jar",
"--sse-url",
"<YOUR_BURP_MCP_SERVER_URL_CONFIGURED>"
]
}
}
}command is the Java executable packaged with Burp; the -jar path is where you extracted mcp-proxy-all.jar (not the build/libs/burp-mcp-all.jar you loaded into Burp); --sse-url is the server address set in Burp's MCP tab, http://127.0.0.1:9876 by default. Restart Claude Desktop with Burp running and the extension loaded.