Skip to content
MCP Shelf

Burp Suite MCP

View on GitHub

Lets an assistant send requests, read proxy history and use Repeater in Burp Suite.

  • Needs your setup first
  • ★ 1.3K GitHub stars
  • Last commit 16 Oct 2026

What is Burp Suite MCP?

Burp Suite MCP is PortSwigger's official extension that lets an assistant send and read HTTP traffic, work with Repeater and Intruder, and query proxy history in Burp Suite.

PortSwigger, the company behind Burp Suite, publishes this extension. Once it is loaded, Burp runs a small MCP server on your computer, and the model can send HTTP/1.1 and HTTP/2 requests, search the proxy and WebSocket history, open requests in Repeater or Intruder, encode and decode values, and switch interception on or off. In Burp Suite Professional it can also read scanner issues and make Collaborator payloads for out-of-band testing.

Burp asks before the model sends a request or reads your history, unless you turn those prompts off. Tools that change Burp’s settings stay off until you tick a box. Use it only on systems you are allowed to test.

Made by
PortSwigger (PortSwigger/mcp-server)
Licence
GPL-3.0
GitHub stars
1.3K
Last commit
16 Oct 2026
Tools
27
Runs on
Your computer
Setup checked
27 Oct 2026
Page updated
27 Oct 2026

Our check: It needs something our Linux test machine does not have (an account, a desktop app, a Mac or a running service), so on 27 Oct 2026 we read its tools from the source code instead of running this config. The npm package called mcp-server is an unrelated project. This server is a Burp extension, installed inside Burp.

MCP Shelf take

Burp Suite needs something our Linux test machine does not have (an account, an app or a service), so on 27 Oct 2026 we read its source and counted 27 tools. 9 of the 27 only read; the other 18 can change things. Other directories point at a package with the same name that belongs to someone else; the config on this page installs the real one. It sits 20th of 21 in its category on our shelf by GitHub stars (1.3K).
MCP Shelf tests: numbers from our own runs, not the README · tested on 27 Oct 2026

What can Burp Suite MCP read and change?

It can read

  • Proxy, WebSocket and Organizer history
  • Scanner issues and Collaborator hits, in Professional
  • Burp's settings, with credentials filtered

It can change

  • Sends real HTTP requests to targets
  • Repeater and Intruder tabs, interception and the task engine
  • Burp's settings, only if config editing is turned on

Safer setup: Keep both approval prompts on, pre-approve only targets in your scope, and leave config editing off.

What's in the pod

What tools does Burp Suite MCP have?

We found 27 tools in its source code on 27 Oct 2026. 9 only read. The rest can change things, so keep your app's "ask before each tool call" setting on for them.

How we tested it: Tool list read from the Kotlin source of the extension (commit 642e6fa). It runs inside Burp Suite, so it cannot start in our sandbox. The scanner and Collaborator tools appear only in Burp Suite Professional.

Changes things18 tools · Can create, edit, send or delete.

ToolWhat it is for
base64_decodeBase64-decodes a string.
base64_encodeBase64-encodes a string.
create_repeater_tabOpens an HTTP/1.1 request in a new Repeater tab.
create_repeater_tab_http2Opens an HTTP/2 request in a new Repeater tab.
generate_collaborator_payloadMakes a Collaborator address for out-of-band testing. Professional only.
generate_random_stringMakes a random string of a given length and character set.
output_project_optionsExports the project settings as JSON, with credentials filtered out by default.
output_user_optionsExports the user settings as JSON.
send_http1_requestSends a raw HTTP/1.1 request and returns the response.
send_http2_requestSends an HTTP/2 request built from pseudo-headers, headers and a body.
send_to_intruderSends a request to Intruder.
set_active_editor_contentsReplaces the text in that editor.
set_project_optionsMerges JSON into the project settings. Off unless config editing is allowed.
set_proxy_intercept_stateTurns proxy interception on or off.
set_task_execution_engine_statePauses or resumes Burp's task engine.
set_user_optionsMerges JSON into the user settings. Off unless config editing is allowed.
url_decodeURL-decodes a string.
url_encodeURL-encodes a string.

Only reads9 tools · Looks things up and changes nothing.

