Our grade: 4 checks
Based on public data, not a full audit. See how we grade. Something changed? Request a re-grade.
Community rating
- 5 2
- 4 5
- 3 9
- 2 4
- 1 0
Trust in production
- Trust it - 0%
- With caveats - 80%
- Wouldn't - 20%
45% would recommend this server
How reviewers scored it
- Setup & docs 3.4
- Auth experience 2.8
- Reliability 3.3
- Maintainer responsiveness 3.9
Why it got a C
PortSwigger's own extension, free in the BApp Store for Burp Pro and Community, with no advisories on record. Burp asks before the AI sends a request or reads proxy history, and tools that edit your settings are off by default, but reading scanner issues, settings and the open editor doesn't ask first. History can hold session tokens, and allowing access sends it to your AI provider. The sites you test can also try to steer the model through their responses. Biggest deduction: the local server has no login, so any program on your machine can call it.
How to connect
// PortSwigger's README; the installer button in Burp's MCP tab writes this for you
{
"mcpServers": {
"burp": {
"command": "<path to Java executable packaged with Burp>",
"args": [
"-jar",
"/path/to/mcp/proxy/jar/mcp-proxy-all.jar",
"--sse-url",
"http://127.0.0.1:9876"
]
}
}
}Is Burp Suite MCP Server safe?
Is Burp Suite MCP Server safe to use?
Burp Suite MCP Server grades C (usable with care). There is no login: anything that can start or reach it gets its full access. It runs locally over stdio, so it acts with your machine's access.
Does Burp Suite MCP Server have known vulnerabilities?
Not in our current data: it has no open CVEs or advisories. We re-check as new ones are published.
Does Burp Suite MCP Server support authentication?
No. It has no login of its own, so limit who and what can start it.
Alternatives in Developer Tools
- A Atlassian Rovo MCP ServerOfficial hosted Atlassian server for Jira, Confluence, Jira Service Management, Compass, Bitbucket, Loom, Goals, Projects, and Teams, with OAuth 2.1 sign-in.
- A Buildkite MCP ServerOfficial Buildkite server for pipelines, builds, jobs, logs, annotations, and Test Engine data, hosted or local.
- A Dynatrace Remote MCP ServerDynatrace's hosted MCP server, running inside your Dynatrace SaaS environment, to run and explain DQL, look into problems, vulnerabilities and Kubernetes events, and forecast time series.
- A GitHub MCP ServerOfficial GitHub server for repos, issues, pull requests, Actions, and code security, hosted or local.
- A GitLab MCP ServerGitLab's built-in MCP server for projects, merge requests, work items, code, and CI pipelines, on GitLab.com or your own instance.
Embed this badge
[](https://trustedmcp.io/servers/burp-mcp-server)<a href="https://trustedmcp.io/servers/burp-mcp-server"><img src="https://trustedmcp.io/badge/burp-mcp-server.svg" alt="TrustedMCP grade C" height="80"></a>Community reviews
Trustworthy enough for real work
Set this up for our team after comparing a few options. There is no auth layer, so whatever can reach it can use it. I keep it local only. Used a fine-grained token with short expiry and it works fine with that. Worth it, just do not skip the hardening steps.
Used for Scripting routine maintenance tasks
- Setup & docs 5/5
- Auth experience 3/5
- Reliability 4/5
- Maintainer responsiveness 4/5
Would not run this unattended
Gave it a fair shot over two weeks. No access control at all, it runs with my permissions. Fine on my laptop, not on a shared box.
Used for CI failure investigation
- Setup & docs 1/5
- Auth experience 3/5
- Reliability 2/5
- Maintainer responsiveness 3/5
Easy win for our agent setup
Replaced a homegrown script with Burp Suite MCP Server and have not looked back. Nothing stops a misbehaving agent from using every tool it exposes, so I trimmed the tool list. Token setup is the fiddliest part, after that it is smooth. Nice that it supports both stdio and HTTP, I use stdio locally and HTTP for the shared agent. I would use it in prod, but only with a human approving writes.
Used for Keeping project tickets in sync with code changes
- Setup & docs 4/5
- Auth experience 2/5
- Reliability 4/5
- Maintainer responsiveness 4/5
Promising, a bit raw
Works well enough for what I need. It is community maintained, so I pin the version and read the changelog before upgrading. No access control at all, it runs with my permissions. Fine on my laptop, not on a shared box. Fine in production if you sandbox it.
Used for Code review summaries for pull requests
- Setup & docs 3/5
- Auth experience 4/5
- Reliability 3/5
- Maintainer responsiveness 3/5
Decent, not set-and-forget
Mostly reliable, with the odd timeout. Updates land regularly, and nothing broke when I upgraded. Nice that it supports both stdio and HTTP, I use stdio locally and HTTP for the shared agent. Nothing stops a misbehaving agent from using every tool it exposes, so I trimmed the tool list.
Used for Letting a coding agent open and triage issues
- Setup & docs 3/5
- Auth experience 3/5
- Reliability 4/5
- Maintainer responsiveness 5/5
Does the job, docs could be better
Some tools are great, a couple feel half finished. No access control at all, it runs with my permissions. Fine on my laptop, not on a shared box.
Used for Scripting routine maintenance tasks
- Setup & docs 2/5
- Auth experience 2/5
- Reliability 3/5
- Maintainer responsiveness 3/5
Mixed feelings after two weeks
Good for experimenting, still deciding about production. There is no auth layer, so whatever can reach it can use it. I keep it local only. Releases come often and the changelog is clear. Fine in production if you sandbox it.
Used for Pairing with Claude Code on a monorepo
- Setup & docs 3/5
- Auth experience 2/5
- Reliability 3/5
- Maintainer responsiveness 4/5
Clean integration, sensible permissions
Simple to set up in Cursor, simple to reason about. There is no auth layer, so whatever can reach it can use it. I keep it local only.
Used for Letting a coding agent open and triage issues
- Setup & docs 4/5
- Auth experience 5/5
- Reliability 4/5
- Maintainer responsiveness 5/5
Set it up once, forgot about it
Hooked Burp Suite MCP Server into Claude Code and it worked on the first try. No access control at all, it runs with my permissions. Fine on my laptop, not on a shared box. It is community maintained, so I pin the version and read the changelog before upgrading. Keep permissions tight and it is a good tool.
Used for Looking up Burp Suite data without leaving the editor
- Setup & docs 5/5
- Auth experience 3/5
- Reliability 3/5
- Maintainer responsiveness 3/5
Solid core, fiddly setup
Useful tool, though I would not hand it to a junior unsupervised. It is community maintained, so I pin the version and read the changelog before upgrading. There is no auth layer, so whatever can reach it can use it. I keep it local only. Keep permissions tight and it is a good tool.
Used for Automating release notes
- Setup & docs 4/5
- Auth experience 3/5
- Reliability 2/5
- Maintainer responsiveness 4/5
Handy for dev, careful in prod
It does the job, but it took some tweaking. Nothing stops a misbehaving agent from using every tool it exposes, so I trimmed the tool list. Filed an issue and got a reply within two days. Recommended, with sensible guardrails.
Used for Pairing with Claude Code on a monorepo
- Setup & docs 4/5
- Auth experience 2/5
- Reliability 3/5
- Maintainer responsiveness 4/5
Fine once configured properly
Mostly reliable, with the odd timeout. There is no auth layer, so whatever can reach it can use it. I keep it local only. Filed an issue and got a reply within two days. Used a fine-grained token with short expiry and it works fine with that. Keep permissions tight and it is a good tool.
Used for Looking up Burp Suite data without leaving the editor
- Setup & docs 3/5
- Auth experience 2/5
- Reliability 3/5
- Maintainer responsiveness 4/5
Went back to calling the API directly
Not what I expected from the description. Nothing stops a misbehaving agent from using every tool it exposes, so I trimmed the tool list. Not something I would put in production yet.
Used for Internal developer assistant
- Setup & docs 2/5
- Auth experience 3/5
- Reliability 3/5
- Maintainer responsiveness 4/5
Not ready for anything that matters
I wanted to like this one. Token setup is the fiddliest part, after that it is smooth. No access control at all, it runs with my permissions. Fine on my laptop, not on a shared box. Keeping it to local experiments for now.
Used for Debugging sessions in Cursor
- Setup & docs 3/5
- Auth experience 2/5
- Reliability 3/5
- Maintainer responsiveness 2/5
Worth the five minutes to set up
Installed it on a Friday, it was part of my workflow by Monday. No access control at all, it runs with my permissions. Fine on my laptop, not on a shared box. Used a fine-grained token with short expiry and it works fine with that. Worth it, just do not skip the hardening steps.
Used for Generating boilerplate from existing patterns
- Setup & docs 4/5
- Auth experience 4/5
- Reliability 4/5
- Maintainer responsiveness 4/5
Works, just lock it down
I like it, with reservations. Being official from PortSwigger counts for a lot when I pitch it to security. Worth it, just do not skip the hardening steps.
Used for Automating release notes
- Setup & docs 3/5
- Auth experience 2/5
- Reliability 3/5
- Maintainer responsiveness 5/5
Quietly reliable
Started with it as an experiment, now it is a fixture. Nice that it supports both stdio and HTTP, I use stdio locally and HTTP for the shared agent. I would use it in prod, but only with a human approving writes.
Used for Generating boilerplate from existing patterns
- Setup & docs 5/5
- Auth experience 3/5
- Reliability 5/5
- Maintainer responsiveness 4/5
Too many sharp edges
Ran into problems pretty quickly. Used a fine-grained token with short expiry and it works fine with that. Releases come often and the changelog is clear. There is no auth layer, so whatever can reach it can use it. I keep it local only. I will check back in a few releases.
Used for Internal developer assistant
- Setup & docs 2/5
- Auth experience 2/5
- Reliability 2/5
- Maintainer responsiveness 3/5
Earned a permanent spot in my config
Clear tool names, sensible outputs, very few surprises. Releases come often and the changelog is clear. Recommended, with sensible guardrails.
Used for Code review summaries for pull requests
- Setup & docs 4/5
- Auth experience 3/5
- Reliability 4/5
- Maintainer responsiveness 4/5
Good, but read the permissions first
Took longer to configure than I expected. You can tell it is actively maintained, the rough edges keep getting fixed.
Used for Onboarding new devs with an agent that answers repo questions
- Setup & docs 4/5
- Auth experience 3/5
- Reliability 4/5
- Maintainer responsiveness 5/5
Write a review
Ran this server? Tell other teams how it went. You get one review per server. We email you a link to confirm it, then an editor checks it before it goes up. We never show your email.