Burp Suite MCP Server Extension
LocalAbout Burp Suite MCP Server Extension
Burp Suite MCP Server Extension is a Burp Suite extension that connects Burp to AI clients through the Model Context Protocol. It includes an installer for Claude Desktop and a packaged stdio proxy for clients that only support stdio servers.
Key features
- 01Connects Burp Suite to AI clients via MCP
- 02Installer that configures Claude Desktop automatically
- 03SSE server and stdio proxy access modes
- 04Optional tools that edit Burp configuration
- 05Configurable host and port for the server
Use cases
- 01Let an AI client query and work with Burp data during testing
- 02Set up the Burp MCP server in Claude Desktop
- 03Connect Burp to a client that supports only stdio servers
MCP support
The extension runs an MCP server inside Burp and exposes its tools to MCP clients through an SSE endpoint or the bundled stdio proxy.
Configuration
Local server config is the same for every client. Copy it into your client’s MCP config file.
We haven’t collected a package or remote endpoint for this server. Follow the instructions in the project README.
Tools
Local servers expose tools only once running on your machine, and the maintainer has not provided a tool list.
Details
From the project READMEBurp Suite MCP Server Extension
Overview
Integrate Burp Suite with AI Clients using the Model Context Protocol (MCP).
For more information about the protocol visit: modelcontextprotocol.io
Features
- Connect Burp Suite to AI clients through MCP
- Automatic installation for Claude Desktop
- Comes with packaged Stdio MCP proxy server
Usage
- Install the extension in Burp Suite
- Configure your Burp MCP server in the extension settings
- Configure your MCP client to use the Burp SSE MCP server or stdio proxy
- Interact with Burp through your client!
Installation
Prerequisites
Ensure that the following prerequisites are met before building and installing the extension:
- Java: Java must be installed and available in your system's PATH. You can verify this by running
java --versionin your terminal. - jar Command: The
jarcommand must be executable and available in your system's PATH. You can verify this by runningjar --versionin your terminal. This is required for building and installing the extension.
Building the Extension
-
Clone the Repository: Obtain the source code for the MCP Server Extension.
git clone https://github.com/PortSwigger/mcp-server.git -
Navigate to the Project Directory: Move into the project's root directory.
cd mcp-server -
Build the JAR File: Use Gradle to build the extension.
./gradlew embedProxyJarThis command compiles the source code and packages it into a JAR file located in
build/libs/burp-mcp-all.jar.
Loading the Extension into Burp Suite
- Open Burp Suite: Launch your Burp Suite application.
- Access the Extensions Tab: Navigate to the
Extensionstab. - Add the Extension:
- Click on
Add. - Set
Extension TypetoJava. - Click
Select file ...and choose the JAR file built in the previous step. - Click
Nextto load the extension.
- Click on
Upon successful loading, the MCP Server Extension will be active within Burp Suite.
Configuration
Configuring the Extension
Configuration for the extension is done through the Burp Suite UI in the MCP tab.
- Toggle the MCP Server: The
Enabledcheckbox controls whether the MCP server is active. - Enable config editing: The
Enable tools that can edit your configcheckbox allows the MCP server to expose tools which can edit Burp configuration files. - Advanced options: You can configure the port and host for the MCP server. By default, it listens on
http://127.0.0.1:9876.
Claude Desktop Client
To fully utilize the MCP Server Extension with Claude, you need to configure your Claude client settings appropriately. The extension has an installer which will automatically configure the client settings for you.
-
Currently, Claude Desktop only support STDIO MCP Servers for the service it needs. This approach isn't ideal for desktop apps like Burp, so instead, Claude will start a proxy server that points to the Burp instance,
which hosts a web server at a known port (localhost:9876). -
Configure Claude to use the Burp MCP server
You can do this in one of two ways:-
Option 1: Run the installer from the extension This will add the Burp MCP server to the Claude Desktop config.
-
Option 2: Manually edit the config file
Open the file located at~/Library/Application Support/Claude/claude_desktop_config.json, and replace or update it with the following:{ "mcpServers": { "burp": { "command": "<path to Java executable packaged with Burp>", "args": [ "-jar", "/path/to/mcp/proxy/jar/mcp-proxy-all.jar", "--sse-url", "<your Burp MCP server URL configured in the extension>" ] } } }
-
-
Restart Claude Desktop - assuming Burp is running with the extension loaded.
Manual installations
If you want to install the MCP server manually you can either use the extension's SSE server directly or the packaged Stdio proxy server.
SSE MCP Server
To use the SSE server directly, provide the configured server URL to your MCP client:
http://127.0.0.1:9876
Stdio MCP Proxy Server
The source code for the proxy server can be found here: MCP Proxy Server
In order to support MCP Clients which only support Stdio MCP Servers, the extension comes packaged with a proxy server for passing requests to the SSE MCP server extension.
If you want to use the Stdio proxy server you can use the extension's installer option to extract the proxy server jar. Once you have the jar you can add the following command and args to your client configuration:
/path/to/packaged/burp/java -jar /path/to/proxy/jar/mcp-proxy-all.jar --sse-url http://127.0.0.1:9876
If you modify the proxy source, rebuild and copy it into this project before packaging the extension:
# From mcp-proxy
./gradlew shadowJar
cp build/libs/mcp-proxy-all.jar /path/to/mcp-server/libs/mcp-proxy-all.jar
# From mcp-server
./gradlew embedProxyJar
Creating / modifying tools
Tools are defined in src/main/kotlin/net/portswigger/mcp/tools/Tools.kt. To define new tools, create a new serializable
data class with the required parameters which will come from the LLM.
The tool name is auto-derived from its parameters data class. A description is also needed for the LLM. You can return
a string or a List<ContentBlock> to provide data back to the LLM.
Extend the Paginated interface to add auto-pagination support.
Comments
New to MCP?
From what the protocol is to installing your first server, these answers cover most first questions.
An open protocol that defines how AI applications connect to external tools and data in a uniform way. Clients talk to the model; MCP servers provide tools, resources and prompt templates. They exchange standard messages, so one server can be reused by many clients.