ToolWhat it is for
get_active_editor_contentsReads the message editor you have focused in Burp.
get_collaborator_interactionsChecks for DNS, HTTP or SMTP hits on Collaborator payloads. Professional only.
get_organizer_itemsPages through items saved in Organizer.
get_organizer_items_regexPages through Organizer items that match a regular expression.
get_proxy_http_historyPages through the proxy HTTP history.
get_proxy_http_history_regexPages through the proxy history entries that match a regular expression.
get_proxy_websocket_historyPages through the WebSocket history.
get_proxy_websocket_history_regexPages through WebSocket messages that match a regular expression.
get_scanner_issuesLists the scanner's findings. Professional only.

Grouped and described by us. The README on GitHub lists the inputs each tool takes.

How do I install Burp Suite MCP?

Install steps from the Burp Suite MCP README

The project's own instructions, copied from its README on GitHub on 27 Oct 2026 under its GPL-3.0 licence. They are the source of truth; the ready-made configs further down are built from them. The rest of the README is in the README tab.

Installation
Prerequisites

Ensure that the following prerequisites are met before building and installing the extension:

  1. Java: Java must be installed and available in your system's PATH. You can verify this by running java --version in your terminal.
  2. jar Command: The jar command must be executable and available in your system's PATH. You can verify this by running jar --version in your terminal. This is required for building and installing the extension.
Building the Extension
  1. Clone the Repository: Obtain the source code for the MCP Server Extension.

    git clone https://github.com/PortSwigger/mcp-server.git
    
  2. Navigate to the Project Directory: Move into the project's root directory.

    cd mcp-server
    
  3. Build the JAR File: Use Gradle to build the extension.

    ./gradlew embedProxyJar
    

    This 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
  1. Open Burp Suite: Launch your Burp Suite application.
  2. Access the Extensions Tab: Navigate to the Extensions tab.
  3. Add the Extension:
    • Click on Add.
    • Set Extension Type to Java.
    • Click Select file ... and choose the JAR file built in the previous step.
    • Click Next to load the extension.

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 Enabled checkbox controls whether the MCP server is active.
  • Enable config editing: The Enable tools that can edit your config checkbox 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.

  1. 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).

  2. 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>"
            ]
          }
        }
      }
      
  3. Restart Claude Desktop - assuming Burp is running with the extension loaded.

What you need first

  • Burp Suite Community or Professional
  • The MCP Server extension, from the BApp Store or built from source
  • Java, which comes bundled with Burp

Steps

  1. In Burp, open Extensions > BApp Store and install MCP Server. To build it yourself instead, clone the repository, run ./gradlew embedProxyJar and add build/libs/burp-mcp-all.jar under Extensions > Add.
  2. Open the new MCP tab and check that the server is enabled. It listens on http://127.0.0.1:9876 by default.
  3. Use the tab's installer to write the Claude Desktop config, or to extract the proxy jar for other clients.

Add Burp Suite MCP to your app

Pick your app for a ready-to-paste snippet and where it goes, built from the steps above.

Where it goes: Your terminal, with Burp open

Claude Code
claude mcp add --transport sse burp http://127.0.0.1:9876

Claude Code can talk to the extension's SSE server directly, so no proxy jar is needed. Change the address if you set another host or port in Burp's MCP tab.

Clients that support SSE can skip the proxy and connect straight to http://127.0.0.1:9876. Otherwise point "command" at the Java that ships with Burp and the first path at the proxy jar the installer extracted.

Checked against the project's own install docs on 27 Oct 2026: PortSwigger/mcp-server README, portswigger.net/bappstore.

New to this? See the setup guides for Claude Code, Cursor, Claude Desktop and ChatGPT.

Burp Suite MCP not working? Common fixes

Claude Desktop cannot reach Burp
Burp must be running with the extension loaded and enabled before you start the client. Check the MCP tab.
java: command not found
Point the command at the Java that ships inside Burp. The installer in the MCP tab fills this in for you.
Requests fail with 400 errors
Line endings may be wrong. The extension fixes literal \r\n in headers; for HTTP/2 targets use the HTTP/2 tools and keep headers out of the body.
Scanner and Collaborator tools are missing
They only load in Burp Suite Professional.

How do I configure Burp Suite MCP?

Names are exactly as the project spells them. Required ones are marked.

SettingWhat it does
EnabledConfig · requiredIn Burp's MCP tab: whether the server is running.
Enable tools that can edit your configConfigLets the two set_*_options tools change Burp's settings. Off by default.
Require approval for HTTP requestsConfigBurp asks you before each request the model sends. On by default; you can pre-approve targets.
Require approval for project data accessConfigBurp asks before the model reads the proxy history, WebSocket history or Organizer. On by default.
Host and portConfigWhere the server listens. Default http://127.0.0.1:9876.127.0.0.1:9876

