Skip to main content
Glama

burp_start

Start Burp Suite Professional with API enabled to automate security testing workflows. Configure Java memory, headless mode, and project files for penetration testing.

Instructions

Start Burp Suite Professional with API enabled

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
jar_pathNoPath to burpsuite_pro.jar (optional, auto-detected)
project_fileNoBurp project file path (optional)
headlessNoRun in headless mode (default: true)
memoryNoJava memory allocation (default: 2g)

Implementation Reference

  • Core handler function that spawns Burp Suite Java process with configured options, waits for startup, and returns success/error status with process details.
    async startBurpSuite(): Promise<ScanResult> {
      try {
        console.error('🚀 Starting Burp Suite...');
    
        if (!this.config.jar_path || !fs.existsSync(this.config.jar_path)) {
          throw new Error('Burp Suite JAR file not found. Please install Burp Suite Professional and set jar_path');
        }
    
        // Prepare user options file for headless mode
        let userOptionsFile = '';
        if (this.config.headless) {
          userOptionsFile = await this.createUserOptionsFile();
        }
    
        // Build command
        const javaArgs = [
          `-Xmx${this.config.memory}`,
          '-Djava.awt.headless=true',
          '-jar', this.config.jar_path,
          '--disable-extensions',
          `--collaborator-server`,
          `--collaborator-location-all`
        ];
    
        if (this.config.headless) {
          javaArgs.push('--unpause-spider-and-scanner');
          javaArgs.push(`--user-config-file=${userOptionsFile}`);
        }
    
        if (this.config.project_file) {
          javaArgs.push(`--project-file=${this.config.project_file}`);
        }
    
        console.error(`Executing: java ${javaArgs.join(' ')}`);
    
        // Spawn Burp Suite process
        this.burpProcess = spawn('java', javaArgs, {
          stdio: ['ignore', 'pipe', 'pipe'],
          detached: false
        });
    
        // Wait for Burp to start up
        await this.waitForBurpStartup();
    
        return {
          target: 'burpsuite',
          timestamp: new Date().toISOString(),
          tool: 'burpsuite_startup',
          results: {
            status: 'started',
            pid: this.burpProcess.pid,
            api_url: this.apiBaseUrl,
            proxy_port: this.config.proxy_port,
            config: this.config
          },
          status: 'success'
        };
    
      } catch (error) {
        return {
          target: 'burpsuite',
          timestamp: new Date().toISOString(),
          tool: 'burpsuite_startup',
          results: {},
          status: 'error',
          error: error instanceof Error ? error.message : String(error)
        };
      }
    }
  • src/index.ts:405-418 (registration)
    Tool registration in MCP server's tool list, including name, description, and input schema definition.
    {
      name: "burp_start",
      description: "Start Burp Suite Professional with API enabled",
      inputSchema: {
        type: "object",
        properties: {
          jar_path: { type: "string", description: "Path to burpsuite_pro.jar (optional, auto-detected)" },
          project_file: { type: "string", description: "Burp project file path (optional)" },
          headless: { type: "boolean", description: "Run in headless mode (default: true)" },
          memory: { type: "string", description: "Java memory allocation (default: 2g)" }
        },
        required: []
      }
    },
  • MCP server switch-case handler for 'burp_start' tool that optionally recreates BurpSuiteIntegration instance and delegates to its startBurpSuite() method.
    case "burp_start":
      // Create new instance with custom config if provided
      if (args.jar_path || args.project_file || args.headless !== undefined || args.memory) {
        this.burpSuite = new BurpSuiteIntegration({
          jar_path: args.jar_path,
          project_file: args.project_file,
          headless: args.headless,
          memory: args.memory
        });
      }
      return respond(await this.burpSuite.startBurpSuite());
  • Helper method called by startBurpSuite to poll Burp Suite REST API until it's ready (up to 5 minutes).
    private async waitForBurpStartup(): Promise<void> {
      const maxAttempts = 60; // 5 minutes
      let attempts = 0;
    
      while (attempts < maxAttempts) {
        try {
          await axios.get(`${this.apiBaseUrl}/v0.1/`, { timeout: 5000 });
          console.error('✅ Burp Suite API is ready');
          return;
        } catch (error) {
          attempts++;
          console.error(`Waiting for Burp startup... (${attempts}/${maxAttempts})`);
          await new Promise(resolve => setTimeout(resolve, 5000));
        }
      }
    
      throw new Error('Burp Suite failed to start within timeout period');
    }
Behavior2/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations provided, the description carries full burden but only states what the tool does without disclosing behavioral traits. It doesn't mention side effects (e.g., starting a process that may consume resources), permissions needed, or error handling, leaving significant gaps for a tool that initiates software.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single, clear sentence with zero wasted words, making it highly efficient and front-loaded. It directly communicates the core action without unnecessary elaboration.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a tool that starts a complex security application with multiple parameters and no output schema, the description is inadequate. It lacks details on expected outcomes, error conditions, or integration with sibling tools, failing to provide sufficient context for effective use.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, so the schema fully documents all parameters. The description adds no additional meaning about parameters beyond what's in the schema, such as explaining interactions or dependencies between them, meeting the baseline for high coverage.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the action ('Start') and target ('Burp Suite Professional with API enabled'), making the purpose evident. However, it doesn't distinguish itself from sibling tools like 'burp_stop' beyond the obvious action difference, missing specific scope or context differentiation.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No guidance is provided on when to use this tool versus alternatives or in what context. The description lacks any mention of prerequisites, typical workflows, or comparisons with related tools like 'burp_active_scan' or 'burp_spider'.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/adriyansyah-mf/mcp-pentest'

If you have feedback or need assistance with the MCP directory API, please join our Discord server