Skip to main content
mcpSource-backed
Burp Suite MCP Server logo

Burp Suite MCP Server

PortSwigger's Burp Suite MCP Server extension connects Burp Suite to MCP clients through an SSE server or packaged stdio proxy for request, Repeater, Intruder, history, scanner, Collaborator, and configuration workflows.

by PortSwigger · submitted by oktofeesh1·added 2026-06-06·
Review first review before installing

Open the source and read safety notes before installing.

Citation facts

Source-backed facts for citing this resource, derived directly from the registry — also available as plain text for AI assistants.

Source URLs
https://raw.githubusercontent.com/PortSwigger/mcp-server/main/README.md, https://github.com/PortSwigger/mcp-server
Brand
Burp Suite MCP Server
Brand domain
portswigger.net
Brand asset source
brandfetch
Safety notes
Burp Suite MCP Server can send HTTP/1.1 and HTTP/2 requests, create Repeater tabs, send requests to Intruder, toggle Proxy Intercept, pause or resume Burp's task execution engine, and update the active message editor., In Burp Suite Professional it can also expose scanner issues and generate or poll Collaborator payloads for out-of-band testing., The extension includes approval flows for outbound HTTP requests and sensitive data access, but users can configure always-allow targets and disable some approval requirements., Configuration editing tools can import project-level or user-level Burp options when enabled in the extension, which can change proxy, scanner, target, and other Burp behavior., Use only on systems and applications where testing is authorized; active requests, Intruder traffic, scanner workflows, and Collaborator payloads can affect third-party services., Keep the MCP server bound to trusted local interfaces and avoid exposing the SSE server to untrusted networks.
Privacy notes
Proxy HTTP history, WebSocket history, Organizer items, scanner issues, request and response bodies, headers, cookies, tokens, session identifiers, and Collaborator interaction data may be returned to the MCP client., The extension can read project-level and user-level Burp configuration; upstream code filters some configuration credentials when configured, but users should still treat exported options as sensitive., MCP prompts, responses, Burp logs, and client transcripts can retain target URLs, credentials, payloads, vulnerability details, and proprietary application behavior., The stdio proxy and SSE server bridge Burp traffic into the MCP client process; keep client configs, proxy paths, and Burp project files protected.
Author
PortSwigger
Submitted by
oktofeesh1
Claim status
unclaimed
Last verified
2026-06-06

Decision playbook

Review trust signals before you adopt

Signals are present but mixed. Use the checklist below to confirm the source and operational safety for your environment.

Compare context
Selected

0

Current score

63

Baseline

Delta

No baseline selected

No major trust-signal divergence detected in the current selection.

Source and provenance checks

Needs review

Confirm ownership and provenance before trusting install instructions.

  • Source link availableRequired

    Open the canonical repository and verify ownership.

    Done
  • Source provenance statusRequired

    Marked as source-backed.

    Done
  • Metadata reviewed

    No reviewed flag detected in metadata.

    Pending

Safety and privacy checks

Complete

Validate risk disclosures before installation or API wiring.

  • Safety notes presentRequired

    Review the listed safety guidance before running commands.

    Done
  • Privacy notes presentRequired

    Review data handling notes before connecting accounts or secrets.

    Done
  • Trust level risk gateRequired

    Trust level does not block evaluation.

    Done

Package and install checks

Needs review

Check package metadata and artifact integrity signals.

  • Install payload available

    Install or copy payload is available for review.

    Done
  • Package verification flag

    No package verification flag provided.

    Pending
  • Checksum metadata

    No checksum provided for downloaded artifact.

    Pending

Compare-driven decision checks

Needs review

Use compare context to validate trade-offs before adoption.

  • Compare tray has multiple entries

    Add at least one more entry to compare trust differences.

    Pending
  • Baseline comparison available

    No baseline peer selected yet.

    Pending
  • Diverging trust signals identified

    No major trust-signal divergence found.

    Pending

Setup at a glance

CLI install

Copy-ready — paste the snippet to get started.

20 minutes

Adoption plan

Balanced adoption plan

Current risk score 24/100. Use staged verification before broader rollout.

Risk 24

Pre-adoption checks

