Skip to content
MCP server

MCP ZAP Server

Self-hosted OWASP ZAP operator that lets AI agents run guided security scans and reports

Install
Pricing
Open source
Platforms
self-hosted, API
Runs
Remotely
Version
0.17.1
Listing updated
2 days ago

About MCP ZAP Server

MCP ZAP Server is an open-source MCP server for security. It runs as a hosted remote server, so there is nothing to install locally.

This server sits between an AI client and a ZAP scanner you run yourself, and keeps the agent on a guided path rather than handing it raw scanner access. Its default tool surface is guided, covering spider and active scans, passive scanning, API imports, findings and report readback. A separate expert surface exposes raw ZAP tools for clients that need them.

Scans start through a queue, with in-memory or PostgreSQL storage, and are tracked through status and stop tools. Operators control who can call what with API-key or JWT auth, tool scopes, runtime policy bundles, rate limits and audit events. Correlation IDs and metrics help trace requests, and findings can be compared against reviewed baselines. A form-login option lets ZAP sign in to an authorised target without the password reaching the AI client.

It runs from a Docker image with Docker Compose for local use and Helm for Kubernetes. The README says it is independent of the ZAP project. Check that the matching release and images are published before installing the current source version, since the README warns about this.

Install

Run in a terminal

claude mcp add mcp-zap-server --env ZAP_API_KEY='<ZAP_API_KEY>' --env MCP_API_KEY='<MCP_API_KEY>' -- docker run -i --rm -e ZAP_API_KEY -e MCP_API_KEY ghcr.io/dtkmn/mcp-zap-server:v0.17.1

Add to claude_desktop_config.json

{
  "mcpServers": {
    "mcp-zap-server": {
      "command": "docker",
      "args": [
        "run",
        "-i",
        "--rm",
        "-e",
        "ZAP_API_KEY",
        "-e",
        "MCP_API_KEY",
        "ghcr.io/dtkmn/mcp-zap-server:v0.17.1"
      ],
      "env": {
        "ZAP_API_KEY": "<ZAP_API_KEY>",
        "MCP_API_KEY": "<MCP_API_KEY>"
      }
    }
  }
}

Add to ~/.cursor/mcp.json

{
  "mcpServers": {
    "mcp-zap-server": {
      "command": "docker",
      "args": [
        "run",
        "-i",
        "--rm",
        "-e",
        "ZAP_API_KEY",
        "-e",
        "MCP_API_KEY",
        "ghcr.io/dtkmn/mcp-zap-server:v0.17.1"
      ],
      "env": {
        "ZAP_API_KEY": "<ZAP_API_KEY>",
        "MCP_API_KEY": "<MCP_API_KEY>"
      }
    }
  }
}

Add to .vscode/mcp.json

{
  "servers": {
    "mcp-zap-server": {
      "type": "stdio",
      "command": "docker",
      "args": [
        "run",
        "-i",
        "--rm",
        "-e",
        "ZAP_API_KEY",
        "-e",
        "MCP_API_KEY",
        "ghcr.io/dtkmn/mcp-zap-server:v0.17.1"
      ],
      "env": {
        "ZAP_API_KEY": "<ZAP_API_KEY>",
        "MCP_API_KEY": "<MCP_API_KEY>"
      }
    }
  }
}

Add to ~/.codeium/windsurf/mcp_config.json

{
  "mcpServers": {
    "mcp-zap-server": {
      "command": "docker",
      "args": [
        "run",
        "-i",
        "--rm",
        "-e",
        "ZAP_API_KEY",
        "-e",
        "MCP_API_KEY",
        "ghcr.io/dtkmn/mcp-zap-server:v0.17.1"
      ],
      "env": {
        "ZAP_API_KEY": "<ZAP_API_KEY>",
        "MCP_API_KEY": "<MCP_API_KEY>"
      }
    }
  }
}

Add to your client's MCP settings (most use this shape)

{
  "mcpServers": {
    "mcp-zap-server": {
      "command": "docker",
      "args": [
        "run",
        "-i",
        "--rm",
        "-e",
        "ZAP_API_KEY",
        "-e",
        "MCP_API_KEY",
        "ghcr.io/dtkmn/mcp-zap-server:v0.17.1"
      ],
      "env": {
        "ZAP_API_KEY": "<ZAP_API_KEY>",
        "MCP_API_KEY": "<MCP_API_KEY>"
      }
    }
  }
}

