Burpsuite MCP Server A Model Context Protocol (MCP) server that provides an interface for. Exposed over MCP by the burpsuite mcp server, that capability becomes something an assistant can invoke while it works, not something you go and do afterwards.

What it actually does

This MCP server allows AI assistants to interact with Burpsuite Professional for web security testing and vulnerability scanning. It provides tools for:

Its toolset

Everything the assistant can do here goes through one of these:

• Parameters — - target: Target URL to scan (e.g., https://example.com)
• scan_type — Type of scan to perform (passive, active, or full)
• severity — Filter issues by severity (high, medium, low, info, or all)
• method — Filter by HTTP method (optional)
• status_code — Filter by HTTP status code (optional)
• limit — Maximum number of items to return (default: 10)
• with_parameters — Only show URLs with parameters (optional)
• Tools — 1. start_scan: Start a new vulnerability scan on a target URL
• Resources — 1. Scan Results: burpsuite://scan/{scanId} 2. Issue Details: burpsuite://scan/{scanId}/issue/{issueId} 3. Proxy History

Adding it to your client

The server ships on npm as @smithery/cli, so your MCP client can launch it on demand — there is no separate build step. Add the server block to your client's configuration, restart it, and the tools register themselves.

When to reach for it

This sits in the developer tooling group, where several servers overlap in what they claim to do but differ sharply once you actually set them up. Burpsuite's toolset — Parameters, scan_type, severity and 6 more — is a fair guide to whether it matches your workflow. It is maintained by Cyreslab-AI; worth a glance at recent repository activity before you build anything load-bearing on it.

We check each listing at SyncDev against the project's documentation before it goes live — if something here drifts out of date, it is a bug worth reporting.

Caveats

• It runs with your machine's permissions. That is convenient and also the reason to think about what you point it at before you approve a tool call.
• With 9 tools registered it takes up a noticeable share of the context window; turn it off in projects that never touch Burpsuite.
• MCP clients confirm each tool call by default. Leave that on until you have watched what the burpsuite mcp server does with a few real requests.