Labsco
MCP SERVER

Burp Suite

by PortSwigger

PortSwigger's own Burp Suite extension for MCP — connect an AI client to a running Burp instance and let it work with your proxy history and tooling.

Vulnerability Scanning & Application Security
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 `MCP` tab in the Burp UI
  • An `Enabled` checkbox that controls whether the MCP server is running at all
  • A separate `Enable tools that can edit your config` switch, 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.