Wazuh-MCP-Server MCP — 使用場景, 安裝 & 即時演示

為什麼要用

核心特性

48 tools across alerts, agents, vulnerabilities, active response, compliance
Output sanitization — redacts credentials before they reach the LLM
Rate limiting + circuit breakers to protect Wazuh Manager
RBAC per tool; audit logs for destructive actions
Deploys via Docker Compose; supports Wazuh 4.8–4.14

即時演示

實際使用效果

wazuh.replay ▶ 就緒

0/0

安裝

選擇你的客戶端

~/Library/Application Support/Claude/claude_desktop_config.json · Windows: %APPDATA%\Claude\claude_desktop_config.json

{
  "mcpServers": {
    "wazuh": {
      "command": "uvx",
      "args": [
        "Wazuh-MCP-Server"
      ],
      "_inferred": true
    }
  }
}

開啟 Claude Desktop → Settings → Developer → Edit Config。儲存後重啟應用。

~/.cursor/mcp.json · .cursor/mcp.json

{
  "mcpServers": {
    "wazuh": {
      "command": "uvx",
      "args": [
        "Wazuh-MCP-Server"
      ],
      "_inferred": true
    }
  }
}

Cursor 使用與 Claude Desktop 相同的 mcpServers 格式。專案級設定優先於全域。

VS Code → Cline → MCP Servers → Edit

{
  "mcpServers": {
    "wazuh": {
      "command": "uvx",
      "args": [
        "Wazuh-MCP-Server"
      ],
      "_inferred": true
    }
  }
}

點擊 Cline 側欄中的 MCP Servers 圖示，然後選 "Edit Configuration"。

~/.codeium/windsurf/mcp_config.json

{
  "mcpServers": {
    "wazuh": {
      "command": "uvx",
      "args": [
        "Wazuh-MCP-Server"
      ],
      "_inferred": true
    }
  }
}

格式與 Claude Desktop 相同。重啟 Windsurf 生效。

~/.continue/config.json

{
  "mcpServers": [
    {
      "name": "wazuh",
      "command": "uvx",
      "args": [
        "Wazuh-MCP-Server"
      ]
    }
  ]
}

Continue 使用伺服器物件陣列，而非映射。

~/.config/zed/settings.json

{
  "context_servers": {
    "wazuh": {
      "command": {
        "path": "uvx",
        "args": [
          "Wazuh-MCP-Server"
        ]
      }
    }
  }
}

加入 context_servers。Zed 儲存後熱重載。

claude mcp add wazuh -- uvx Wazuh-MCP-Server

一行命令搞定。用 claude mcp list 驗證，claude mcp remove 移除。

使用場景

實戰用法： Wazuh-MCP-Server

Triage overnight alerts in 10 minutes instead of 2 hours

👤 SOC analysts ⏱ ~20 min advanced

何時使用： Shift start. Hundreds of alerts overnight. You need to find the real ones without reading every row.

前置條件

Wazuh Manager API creds — Wazuh UI > API credentials

步驟

Summarize

For last 12 hours: group alerts by rule group, count severity 10+ per group, top 5 agents with most high-sev alerts.✓ 已複製

→ Ranked summary
Investigate

For top agent, pull the 10 most recent high-sev alerts with full details.✓ 已複製

→ Detailed events
Determine action

Based on these events, is this a true positive? If yes, propose response: isolate agent / disable account / create ticket.✓ 已複製

→ Verdict + action plan

結果： Faster MTTD/MTTR without more eyeballs.

注意事項

Auto-triggering active response before confirming — Keep active response tools behind a confirmation gate

Weekly vulnerability posture report

👤 Security managers ⏱ ~30 min intermediate

何時使用： Friday report for leadership. How many CVEs open? Where? Trend vs last week?

步驟

Pull vulnerabilities

From Wazuh vulnerability module: total open CVEs by severity, top 10 agents by critical CVE count.✓ 已複製

→ Numbers + top agents
Compare to last week