Configuration

  • ZAP_API_URLHostname or URL of a separately running ZAP daemon reachable from this container.
  • ZAP_API_PORTZAP API port.
  • ZAP_API_KEYAPI key configured on the ZAP daemon.Required
  • MCP_API_KEYAPI key clients must send as X-API-Key.Required
  • MCP_SERVER_TOOLS_SURFACETool surface to expose. Use guided for the safer default workflow, including report readback. Use expert only when clients need raw ZAP tools outside the guided surface.
  • MCP_SECURITY_MODE
  • MCP_SECURITY_ENABLED
  • MCP_SECURITY_ALLOW_PLACEHOLDER_API_KEY
  • ZAP_API_URLHostname or URL of a separately running ZAP daemon reachable from this container.
  • ZAP_API_PORTZAP API port.
  • ZAP_API_KEYAPI key configured on the ZAP daemon.Required
  • MCP_API_KEYAPI key clients must send as X-API-Key.Required
  • MCP_SERVER_TOOLS_SURFACETool surface to expose. Use guided for the safer default workflow, including report readback. Use expert only when clients need raw ZAP tools outside the guided surface.
  • MCP_SECURITY_MODE
  • MCP_SECURITY_ENABLED
  • MCP_SECURITY_ALLOW_PLACEHOLDER_API_KEY

What it does

Guided scan tools
Spider, active and passive scans, API imports and reports on a safer default surface.
Queue-managed scans
Scan starts go through a queue with in-memory or PostgreSQL storage.
Operator guardrails
API-key or JWT auth, tool scopes, rate limits and audit events.
Findings baselines
Reads target-scoped findings and compares against reviewed baselines.
Form login
Lets ZAP log in to an authorised target without exposing the password.
Docker and Helm
Deploys locally with Compose or on Kubernetes.

Good for

  • Run a first crawl and get an HTML report against a demo target
  • Let an agent scan a staging site within set limits
  • Gate CI on findings compared to a baseline
  • Keep an audit trail of scans started by AI clients

Pricing

Open source

Apache-2.0 core; optional paid support from Agentic Lab

Prices change. Check danieltse.org before you buy.

MCP ZAP Server FAQ

What licence is it under?

The site says the open-source core is Apache-2.0.

What do I need to run it?

Docker 20.10 or newer, Docker Compose v2, and an MCP client that supports streamable HTTP and custom headers.

Is it affiliated with ZAP?

No. The README says it is an independent implementation.

How do clients authenticate?

Send the key set in `MCP_API_KEY` as an `X-API-Key` header; JWT is also supported.

Is paid support available?

The site says Agentic Lab offers optional paid support for production adoption, SSO, OAuth2 setup and compliance reporting.

Is MCP ZAP Server free?

Yes. MCP ZAP Server is open source, so you can use and self-host it for free.

How do I add MCP ZAP Server to Claude Code?

Run this command in your terminal: claude mcp add mcp-zap-server --env ZAP_API_KEY='<ZAP_API_KEY>' --env MCP_API_KEY='<MCP_API_KEY>' -- docker run -i --rm -e ZAP_API_KEY -e MCP_API_KEY ghcr.io/dtkmn/mcp-zap-server:v0.17.1

What are the best alternatives to MCP ZAP Server?

The closest alternatives to MCP ZAP Server are REA, Agent Roast, Midplane, Leash and Tinplate Edge AI Safety, Security & EU Compliance.

Alternatives to MCP ZAP Server

  1. REA

    MCP server

    CLI and MCP server that lets coding agents reverse engineer apps and binaries

    Runs locally
    • Open source
    • 464K GitHub stars
    • Developer tools
  2. Agent Roast

    MCP server

    Offline review that flags agent changes which weaken tests, assertions or CI

    Runs locally
    • Open source
    • 4 Hacker News points
    • Developer tools
  3. Midplane

    MCP server

    Postgres gateway for AI agents with table grants, column masking and approval for writes

    Runs locally
    • Open source
    • 5 GitHub stars
    • Databases
  4. Leash

    MCP server

    Review what your AI touched, approve risky actions and undo supported changes

    • 1 tool
    • Remote
    • Free
    • 1 GitHub star
    • Security
  5. SecureCloud

    MCP server

    SentinelOne and IT security catalog, prices, quotes and checkout links for Israel

    • 7 tools
    • Remote
    • Free
    • Security