Validate source and review signals before any execution.

  • Confirm source provenanceRequired

    Source URL/provenance metadata is present.

    Done
  • Confirm metadata review state

    No review metadata found; increase manual validation.

    Pending
  • Verify install payload

    Install/config payload exists and can be inspected.

    Done

Security checks

Confirm safety, privacy, and package integrity signals.

  • Review safety notesRequired

    Safety notes are present.

    Done
  • Review privacy notesRequired

    Privacy notes are present.

    Done
  • Verify package integrity metadata

    No package verification/checksum metadata.

    Pending

Rollout

Adopt in controlled steps based on the selected plan.

  • Run in isolated sandbox firstRequired

    Use a constrained sandbox and observe behavior across multiple tasks.

    Pending
  • Roll out graduallyRequired

    Roll out to a small cohort before wider usage.

    Pending
  • Set monitoring and fallback

    Define rollback path and monitor errors after adoption.

    Pending

Evidence readiness

Evidence readiness matrix · balanced

Missing required evidence: Metadata review. Risk score 31.

Risk 31

Source provenance

Present

Source repository/provenance is listed.

Required in this preset

Metadata review

Missing

Review metadata is missing.

Required in this preset

Safety notes

Present

Safety notes are present.

Required in this preset

Privacy notes

Present

Privacy notes are present.

Optional in this preset

Package integrity

Missing

Package integrity metadata is missing.

Optional in this preset

Install payload

Present

Install payload is available.

Required in this preset

Required gaps: Metadata review

Decision timeline

Decision timeline · balanced

Blocking gaps: Check metadata review status. Risk 28.

Risk 28

triage

Confirm source provenanceRequired

Source/provenance metadata is available.

Done

triage

Check metadata review statusRequired

Review metadata is missing.

Pending

verify

Review safety notesRequired

Safety notes are available.

Done

verify

Review privacy notes

Privacy notes are available.

Done

verify

Validate package integrity metadata

Package integrity metadata is missing.

Pending

rollout

Verify install payload and commandsRequired

Install payload is available.

Done

Blockers: Check metadata review status

Prerequisite readiness

Prerequisite readiness

5 prerequisites to line up before setup.

0/5 ready
Permissions & scopes1Network & hosting2General220 minutes

Safety & privacy surface

Safety & privacy surface

6 safety and 4 privacy notes across 5 risk areas. Review closely: credentials & tokens, permissions & scopes, network access.

5 areas
  • SafetyNetwork accessBurp Suite MCP Server can send HTTP/1.1 and HTTP/2 requests, create Repeater tabs, send requests to Intruder, toggle Proxy Intercept, pause or resume Burp's task execution engine, and update the active message editor.
  • SafetyGeneralIn Burp Suite Professional it can also expose scanner issues and generate or poll Collaborator payloads for out-of-band testing.
  • SafetyNetwork accessThe extension includes approval flows for outbound HTTP requests and sensitive data access, but users can configure always-allow targets and disable some approval requirements.
  • SafetyGeneralConfiguration editing tools can import project-level or user-level Burp options when enabled in the extension, which can change proxy, scanner, target, and other Burp behavior.
  • SafetyPermissions & scopesUse only on systems and applications where testing is authorized; active requests, Intruder traffic, scanner workflows, and Collaborator payloads can affect third-party services.
  • SafetyNetwork accessKeep the MCP server bound to trusted local interfaces and avoid exposing the SSE server to untrusted networks.
  • PrivacyCredentials & tokensProxy HTTP history, WebSocket history, Organizer items, scanner issues, request and response bodies, headers, cookies, tokens, session identifiers, and Collaborator interaction data may be returned to the MCP client.
  • PrivacyCredentials & tokensThe extension can read project-level and user-level Burp configuration; upstream code filters some configuration credentials when configured, but users should still treat exported options as sensitive.
  • PrivacyCredentials & tokensMCP prompts, responses, Burp logs, and client transcripts can retain target URLs, credentials, payloads, vulnerability details, and proprietary application behavior.
  • PrivacyLocal filesThe stdio proxy and SSE server bridge Burp traffic into the MCP client process; keep client configs, proxy paths, and Burp project files protected.

Disclosure: Source-backed Burp Suite extension from PortSwigger. The repository includes a GPL-3.0 license file and a BApp manifest for the Java extension.