Compare counts to last Friday's report [paste]. What improved, what regressed?✓ 已複製

→ Delta analysis
Prioritize

List the 5 critical CVEs affecting most hosts that should be patched this weekend.✓ 已複製

→ Actionable patch list

結果： Board-ready security posture summary.

注意事項

Vuln data only as fresh as last scan — Check scan timestamps before drawing conclusions

搭配使用： notion

Isolate a compromised host on confirmation

👤 SOC on-call ⏱ ~10 min advanced

何時使用： Alert fires: unambiguous malware on endpoint. You need to isolate fast.

步驟

Confirm scope

For agent 'ws-4412': show active processes with parent PID, recent listening ports, and last 20 alerts. Is this clearly compromised?✓ 已複製

→ Risk assessment
Isolate

Isolate agent ws-4412 via active response. Require my explicit confirm first.✓ 已複製

→ Confirmation prompt, then isolation + audit log entry

結果： Compromised host isolated within minutes.

注意事項

False-positive isolation of prod server — Double-check agent ID and classification before confirming; keep an out-of-band way to re-enable

組合

與其他 MCP 搭配，撬動十倍槓桿

wazuh + notion

Weekly security digest to exec

Compose a weekly Wazuh summary and create a Notion page in 'Security Weekly'.✓ 已複製

工具

此 MCP 暴露的能力

工具	輸入參數	何時呼叫	成本
list_alerts	filter: obj, from, to, limit	Investigate by time/severity/rule	1 API call
get_agent	agent_id	Profile a specific endpoint	1 API call
list_vulnerabilities	agent_id?, severity?	Vuln posture checks	1 API call
trigger_active_response	agent_id, command, arguments?	Isolate / kill process / disable account — destructive; confirm	1 API call + physical effect
compliance_report	framework: 'pci'\|'hipaa'\|'nist', scope	Audit readiness	1 API call

成本與限制

運行它的成本

API 配額: Bounded by Wazuh Manager API limits
每次呼叫 Token 數: Alert listings can be huge — always filter by time + severity
費用: Free. Wazuh itself is open-source.
提示: Use limit aggressively. Don't list a week's alerts without grouping.

安全

權限、密鑰、影響範圍

最小權限： Wazuh API user scoped read-only for inspection; elevate for active response

憑證儲存： Wazuh API creds in env or Docker secrets

資料出站： Alert/event data goes to your LLM provider

切勿授予： Active-response scope to a dev/eval instance

Active response tools cause real actions on endpoints. Gate behind human confirmation.
Alert payloads may contain sensitive info (filenames, users); consider Presidio-style redaction upstream.

故障排查

常見錯誤與修復

401 from Wazuh API

Creds wrong, or JWT expired. Server auto-rotates; if persistent, check ENV.

Empty alert list despite known alerts

Indexer (Elasticsearch) not reachable from MCP container. Check docker-compose networks.

Active response failed / no effect

Confirm the active-response script is enabled on that agent (ossec.conf). Some actions are agent-side only.

替代方案

Wazuh-MCP-Server 對比其他方案

替代方案	何時用它替代	權衡
Splunk / Sentinel MCPs	You use Splunk or Sentinel instead	Different SIEM
Wazuh UI directly	Single-alert deep dive	Slower; no LLM synthesis

Wazuh-MCP-Server

為什麼要用

核心特性

即時演示

實際使用效果

安裝

選擇你的客戶端

使用場景

實戰用法： Wazuh-MCP-Server

Triage overnight alerts in 10 minutes instead of 2 hours

前置條件

步驟

注意事項

Weekly vulnerability posture report

步驟

注意事項

Isolate a compromised host on confirmation

步驟

注意事項

組合

與其他 MCP 搭配，撬動十倍槓桿

工具

此 MCP 暴露的能力

成本與限制

運行它的成本

安全

權限、密鑰、影響範圍

故障排查

常見錯誤與修復

替代方案

Wazuh-MCP-Server 對比其他方案

更多

資源