mcp-server-wazuh
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@mcp-server-wazuhshow me recent high-severity vulnerability findings"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
mcp-server-wazuh
stdio MCP server for Wazuh 5. It reads the manager API on port 55000 (agents, groups, cluster, MITRE) and the indexer on port 9200 (events, findings, vulnerability state).
Wazuh 5 removed the 4.x manager paths /manager, /rules, /syscheck, /sca and /vulnerability. Existing public servers such as gbrigandi/mcp-server-wazuh still call those paths, so this package talks to the 5.0 API instead of forking them. Rule matches are findings in wazuh-findings-v5*, not wazuh-alerts-*.
Install
apt install mcp-server-wazuh
apt install mcprack-mcp-server-wazuhRelated MCP server: wazuh-mcp
Environment
Variable | Secret | Default | Meaning |
| no |
| Manager API base URL |
| yes | – | API user. Used once to obtain a JWT |
| yes | – | API password |
| no |
| Indexer base URL |
| yes | – | Indexer user |
| yes | – | Indexer password |
| no |
| Hide |
| no |
| Verify manager and indexer certificates |
| no |
| Seconds per request |
| no |
| Truncate larger tool output |
| no |
| Events data stream |
| no |
| Findings data stream |
| no |
| Vulnerability state index |
The JWT is refreshed in-process and is never printed. A 401 fetches a new token once.
Tools
Tool | Title | Annotation | Backend |
| API Info | read-only | manager |
| List Agents | read-only | manager |
| Get Agent | read-only | manager |
| Agents Summary | read-only | manager |
| List Groups | read-only | manager |
| Cluster Status | read-only | manager |
| List Cluster Nodes | read-only | manager |
| Search MITRE | read-only | manager |
| Search Events | read-only | indexer |
| Search Findings | read-only | indexer |
| Search Vulnerabilities | read-only | indexer |
| Restart Agents | destructive | manager, only when |
restart_agents interrupts agents. Ask before calling it. Wazuh 5 may reject the restart endpoint.
Development
PYTHONPATH=src python3 -m pytest
This server cannot be deployed
Maintenance
Related MCP Connectors
Read-only access to an ET Ducky organization's agents, alerts, and fleet summary
Read-only CVE intelligence, remediation playbooks, and agent setup guides. Not a scanner.
XFA's remote MCP server — query device posture, compliance, policies & CVEs. Read-only.
Read-only MCP access to a documented IT fleet: state, changes, posture. 15 tools.
Related MCP Servers
- AlicenseNot gradedqualityDmaintenanceEnables natural language interaction with Wazuh SIEM for alert querying, threat hunting, vulnerability scanning, and active response actions.MIT
- FlicenseAqualityCmaintenanceEnables querying a remote Wazuh deployment via MCP, covering Manager API (agents, rules, inventory, configuration) and Indexer (alerts, vulnerabilities) with 34 tools and reports, read-only by default.34-
- AlicenseNot gradedqualityCmaintenanceEnables AI assistants to converse in plain language with a Wazuh SIEM deployment, querying and aggregating alerts, hunting threats, triaging vulnerabilities, running compliance checks, and executing or rolling back active responses across multi-cluster environments. Works with both cloud and fully local, air-gapped LLM clients while enforcing scoped, audited access to the security tools.MIT
- AlicenseNot gradedqualityBmaintenanceExposes Wazuh SIEM data and actions—including agents, alerts, vulnerabilities, rules, decoders, active response, and Wazuh 5 Sigma rules, Detectors, and content promotion—as Model Context Protocol tools that LLM clients can call over HTTP.MIT