Nuclei MCP Integration provides a standardized interface for performing security scans using Nuclei's vulnerability scanning engine. This server implementation allows you to run vulnerability assessments programmatically through the Model Context Protocol (MCP) ecosystem.
# Linux/macOS
./nuclei-mcp
# Windows
nuclei-mcp.exe
go install github.com/your-org/nuclei-mcp/cmd/nuclei-mcp@latest
git clone https://github.com/your-org/nuclei-mcp.git
cd nuclei-mcp
go mod download
go build -o nuclei-mcp ./cmd/nuclei-mcp
./nuclei-mcp
Start the MCP server:
# If using pre-built binary
./nuclei-mcp
# If built from source
go run cmd/nuclei-mcp/main.go
For testing, use the MCP Inspector:
# Install the MCP Inspector globally
npm install -g @modelcontextprotocol/inspector
# Start the inspector with the Nuclei MCP server
npx @modelcontextprotocol/inspector go run cmd/nuclei-mcp/main.go
The inspector UI will be available at http://localhost:5173
Configuration can be managed through a YAML configuration file or environment variables, checked in the following order:
--config
flagconfig.yaml
in the current directory$HOME/.nuclei-mcp/config.yaml
/etc/nuclei-mcp/config.yaml
Create a config.yaml
file with this structure:
server:
name: "nuclei-mcp"
version: "1.0.0"
port: 3000
host: "127.0.0.1"
cache:
enabled: true
expiry: 1h
max_size: 1000
logging:
level: "info"
path: "./logs/nuclei-mcp.log"
max_size_mb: 10
max_backups: 5
max_age_days: 30
compress: true
nuclei:
templates_directory: "nuclei-templates"
timeout: 5m
rate_limit: 150
bulk_size: 25
template_threads: 10
headless: false
show_browser: false
system_resolvers: true
All configuration options can be set using environment variables with the NUCLEI_MCP_
prefix. For example:
NUCLEI_MCP_SERVER_PORT=3000
NUCLEI_MCP_LOGGING_LEVEL=debug
To connect an MCP client to the Nuclei MCP server:
stdio
(subprocess) or http
(standalone server)go run cmd/nuclei-mcp/main.go
(development) or the binary pathFor HTTP connections, the server defaults to http://127.0.0.1:3000
.
{
"mcpServers": {
"nuclei-scanner": {
"command": "go",
"args": ["run", "cmd/nuclei-mcp/main.go"],
"env": {
"NUCLEI_MCP_SERVER_PORT": "3000",
"NUCLEI_MCP_CACHE_ENABLED": "true"
}
}
}
}
To add this MCP server to Claude Code, run this command in your terminal:
claude mcp add-json "nuclei" '{"command":"go","args":["run","nuclei_mcp.go"]}'
See the official Claude Code MCP documentation for more details.
There are two ways to add an MCP server to Cursor. The most common way is to add the server globally in the ~/.cursor/mcp.json
file so that it is available in all of your projects.
If you only need the server in a single project, you can add it to the project instead by creating or adding it to the .cursor/mcp.json
file.
To add a global MCP server go to Cursor Settings > Tools & Integrations and click "New MCP Server".
When you click that button the ~/.cursor/mcp.json
file will be opened and you can add your server like this:
{
"mcpServers": {
"nuclei": {
"command": "go",
"args": [
"run",
"nuclei_mcp.go"
]
}
}
}
To add an MCP server to a project you can create a new .cursor/mcp.json
file or add it to the existing one. This will look exactly the same as the global MCP server example above.
Once the server is installed, you might need to head back to Settings > MCP and click the refresh button.
The Cursor agent will then be able to see the available tools the added MCP server has available and will call them when it needs to.
You can also explicitly ask the agent to use the tool by mentioning the tool name and describing what the function does.
To add this MCP server to Claude Desktop:
1. Find your configuration file:
~/Library/Application Support/Claude/claude_desktop_config.json
%APPDATA%\Claude\claude_desktop_config.json
~/.config/Claude/claude_desktop_config.json
2. Add this to your configuration file:
{
"mcpServers": {
"nuclei": {
"command": "go",
"args": [
"run",
"nuclei_mcp.go"
]
}
}
}
3. Restart Claude Desktop for the changes to take effect