MCP server for Burp Suite that provides tools for evidence capture, annotation, HTTP request sending, Repeater tab management, and project data access
Server has 15 tools with basic schemas and descriptions, but significant gaps limit production readiness. Most tools have descriptions (10 - 200 chars), but many lack parameter-level detail. Input schemas are present but sparse, most parameters have type and description, but lack constraints (enums, ranges, patterns). Error handling is minimal; most tools return generic 'Error: {message}' without recovery guidance. No tool annotations (readOnlyHint, destructiveHint, idempotentHint) despite several destructive operations (delete_repeater_tab, delete_all_repeater_tabs). Output schemas are undocumented. Naming is generally clear (verb_noun pattern), but some tools conflate multiple concerns (e.g., send_repeater_tab both selects AND sends). Security: no visible credential injection or permission gates. Composition: tools are mostly single-purpose, but some lack chaining IDs in responses.
Annotates a captured Burp PNG with report-ready rectangles, highlights, arrows, text, blur, or redaction. Coordinates are relative to the captured image. Use callout to draw an arrow and its label together.
Captures the Burp Suite window (or full desktop) as PNG evidence. Use crop coordinates to keep only the relevant Repeater, Intruder, Proxy, or Scanner area.
Closes every Repeater request tab, or only those whose title starts with titlePrefix. Irreversible bulk UI action - use it to clear a Repeater cluttered by automation.
Closes one exact Repeater tab in Burp Suite. Provide either tabName or the 1-based tabIndex. This is an irreversible UI action for the selected tab; use the exact name when possible.
Debug: dumps clickable components in the Repeater view.
Debug: introspects the Repeater Send control.
No tool annotations (readOnlyHint, destructiveHint, idempotentHint) despite clear risk levels. delete_repeater_tab, delete_all_repeater_tabs, and send_* tools are marked IRREVERSIBLE/DESTRUCTIVE/WRITE but lack schema hints to guide LLM behavior.
Output schemas undocumented. Tools like list_repeater_tabs, list_burp_evidence, output_project_options, and output_user_options return structured data but do not document field names, types, or pagination. LLMs cannot plan downstream calls without knowing response structure.
Error handling returns generic 'Error: {message}' without recovery guidance. No categorization of retryable vs fatal errors, no suggestions for next steps (e.g., 'Tab not found. Call list_repeater_tabs() to see available tabs.').
Inferred effective spec: <=2025-11-25.
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-23 | C | 61 | <=2025-11-25 | v2 |
Lists recent PNG evidence files created by the Burp MCP extension.
Lists the visible Burp Repeater tabs with 1-based indexes.
Outputs the current Burp Suite project options in JSON format.
Outputs the current Burp Suite user options in JSON format.
Scrolls the Repeater response viewer so the JSON body is visible instead of only headers. fraction 0.0=top, 1.0=bottom. Defaults to the response editor; set requestSide=true to scroll the request instead.
Selects a view tab (Pretty/Raw/Hex/Render/JQ) in the Repeater response (or request) editor. JQ renders the JSON body alone, without the header block above it.
Issues an HTTP/1.1 request and returns the response.
Issues an HTTP/2 request and returns the response. Do NOT pass headers to the body parameter.
Selects a Repeater tab and clicks its Send button so the Response panel is populated. Provide either tabName or the 1-based tabIndex; waitMs controls how long to wait for the response.
Debug tools (inspect_send_control, dump_repeater_ui) have minimal descriptions (<50 chars). LLMs cannot determine when to call them or what they return. Descriptions should explain purpose and output format.
Parameter constraints missing. Many parameters lack enums, ranges, or patterns. E.g., viewName accepts 'Pretty|Raw|Hex|Render|JQ' but no enum constraint; fraction accepts 0.0 - 1.0 but no min/max bounds; waitMs unbounded (could be 0 or 999999).