Safety notes

  • Burp Suite MCP Server can send HTTP/1.1 and HTTP/2 requests, create Repeater tabs, send requests to Intruder, toggle Proxy Intercept, pause or resume Burp's task execution engine, and update the active message editor.
  • In Burp Suite Professional it can also expose scanner issues and generate or poll Collaborator payloads for out-of-band testing.
  • The extension includes approval flows for outbound HTTP requests and sensitive data access, but users can configure always-allow targets and disable some approval requirements.
  • Configuration editing tools can import project-level or user-level Burp options when enabled in the extension, which can change proxy, scanner, target, and other Burp behavior.
  • Use only on systems and applications where testing is authorized; active requests, Intruder traffic, scanner workflows, and Collaborator payloads can affect third-party services.
  • Keep the MCP server bound to trusted local interfaces and avoid exposing the SSE server to untrusted networks.

Privacy notes

  • Proxy HTTP history, WebSocket history, Organizer items, scanner issues, request and response bodies, headers, cookies, tokens, session identifiers, and Collaborator interaction data may be returned to the MCP client.
  • The extension can read project-level and user-level Burp configuration; upstream code filters some configuration credentials when configured, but users should still treat exported options as sensitive.
  • MCP prompts, responses, Burp logs, and client transcripts can retain target URLs, credentials, payloads, vulnerability details, and proprietary application behavior.
  • The stdio proxy and SSE server bridge Burp traffic into the MCP client process; keep client configs, proxy paths, and Burp project files protected.

Prerequisites

  • Burp Suite Community or Professional with Java extension support.
  • Java and the `jar` command available for building and loading the extension.
  • Gradle wrapper execution allowed for building `build/libs/burp-mcp-all.jar` from source.
  • An MCP client that can connect to the Burp SSE server or run the packaged stdio proxy.
  • Explicit authorization to test the target applications, hosts, and network traffic exposed through Burp.

Schema details

Install type
cli
Troubleshooting
No
Source repository stats
Scope
Source repo
Collection metadata
Estimated setup
20 minutes
Difficulty
advanced
Tool listing metadata
Disclosure
Source-backed Burp Suite extension from PortSwigger. The repository includes a GPL-3.0 license file and a BApp manifest for the Java extension.
Full copyable content
{
  "mcpServers": {
    "burp": {
      "command": "/path/to/packaged/burp/java",
      "args": [
        "-jar",
        "/path/to/mcp-proxy-all.jar",
        "--sse-url",
        "BURP_MCP_SSE_URL"
      ]
    }
  }
}

About this resource

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

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.

Source citations

Add this badge to your README

Show that Burp Suite MCP Server is listed on HeyClaude. Paste this Markdown into your README — it renders the badge and links back to this page.

