Burp Suite 扩展，增加了内置 MCP 工具、AI 辅助分析、隐私控制、被动和主动扫描等功能
概览
该扩展以（前称 Burp AI Agent）发布。它被重新命名是为了符合 PortSwigger 的 BApp Store 命名要求，并避免与 Burp Suite 内置的服务商混淆。GitHub 仓库（github.com/six2dez/burp-ai-agent）、文档网站（burp-ai-agent.six2dez.com）和配置文件目录（~/.burp-ai-agent/）保留了 burp-ai-agent 标识符以保证连续性。 Custom AI Agent 是 Burp Suite 的一个扩展，将 AI 集成到你的安全工作流程中。使用本地模型或云服务商，通过 MCP 连接外部 AI 代理，让被动/主动扫描器在你专注于手动测试时发现漏洞。 - （CAP-01） — 通过Burp的HTTP传输直接Anthropic Messages API;所有流量都出现在代理历史中。- （SEC-01） — 所有存储的API密钥和令牌均使用javax.crypto按安装密钥加密;偏好设置中无明文。
概述（AI 翻译）
** Burp Suite 与现代人工智能之间的桥梁。**
关于名称的说明： 该扩展发布为Custom AI Agent（前称Burp AI Agent）。它被重新命名是为了符合PortSwigger的BApp Store命名要求，并避免与Burp Suite内置的Burp AI提供者混淆。GitHub仓库（
github.com/six2dez/burp-ai-agent）、文档网站（burp-ai-agent.six2dez.com）和配置目录（~/.burp-ai-agent/）保留了burp-ai-agent标识以保持连续性。
Custom AI Agent 是 Burp Suite 的一个扩展，将 AI 集成到你的安全工作流程中。使用本地模型或云服务商，通过 MCP 连接外部 AI 代理，让被动/主动扫描器在你专注于手动测试时发现漏洞。
[!重要] 如果您运行的是1.0.0或更早版本，请阅读安全警示并升级到最新版本1.1.0. Audit 文件如果开启 Audit 登录，可能会保存 MCP 令牌和完整提示，右键点击即可 “发送给AI”上下文可以绕过隐私模式;两条警示都说明了需要轮换哪些凭证。 这些项目中没有任何一个被授予CVE或GHSA标识符。
第一版有什么新内容。
本页由 AI 翻译，技术细节请以原文为准。
README
以下为原文 README 节选，完整内容请查看原文。
Custom AI Agent
The bridge between Burp Suite and modern AI.
A note on the name: This extension is published as Custom AI Agent (formerly Burp AI Agent). It was renamed to comply with PortSwigger’s BApp Store naming requirements and to avoid confusion with Burp Suite’s built-in Burp AI provider. The GitHub repository (
github.com/six2dez/burp-ai-agent), the documentation site (burp-ai-agent.six2dez.com), and the configuration directory (~/.burp-ai-agent/) keep theburp-ai-agentidentifier for continuity.
Custom AI Agent is an extension for Burp Suite that integrates AI into your security workflow. Use local models or cloud providers, connect external AI agents via MCP, and let passive/active scanners find vulnerabilities while you focus on manual testing.
[!IMPORTANT] If you are running 1.0.0 or earlier, read the security advisories and upgrade to the latest release, 1.1.0. Audit files written with Audit logging on may hold the MCP token and full prompts, and right-click “send to AI” context could bypass the privacy mode; both advisories say which credentials to rotate. No CVE or GHSA identifier has been issued for any of them.
What’s new in v1.1.0
Two builds from one repository, built for the BApp Store resubmission. Full detail in CHANGELOG.md.
- Two builds. The BApp Store build (
./gradlew bappJar) has the 8 extension-native MCP tools, Burp AI and the six HTTP backends. The GitHub full build (./gradlew fullJar) has all 59 MCP tools, the five CLI backends, the external MCP client and the opt-in auto-queue. Both are on Releases, each with a.sha256. Load only one at a time; Which Build? compares them. - The BApp Store build’s AI gate. The BApp Store build runs on Burp Community and Burp Professional; it sends AI requests only while Burp’s “Use AI” setting is enabled for the extension, and with it off it loads and refuses every AI request.
- Passive scans send nothing to the target. Passive findings the AI Active Scanner can test are listed as suggested targets in its queue dialog, in both builds, and you queue them by hand: nothing is sent to a target before you confirm.
- Clean unload. Unloading leaves no thread, timer or MCP listener of the extension running and starts no new request to an AI provider.
- Issue details are HTML-encoded. Payloads, values taken from the target and AI text show as literal text in Burp’s issue view and reports.
- The AI scanners start OFF at every load, in both builds; switching one on lasts until Burp unloads the extension.
What’s new in v1.0.1
安装
npx -y supergateway --sse http://127.0.0.1:9876/sse配置
{
"mcpServers": {
"burp-ai-agent": {
"command": "npx",
"args": [
"-y",
"supergateway",
"--sse",
"http://127.0.0.1:9876/sse"
]
}
}
}