Sign inSign up

hackerdogs/zap-mcp

By hackerdogs

•Updated 3 months ago

OWASP ZAP MCP Server

Image
0

713

hackerdogs/zap-mcp repository overview

Hackerdogs
hackerdogs ⁠

⁠OWASP ZAP MCP Server

MCP server wrapper for Zap⁠ — Automated security scanning proxy (headless).

⁠What is Zap?

Zap (zap.sh) is a security tool that provides: Automated security scanning proxy (headless).

See zaproxy/zap-core⁠ for full documentation.

No API keys required — Zap runs locally inside the Docker container.

Summary. MCP server wrapper for Zap⁠ — Automated security scanning proxy (headless).

Tools:

  • run_zap — Run zap.sh with the given arguments. Returns structured JSON output.

⁠Tools Reference

⁠run_zap

Run zap.sh with the given arguments. Returns structured JSON output.

ParameterTypeRequiredDefaultDescription
argumentsstringYes—Command-line arguments (e.g. "--help")
timeout_secondsintegerNo600Maximum execution time in seconds
Example response
{
  "raw": "zap.sh output will appear here"
}

⁠Example Prompts

Here are example prompts you can use with Claude (or any MCP client) when this tool is connected:

  • "Run zap.sh with --help to see all available options."
  • "Use zap to scan the target 192.168.1.1."
  • "What options does zap.sh support? Show me its help output."
  • "Run zap against example.com with default settings."
  • "Execute zap.sh with verbose output enabled."
  • "Use the zap tool to analyze the target and report findings."

⁠Deploy

docker-compose up -d
⁠Docker Run (stdio mode)
docker run -i --rm hackerdogs/zap-mcp:latest
⁠Docker Run (HTTP streamable mode)
docker run -d -p 8231:8231 \
  -e MCP_TRANSPORT=streamable-http \
  -e MCP_PORT=8231 \
  hackerdogs/zap-mcp:latest

⁠MCP Client Configuration

⁠Stdio mode (default)

Add to your Claude Desktop or Cursor MCP config:

{
  "mcpServers": {
    "zap-mcp": {
      "command": "docker",
      "args": ["run", "-i", "--rm", "-e", "MCP_TRANSPORT", "hackerdogs/zap-mcp:latest"],
      "env": {
        "MCP_TRANSPORT": "stdio"
      }
    }
  }
}
⁠HTTP mode (streamable-http)

First, start the server using Docker Compose or docker run with HTTP mode (see Deploy⁠ above), then point your MCP client at the running server:

{
  "mcpServers": {
    "zap-mcp": {
      "url": "http://localhost:8231/mcp"
    }
  }
}

When to use HTTP mode: HTTP mode is ideal for shared/remote deployments, multi-user setups, and Hackerdogs⁠ scheduled prompts. The server runs as a long-lived process and accepts connections from multiple MCP clients concurrently.

⁠Environment Variables

VariableDefaultDescription
MCP_TRANSPORTstdioTransport mode: stdio or streamable-http
MCP_PORT8231HTTP port (only used with streamable-http)

⁠Installing in Hackerdogs

The fastest way to get started is through Hackerdogs⁠:

  1. Log in to your Hackerdogs account.
  2. Go to the Tools Catalog.
  3. Search for the tool by name (e.g. "nuclei", "naabu", "julius").
  4. Expand the tool card and click Install — you're ready to go.

Give it a couple of minutes to go live. Then start querying by asking Hackerdogs to use the tool explicitly (e.g. "Use naabu to scan example.com"). If you don't specify, Hackerdogs will automatically choose the best tool for the job — it may choose this one on its own.

  1. Vendor API key required? Add your key in the config environment variable field before clicking Install. Your key will be encrypted at rest.
  2. Enable / Disable the tool anytime from the Enabled Tools page.
  3. Need to update a key or parameter? Go to My Tools → toggle Show Decrypted Values → edit → Save.

Want to contribute or chat with the team? Join our Discord⁠.

⁠Build

docker build -t hackerdogs/zap-mcp:latest .

⁠Testing

⁠Automated tests
./test.sh
⁠Test directly with Docker

1. Start the server in HTTP mode:

docker run -d --rm --name zap-mcp-test -p 8231:8231 \
  -e MCP_TRANSPORT=streamable-http \
  hackerdogs/zap-mcp:latest

2. Initialize the MCP session:

SESSION_ID=$(curl -s -D - -X POST http://localhost:8231/mcp \
  -H "Content-Type: application/json" \
  -H "Accept: application/json, text/event-stream" \
  -d '{"jsonrpc":"2.0","id":1,"method":"initialize","params":{"protocolVersion":"2024-11-05","capabilities":{},"clientInfo":{"name":"test","version":"0.1"}}}' \
  2>&1 | grep -i mcp-session-id | awk '{print $2}' | tr -d '\r\n')

curl -s -X POST http://localhost:8231/mcp \
  -H "Content-Type: application/json" \
  -H "Accept: application/json, text/event-stream" \
  -H "mcp-session-id: $SESSION_ID" \
  -d '{"jsonrpc":"2.0","method":"notifications/initialized"}'

3. Call a tool:

curl -s -X POST http://localhost:8231/mcp \
  -H "Content-Type: application/json" \
  -H "Accept: application/json, text/event-stream" \
  -H "mcp-session-id: $SESSION_ID" \
  -d '{"jsonrpc":"2.0","id":2,"method":"tools/call","params":{"name":"run_zap","arguments":{"arguments":"--help"}}}'

4. Clean up:

docker stop zap-mcp-test

⁠Running the tool directly (bypassing MCP)

You can run the zap.sh (OWASP ZAP) CLI in the same container by overriding the entrypoint for headless passive or active scanning without starting the MCP server.

Show help:

docker run -i --rm --entrypoint zap.sh hackerdogs/zap-mcp:latest -h

Tag summary

Content type

Image

Digest

sha256:9593bf611…

Size

368.4 MB

Last updated

3 months ago

docker pull hackerdogs/zap-mcp