Burp Suite MCP FAQ

How do I connect Burp Suite to Claude?

Install MCP Server from Burp's BApp Store, check that it is enabled in the new MCP tab, then use that tab's installer for Claude Desktop. Keep Burp open while you work.

How do I add Burp Suite MCP to Claude Code?

With Burp running and the extension enabled, run claude mcp add --transport sse burp http://127.0.0.1:9876. Clients without SSE support use the proxy jar the extension can extract.

Does it work with Burp Suite Community?

Yes, most tools do. The scanner and Collaborator tools need Burp Suite Professional.

Can the model attack sites on its own?

It can only send requests through Burp, and by default Burp asks you to approve them first. Test only systems you have permission to test, and keep those prompts on.

Is Burp Suite MCP safe to use?

It gives the model access to your proxy history, which can hold cookies and tokens. Keep the approval prompts for requests and project data on, and leave config editing off.

Is it on npm?

No. The npm package named mcp-server is unrelated. This is a Burp extension from PortSwigger.

Why does Claude Desktop not see Burp?

Burp must be running with the extension enabled before Claude starts, and the config must point at the Java bundled with Burp and the extracted proxy jar.

Is Burp Suite MCP free?

The extension is free and GPL-3.0 licensed. Burp Suite Community is free; Professional is a paid product.

Burp Suite MCP README

This is the project's own README from PortSwigger/mcp-server, written by PortSwigger (PortSwigger/mcp-server), and shared under its GPL-3.0 licence. We copied it on 27 Oct 2026, so the version on GitHub may be newer.

Burp 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:

  1. Java: Java must be installed and available in your system's PATH. You can verify this by running java --version in your terminal.
  2. jar Command: The jar command must be executable and available in your system's PATH. You can verify this by running jar --version in your terminal. This is required for building and installing the extension.
Building the Extension
  1. Clone the Repository: Obtain the source code for the MCP Server Extension.

    git clone https://github.com/PortSwigger/mcp-server.git
    
  2. Navigate to the Project Directory: Move into the project's root directory.

    cd mcp-server
    
  3. Build the JAR File: Use Gradle to build the extension.

    ./gradlew embedProxyJar
    

    This 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
  1. Open Burp Suite: Launch your Burp Suite application.
  2. Access the Extensions Tab: Navigate to the Extensions tab.
  3. Add the Extension:
    • Click on Add.
    • Set Extension Type to Java.
    • Click Select file ... and choose the JAR file built in the previous step.
    • Click Next to load the extension.

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 Enabled checkbox controls whether the MCP server is active.
  • Enable config editing: The Enable tools that can edit your config checkbox 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.

  1. 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).

  2. 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>"
            ]
          }
        }
      }
      
  3. 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.

Two peas, one chat

Chat with AI about Burp Suite

Opens a chat primed with Burp Suite’s README and setup docs from this page, or add it in Cursor to use its tools.

The Cursor button opens Cursor and asks before it adds the server. Fill in any keys it needs in Cursor’s MCP settings.

Peas in a pod

What are the alternatives to Burp Suite MCP?

How Burp Suite MCP lines up against its neighbours on the shelf. See every developer tools server.

  • Burp Suite MCPThis pea

    Lets an assistant send requests, read proxy history and use Repeater in Burp Suite.

    Tools
    27
    Runs on
    Your computer
    Licence
    GPL-3.0
    Stars
    1.3K
  • Ref MCP

    Docs search for coding agents that returns only the part of the page that matters.

    Tools
    2
    Runs on
    Your computer or hosted
    Licence
    MIT
    Stars
    1.2K
  • Desktop Commander

    A terminal, file search and surgical file edits for your assistant.

    Tools
    25
    Runs on
    Your computer
    Licence
    MIT
    Stars
    10.1K
  • Serena

    IDE-style "find symbol" and "edit symbol" for an agent, backed by language servers.

    Tools
    3 (REPL)
    Runs on
    Your computer
    Licence
    GPL-3.0
    Stars
    30.7K
  • Context7

    Pulls current, version-specific library docs into the conversation.

    Tools
    2
    Runs on
    Your computer or hosted
    Licence
    MIT
    Stars
    63.7K
  • GitHub

    GitHub's own server for repos, issues, pull requests and Actions.

    Tools
    46
    Runs on
    Hosted or your computer
    Licence
    MIT
    Stars
    34K
Full docs on GitHubPortSwigger/mcp-server

Something wrong on this page? Tell us.