Listed on HeyClaude
[![Listed on HeyClaude](https://heyclau.de/badge/mcp/burp-suite-mcp-server.svg)](https://heyclau.de/entry/mcp/burp-suite-mcp-server)

How it compares

Burp Suite MCP Server side by side with 3 alternatives on trust, install, platform support, and disclosed safety notes — all from reviewed registry metadata.

Field

PortSwigger's Burp Suite MCP Server extension connects Burp Suite to MCP clients through an SSE server or packaged stdio proxy for request, Repeater, Intruder, history, scanner, Collaborator, and configuration workflows.

Open dossier

Django extension that exposes MCP endpoints and stdio transport for Django apps, with declarative model query tools, custom toolsets, DRF create/list/ update/delete tool publishing, serializer output, and MCP inspection.

Open dossier

MCP server for GPT Researcher that gives Claude deep research, quick search, report writing, source retrieval, research context, and research-resource tools backed by web search and LLM providers.

Open dossier

MCP server for the Graphlit platform, enabling Claude to ingest, search, retrieve, organize, and operate on files, web pages, feeds, collections, conversations, memory, connectors, crawls, and RAG-ready project knowledge.

Open dossier
Next steps
Trust
Review statusNot reviewedNot reviewedNot reviewedNot reviewed
Package trustPackage not verifiedPackage not verifiedPackage not verifiedPackage not verified
Source provenanceSource-backedSource-backedSource-backedSource-backed
Submitteroktofeesh1oktofeesh1oktofeesh1oktofeesh1
Install riskReview firstReview firstReview firstReview first
Notes Safety ✓ Privacy ✓ Safety ✓ Privacy ✓ Safety ✓ Privacy ✓ Safety ✓ Privacy ✓
BrandBurp Suite MCP Server logoBurp Suite MCP ServerDjango MCP Server logoDjango MCP ServerGPT Researcher MCP Server logoGPT Researcher MCP ServerGraphlit MCP Server logoGraphlit MCP Server
Categorymcpmcpmcpmcp
SourceSource-backedSource-backedSource-backedSource-backed
AuthorPortSwiggerSmart GTSAssaf ElovicGraphlit
Added2026-06-062026-06-062026-06-062026-06-06
Platforms
Harness
Source repo
Safety notesBurp Suite MCP Server can send HTTP/1.1 and HTTP/2 requests, create Repeater tabs, send requests to Intruder, toggle Proxy Intercept, pause or resume Burp's task execution engine, and update the active message editor. In Burp Suite Professional it can also expose scanner issues and generate or poll Collaborator payloads for out-of-band testing. The extension includes approval flows for outbound HTTP requests and sensitive data access, but users can configure always-allow targets and disable some approval requirements. Configuration editing tools can import project-level or user-level Burp options when enabled in the extension, which can change proxy, scanner, target, and other Burp behavior. Use only on systems and applications where testing is authorized; active requests, Intruder traffic, scanner workflows, and Collaborator payloads can affect third-party services. Keep the MCP server bound to trusted local interfaces and avoid exposing the SSE server to untrusted networks.Django MCP Server can expose Django model querysets, custom Python methods, DRF create/list/update/delete views, serializers, resources, and low-level FastMCP tools to an MCP client. Published DRF create, update, and delete tools can mutate application data if their serializers, views, and authentication rules permit it. The README notes that built-in DRF authentication classes, permission classes, filter backends, and pagination are disabled for published DRF tools in favor of MCP authentication; review this carefully before reusing production views. Query tools can evaluate QuerySets and return database records; restrict queryset scope and fields before exposing sensitive models. Require confirmation and application-level authorization before exposing write tools, email-sending methods, admin-like actions, or tools that touch customer, employee, financial, health, or regulated data.GPT Researcher MCP Server sends research queries to configured search retrievers and LLM providers, which can create API costs and external data exposure. The server exposes `deep_research`, `quick_search`, `write_report`, source, context, prompt, and resource workflows that can gather and synthesize live web content. Docker mode auto-selects SSE transport on `0.0.0.0:8000`; bind it only on trusted networks and avoid exposing unauthenticated endpoints publicly. Generated reports can contain outdated, biased, incomplete, or hallucinated claims; review sources before acting on medical, legal, financial, or safety-critical output. Protect Claude Desktop or MCP client configuration files because they may contain API keys in the `env` block.Graphlit MCP Server can ingest files, web pages, messages, posts, emails, issues, text, memory, feeds, crawls, and connected SaaS data into a Graphlit project. Tools can create or delete contents, feeds, collections, conversations, specifications, and workflows, and can configure project defaults when explicitly requested. Web crawling, web search, screenshots, podcast search, feed scheduling, publishing, and connector operations may contact third-party services and process external content. Generated audio and image publishing can call configured model/provider services and consume credits or quota. Require confirmation before ingesting private repositories, emails, drive files, Slack/Teams/Discord data, customer documents, large crawls, generated media, deletion operations, or project configuration changes.
Privacy notesProxy HTTP history, WebSocket history, Organizer items, scanner issues, request and response bodies, headers, cookies, tokens, session identifiers, and Collaborator interaction data may be returned to the MCP client. The extension can read project-level and user-level Burp configuration; upstream code filters some configuration credentials when configured, but users should still treat exported options as sensitive. MCP prompts, responses, Burp logs, and client transcripts can retain target URLs, credentials, payloads, vulnerability details, and proprietary application behavior. The stdio proxy and SSE server bridge Burp traffic into the MCP client process; keep client configs, proxy paths, and Burp project files protected.Django sessions, request headers, model names, field names, primary keys, QuerySet results, serializer output, DRF request bodies, custom tool arguments, and tool responses can be exposed to the MCP client. Exposed models may contain user accounts, permissions, customer records, orders, messages, files, logs, internal notes, audit trails, or application-specific secrets. Remote streamable HTTP deployments can move application data outside the original Django UI and audit path if MCP auth, OAuth metadata, and retention are not configured correctly. Stdio usage can still expose data through local MCP client logs, transcripts, and tool traces. Keep MCP endpoint access, serializer fields, queryset filters, and tool docstrings intentionally narrow for each app.Research queries, prompts, source URLs, fetched snippets, research context, generated reports, and cost metadata can enter the MCP client context. Provider APIs and search retrievers may receive sensitive research topics, entity names, customer details, or internal strategy questions. The server keeps in-process research IDs, context, source lists, and source URLs for later report/source/context calls during the session. Docker, n8n, SSE, or Streamable HTTP deployments can expose research sessions and messages to other systems on the network if not isolated. Local logs and troubleshooting output may include queries, errors, endpoint names, provider configuration issues, or session identifiers.Graphlit environment IDs, organization IDs, JWT secrets, project IDs, resource IDs, connector tokens, URLs, files, emails, messages, issues, transcripts, screenshots, memories, conversations, usage records, and retrieved sources can be exposed to the MCP client. Ingested documents may be extracted to Markdown; audio and video may be transcribed; images and pages may be described or screenshot. Connected services such as Slack, Discord, Google Drive, Microsoft 365, GitHub, Jira, Linear, Notion, Dropbox, Box, Reddit, and Twitter/X can expose private workspace content. Usage records can include request, response, variables, token counts, bytes, units, and credit charges for project operations. Keep Graphlit secrets in local MCP client configuration only, and review retention, deletion, and connector policies before ingesting regulated or customer data.
Prerequisites
  • Burp Suite Community or Professional with Java extension support.
  • Java and the `jar` command available for building and loading the extension.
  • Gradle wrapper execution allowed for building `build/libs/burp-mcp-all.jar` from source.
  • An MCP client that can connect to the Burp SSE server or run the packaged stdio proxy.
  • Django 4 or 5 application with Python 3.10 or newer.
  • mcp_server added to INSTALLED_APPS and mcp_server.urls included in the Django URL configuration.
  • Review of which Django models, querysets, custom methods, DRF views, serializers, and request context should be exposed to MCP clients.
  • Authentication classes configured through DJANGO_MCP_AUTHENTICATION_CLASSES before exposing non-public data over streamable HTTP.
  • Python 3.11 or newer.
  • OpenAI API key, or another GPT Researcher-compatible LLM provider configuration.
  • Tavily API key or another GPT Researcher-compatible search retriever.
  • A cloned `assafelovic/gptr-mcp` repository with dependencies installed from `requirements.txt`.
  • Active Graphlit platform account and project access.
  • Graphlit organization ID, environment ID, and JWT secret from the Graphlit API settings dashboard.
  • Node.js 18 or newer for the npm stdio server.
  • Review of which files, URLs, feeds, SaaS connectors, memories, conversations, collections, and web crawls Claude may create or query.
Install
./gradlew embedProxyJar
pip install django-mcp-server
git clone https://github.com/assafelovic/gptr-mcp.git && cd gptr-mcp && pip install -r requirements.txt
npx -y graphlit-mcp-server
Config
Manual-only setup:
./gradlew embedProxyJar
{
  "mcpServers": {
    "django": {
      "command": "python",
      "args": [
        "manage.py",
        "stdio_server"
      ],
      "type": "stdio"
    }
  }
}
Manual-only setup:
python server.py
{
  "mcpServers": {
    "graphlit": {
      "command": "npx",
      "args": [
        "-y",
        "graphlit-mcp-server"
      ],
      "env": {
        "GRAPHLIT_ORGANIZATION_ID": "your-organization-id",
        "GRAPHLIT_ENVIRONMENT_ID": "your-environment-id",
        "GRAPHLIT_JWT_SECRET": "your-jwt-secret"
      },
      "type": "stdio"
    }
  }
}
Citations
ClaimUnclaimedUnclaimedUnclaimedUnclaimed
Open 4 picks in the interactive comparison tool

Related guides

Signals

Loading live community signals…

More like this, weekly

A short, calm digest of reviewed Claude resources. Unsubscribe any time.