No installation required - Just configurationUse https://mcp.prowler.com/mcp
Option 2: Run Locally
Local installation - Full controlInstall via Docker, PyPI, or source code
For “Option 1: Managed by Prowler”, go directly to the Configuration Guide to set up your Claude Desktop, Cursor, or other MCP client.
This guide is focused on local installation, “Option 2: Run Locally”.
When running Prowler MCP Server locally (“Option 2: Run Locally”), upgrade to the latest version using the same method chosen for installation. The hosted server (https://mcp.prowler.com/mcp) is always kept up to date by Prowler and requires no action.
Docker
From Source
Build Docker Image
Pull the latest image and restart the container:
docker pull prowlercloud/prowler-mcp
Recreate any running container after pulling the new image so the updated version takes effect.
Pull the latest changes and sync the dependencies:
cd prowler/mcp_servergit pulluv syncuv run prowler-mcp --help
Pull the latest source and rebuild the image:
cd prowler/mcp_servergit pulldocker build -t prowler-mcp .
For production deployments that require customization, it is recommended to use the ASGI application that can be found in prowler_mcp_server.server. This can be run with uvicorn:
The source tree includes entrypoint.sh to simplify switching between the
standard CLI runner and the ASGI app. The first argument selects the mode and
any additional flags are passed straight through:
Omitting the mode defaults to main, matching the prowler-mcp console script.
When uvicorn mode is selected, the script exports PROWLER_MCP_TRANSPORT_MODE=http automatically.This is the default entrypoint for the Docker container.