AI-powered security operations for Wazuh SIEM—use any MCP-compatible client to ask security questions in plain English. Faster threat detection, incident triage, and compliance checks with real-time monitoring and anomaly spotting. Production-ready MCP server for conversational SOC workflows.
# Add to your Claude Code skills
git clone https://github.com/gensecaihq/Wazuh-MCP-Server
README.md
Wazuh MCP Server
Talk to your SIEM. Query alerts, hunt threats, check vulnerabilities, and trigger active responses across your entire Wazuh deployment — through natural conversation with any AI assistant.
Your Wazuh SIEM generates thousands of alerts, vulnerability findings, and agent events daily. Investigating them means juggling dashboards, writing API queries, and manually correlating data across tools.
This MCP server turns that workflow into a conversation:
You: "Show me critical alerts from the last hour"
AI: [calls get_wazuh_alerts] Found 3 critical alerts:
1. SSH brute force from 10.0.1.45 → agent-003 (Rule 5712, Level 10)
2. Rootkit detection on agent-007 (Rule 510, Level 12)
3. FIM change /etc/shadow on agent-001 (Rule 550, Level 10)
You: "Block that source IP on agent-003"
AI: [calls wazuh_block_ip] Blocked 10.0.1.45 via firewall-drop on agent-003.
You: "Which agents have unpatched critical CVEs?"
AI: [calls get_critical_vulnerabilities] 3 agents with critical vulnerabilities...
It works with Claude Desktop, Open WebUI + Ollama (fully local, air-gapped), , or any MCP-compliant client.
Fair-code workflow automation platform with native AI capabilities. Combine visual building with custom code, self-host or cloud, 400+ integrations.
183,625
dxt
genai
hacktoberfest
hacktoberfest-accepted
hacktoberfest2025
mcp
mcp-server
mcpserver
model-context-protocol
model-context-protocol-servers
python
wazuh
wazuh-integration
mcphost
Works With Cloud AND Local LLMs
This is a standard MCP tool server. It doesn't care what LLM you use — it just executes tools and returns results.
| Mode | LLM | Client | Data leaves your network? |
|------|-----|--------|--------------------------|
| Cloud | Claude, GPT, etc. | Claude Desktop, any MCP client | Yes (to LLM provider) |
| Local | Llama, Qwen, Mistral via Ollama | Open WebUI, mcphost, IBM/mcp-cli | No. Fully air-gappable. |
For security teams that can't send SIEM data to cloud APIs (compliance, air-gapped networks, data sovereignty), the local mode with Ollama keeps everything on-premises. Both modes coexist — same server, same tools, same API.
Quick Start: Local LLM with mcphost
# 1. Start the MCP server
docker compose up -d
# 2. Install mcphost (Go binary, no dependencies)
go install github.com/mark3labs/mcphost@latest
# 3. Configure
cat > ~/.mcphost.yml << 'EOF'
mcpServers:
wazuh:
type: remote
url: http://localhost:3000/mcp
headers: ["Authorization: Bearer ${env://MCP_API_KEY}"]
EOF
# 4. Chat with your SIEM using a local model
export MCP_API_KEY="your-key-from-server-logs"
mcphost --model ollama/qwen2.5:7b
Quick Start: Multi-User SOC with Open WebUI
Open WebUI v0.6.31+ connects to our /mcp endpoint natively. Add it as an MCP tool server in Admin Settings, and your entire team gets AI-powered SIEM analysis with conversation history, RBAC, and a web UI.
48 Security Tools
Every tool is validated, rate-limited, scope-checked, and audit-logged.
| Category | Tools | What They Do |
|----------|-------|-------------|
| Alerts (4) | get_wazuh_alertsget_wazuh_alert_summaryanalyze_alert_patternssearch_security_events | Query, filter, search, and analyze alert data via Elasticsearch |
| Agents (6) | get_wazuh_agentsget_wazuh_running_agentscheck_agent_healthget_agent_processesget_agent_portsget_agent_configuration | Monitor agent status, running processes, open ports, and configs |
| Vulnerabilities (3) | get_wazuh_vulnerabilitiesget_critical_vulnerabilitiesvulnerability_summary | Query CVEs by severity, agent, and package |
| Security Analysis (6) | analyze_security_threatcheck_ioc_reputationperform_risk_assessmentget_top_security_threatsgenerate_security_reportrun_compliance_check | Threat analysis, IOC lookup, risk scoring, compliance checks |
| System (10) | get_wazuh_statisticsget_wazuh_cluster_healthget_wazuh_rules_summarysearch_wazuh_manager_logs ... | Cluster health, rules, manager logs, stats |
| Active Response (9) | wazuh_block_ipwazuh_isolate_hostwazuh_kill_processwazuh_disable_userwazuh_quarantine_file ... | Block IPs, isolate hosts, kill processes, quarantine files |
| Verification (5) | wazuh_check_blocked_ipwazuh_check_agent_isolationwazuh_check_processwazuh_check_user_status ... | Verify active response actions took effect |
| Rollback (5) | wazuh_unisolate_hostwazuh_enable_userwazuh_restore_filewazuh_firewall_allowwazuh_host_allow | Undo active response actions |
Quick Start
Prerequisites
Docker 20.10+ with Compose v2
Wazuh 4.8.0–4.14.4 with API access enabled
Deploy
git clone https://github.com/gensecaihq/Wazuh-MCP-Server.git
cd Wazuh-MCP-Server
cp .env.example .env
This server sits between an LLM and your SIEM. Security is not optional.
| Layer | What It Does |
|-------|-------------|
| RBAC | Per-tool scope enforcement. 14 active response tools require wazuh:write. Read-only tokens can query but never trigger actions. Authless mode is read-only by default. |
| Audit Logging | Every destructive tool call (block IP, isolate host, kill process) is logged with client ID, session, timestamp, and full arguments. |
| Output Sanitization | Credentials, tokens, and API keys in alert full_log fields are redacted before reaching the LLM. Prevents credential leakage through AI responses. |
| Input Validation | Every parameter validated: regex agent IDs, ipaddress module for IPs, shell metacharacter blocking for active response, Elasticsearch Query DSL (no string interpolation). |
| Rate Limiting | Per-client sliding window with escalating block duration (10s → 5min). |
| Circuit Breakers | Wazuh API failures trigger fail-fast for 60s, auto-recover. Single trial in HALF_OPEN state. |
| Log Sanitization | Global filter redacts passwords, tokens, secrets from all server logs. |
| Container Hardening | Non-root user, read-only filesystem, CAP_DROP ALL, no-new-privileges. |
# Generate a secure API key
python -c "import secrets; print('wazuh_' + secrets.token_urlsafe(32))"
Configuration
Required
| Variable | Description |
|----------|-------------|
| WAZUH_HOST | Wazuh Manager hostname or IP |
| WAZUH_USER | API username |
| WAZUH_PASS | API password |
Optional
| Variable | Default | Description |
|----------|---------|-------------|
| WAZUH_PORT | 55000 | Manager API port |
| MCP_HOST | 0.0.0.0 | Server bind address |
| MCP_PORT | 3000 | Server port |
| AUTH_MODE | bearer | oauth, bearer, or none |
| AUTH_SECRET_KEY | auto-generated | JWT signing key |
| AUTHLESS_ALLOW_WRITE | false | Allow active response in authless mode |
| ALLOWED_ORIGINS | https://claude.ai | CORS origins (comma-separated) |
| REDIS_URL | — | Redis URL for multi-instance session storage |
Combine this MCP server with Wazuh OpenClaw Autopilot to build a fully autonomous Security Operations Center.
While this server gives you conversational access to Wazuh, OpenClaw deploys AI agents that work around the clock — triaging alerts, correlating incidents, and recommending responses without human intervention.
The agent harness performance optimization system. Skills, instincts, memory, security, and research-first development for Claude Code, Codex, Opencode, Cursor and beyond.
