Burp Suite MCP Server

Content

Burp Suite MCP Server is PortSwigger's MCP extension for connecting Burp Suite to Claude and other MCP clients. It runs inside Burp, exposes an SSE MCP server by default on localhost, and includes a packaged stdio proxy for clients that only support stdio servers.

Use it when Claude needs to work alongside a human tester in Burp Suite: sending requests, preparing Repeater or Intruder workflows, inspecting proxy history, reviewing scanner issues, using Collaborator payloads, or reading and updating Burp configuration under operator control.

Source Review

• https://github.com/PortSwigger/mcp-server
• https://raw.githubusercontent.com/PortSwigger/mcp-server/main/README.md
• https://raw.githubusercontent.com/PortSwigger/mcp-server/main/LICENSE
• https://raw.githubusercontent.com/PortSwigger/mcp-server/main/BappManifest.bmf
• https://raw.githubusercontent.com/PortSwigger/mcp-server/main/gradle.properties
• https://raw.githubusercontent.com/PortSwigger/mcp-server/main/build.gradle.kts
• https://raw.githubusercontent.com/PortSwigger/mcp-server/main/src/main/kotlin/net/portswigger/mcp/ExtensionBase.kt
• https://raw.githubusercontent.com/PortSwigger/mcp-server/main/src/main/kotlin/net/portswigger/mcp/tools/Tools.kt
• https://raw.githubusercontent.com/PortSwigger/mcp-server/main/src/main/kotlin/net/portswigger/mcp/security/DataAccessSecurity.kt
• https://raw.githubusercontent.com/PortSwigger/mcp-server/main/src/main/kotlin/net/portswigger/mcp/security/HttpRequestSecurity.kt

These sources were reviewed on 2026-06-06. Prefer the live repository, README, license, BApp manifest, Gradle metadata, build script, extension entrypoint, tool implementation, and request and data-access security code for current installation and behavior details.

Features

• Run as a Burp Suite Java extension.
• Expose a local SSE MCP server from the Burp extension.
• Connect stdio-only MCP clients through the packaged MCP proxy JAR.
• Send HTTP/1.1 and HTTP/2 requests through Burp.
• Create Repeater tabs and send requests to Intruder.
• URL encode, URL decode, Base64 encode, Base64 decode, and generate random strings through Burp utilities.
• Export project and user options, with credential filtering available in the extension configuration.
• Import project and user options when configuration-editing tools are enabled.
• Read proxy HTTP history, proxy WebSocket history, Organizer items, and scanner issues.
• Generate and poll Collaborator payloads in Burp Suite Professional.
• Toggle Proxy Intercept and the task execution engine state.

Installation

Build the extension from source:

git clone https://github.com/PortSwigger/mcp-server.git
cd mcp-server
./gradlew embedProxyJar

Then load build/libs/burp-mcp-all.jar in Burp Suite from the Extensions tab as a Java extension. Configure the MCP tab in Burp and connect your MCP client to the local SSE server, usually:

127.0.0.1:9876

For stdio-only clients, use the packaged proxy JAR extracted by the extension:

{
  "mcpServers": {
    "burp": {
      "command": "/path/to/packaged/burp/java",
      "args": [
          "-jar",
          "/path/to/mcp-proxy-all.jar",
          "--sse-url",
          "BURP_MCP_SSE_URL"
        ]
      }
    }
}

Use Cases

• Ask Claude to prepare a Repeater tab for a raw HTTP request.
• Send approved HTTP/1.1 or HTTP/2 requests through Burp.
• Search and summarize proxy history for a target application.
• Review scanner issues during a supervised Burp Suite Professional workflow.
• Generate Collaborator payloads for authorized out-of-band testing.
• Toggle Proxy Intercept or pause Burp's task execution engine during testing.
• Inspect Burp project or user options before changing a test configuration.

Safety and Privacy

Burp Suite MCP Server sits next to sensitive security-testing traffic. Use it only for targets where testing is authorized, and keep request approvals enabled unless the scope is tightly constrained. Intruder, scanner, Collaborator, and manual request tools can generate traffic that affects real services.

The extension can expose HTTP history, WebSocket history, Organizer items, scanner issues, active editor contents, request and response bodies, cookies, authorization headers, session tokens, and vulnerability details. Treat MCP client transcripts and model context as sensitive security records.

If configuration editing is enabled, Claude can apply project-level or user-level Burp option changes. Review exported configuration first, keep credential filtering enabled where appropriate, and bind the MCP server only to trusted local interfaces.

Duplicate Check

Existing MCP entries cover security and vulnerability tools such as Snyk, CVE, Pentest AI, and CLI security workflows, but no Burp Suite MCP Server, PortSwigger/mcp-server, PortSwigger BApp MCP extension, or matching source URL was found in content/mcp.