MCP ZAP Server

MCP ZAP Server runs locally from a container image in an OCI registry such as Docker Hub or GitHub Container Registry: ghcr.io/dtkmn/mcp-zap-server:v0.14.0. The package starts a local server that speaks MCP over Streamable HTTP; the client then connects to it by URL (the entry names docker as the runtime). It reads these environment variables: ZAP_API_URL, ZAP_API_PORT, ZAP_API_KEY (required, secret), MCP_API_KEY (required, secret), MCP_SERVER_TOOLS_SURFACE, MCP_SECURITY_MODE, MCP_SECURITY_ENABLED and MCP_SECURITY_ALLOW_PLACEHOLDER_API_KEY; set them in the client's configuration for this server.

MCP ZAP Server runs locally from a container image in an OCI registry such as Docker Hub or GitHub Container Registry: docker.io/dtkmn/mcp-zap-server:v0.14.0. The package starts a local server that speaks MCP over Streamable HTTP; the client then connects to it by URL (the entry names docker as the runtime). It reads these environment variables: ZAP_API_URL, ZAP_API_PORT, ZAP_API_KEY (required, secret), MCP_API_KEY (required, secret), MCP_SERVER_TOOLS_SURFACE, MCP_SECURITY_MODE, MCP_SECURITY_ENABLED and MCP_SECURITY_ALLOW_PLACEHOLDER_API_KEY; set them in the client's configuration for this server.

Derived from the registry entry, not tested here. What the server does, and on what terms, is set by its publisher; check its repository or website before giving it access to your accounts or files. How to add an MCP server to an assistant · Before you connect