Compatible with every major AI agent and IDE
What is the Wazuh (SIEM) MCP Server?
Connect your Wazuh SIEM to any AI agent to streamline security operations and endpoint monitoring through natural language.
What you can do
- Agent Management — List all enrolled agents, create new ones, and perform bulk actions like restarts or upgrades using WQL filtering.
- Manager & Cluster Health — Monitor manager daemon status, fetch logs, and inspect cluster nodes to ensure high availability.
- Security Auditing — Query File Integrity Monitoring (Syscheck), Security Configuration Assessment (SCA), and Rootcheck results.
- Threat Intelligence — Access MITRE ATT&CK mappings and test log decoders to validate your detection pipeline.
- Rule Orchestration — List and update rules or decoders directly to fine-tune your security posture.
How it works
- Subscribe to this server
- Provide your Wazuh API URL, Username, and Password
- Start auditing your security environment from Claude, Cursor, or any MCP client
Who is this for?
- Security Analysts — quickly query agent status and FIM results without navigating the Wazuh dashboard
- DevSecOps Engineers — automate agent upgrades and monitor cluster health directly from terminal-based AI tools
- Incident Responders — fetch MITRE mappings and manager logs instantly during active investigations
Built-in capabilities (21)
Enroll a new Wazuh agent
Create a new Wazuh security role
Use WQL to specify which agents to delete. Remove Wazuh agents
Test rules and decoders against logs
Retrieve Wazuh manager logs
Get Wazuh manager daemon status
Supports WQL filtering. Get MITRE ATT&CK results
Supports WQL filtering. Get Rootcheck results
Supports WQL filtering. Get Security Configuration Assessment (SCA) results
Supports WQL filtering. Get File Integrity Monitoring (Syscheck) results
Supports WQL filtering. Get Syscollector inventory
Supports WQL filtering. List all Wazuh agents
List Wazuh cluster nodes
Supports WQL filtering. List loaded Wazuh decoders
Supports WQL filtering. List loaded Wazuh rules
List Wazuh API users
Restart Wazuh agents
Restart the Wazuh cluster
Update a Wazuh rule file
Update Wazuh security configuration
Upgrade Wazuh agents
Why Claude Code?
Claude Code registers Wazuh (SIEM) as an MCP server in a single terminal command. Once connected, Claude Code discovers all 21 tools at runtime and can call them headlessly. ideal for CI/CD pipelines, cron jobs, and automated workflows where Wazuh (SIEM) data drives decisions without human intervention.
- —
Single-command setup:
claude mcp addregisters the server instantly. no config files to edit or applications to restart - —
Terminal-native workflow means MCP tools integrate seamlessly into shell scripts, CI/CD pipelines, and automated DevOps tasks
- —
Claude Code runs headlessly, enabling unattended batch processing using Wazuh (SIEM) tools in cron jobs or deployment scripts
- —
Built by the same team that created the MCP protocol, ensuring first-class compatibility and the fastest adoption of new protocol features
Wazuh (SIEM) in Claude Code
Wazuh (SIEM) and 4,000+ other MCP servers. One platform. One governance layer.
Teams that connect Wazuh (SIEM) to Claude Code through Vinkius don't need to source, host, or maintain individual MCP servers. Every tool call runs inside a hardened runtime with credential isolation, DLP, and a signed audit chain.
Raw MCP | Vinkius | |
|---|---|---|
| Server catalog | Find and host yourself | 4,000+ managed |
| Infrastructure | Self-hosted | Sandboxed V8 isolates |
| Credential handling | Plaintext in config | Vault + runtime injection |
| Data loss prevention | None | Configurable DLP policies |
| Kill switch | None | Global instant shutdown |
| Financial circuit breakers | None | Per-server limits + alerts |
| Audit trail | None | Ed25519 signed logs |
| SIEM log streaming | None | Splunk, Datadog, Webhook |
| Honeytokens | None | Canary alerts on leak |
| Custom domains | Not applicable | DNS challenge verified |
| GDPR compliance | Manual effort | Automated purge + export |
Why teams choose Vinkius for Wazuh (SIEM) in Claude Code
The Wazuh (SIEM) MCP Server runs on Vinkius-managed infrastructure inside AWS — a purpose-built runtime with per-request V8 isolates, Ed25519 signed audit chains, and sub-40ms cold starts. All 21 tools execute in hardened sandboxes optimized for native MCP execution.
Your AI agents in Claude Code only access the data you authorize, with DLP that blocks sensitive information from ever reaching the model, kill switch for instant shutdown, and up to 60% token savings. Enterprise-grade infrastructure, zero maintenance.

* Every MCP server runs on Vinkius-managed infrastructure inside AWS - a purpose-built runtime with per-request V8 isolates, Ed25519 signed audit chains, and sub-40ms cold starts optimized for native MCP execution. See our infrastructure
How Vinkius secures
Wazuh (SIEM) for Claude Code
Every tool call from Claude Code to the Wazuh (SIEM) MCP Server is protected by DLP redaction, cryptographic audit chains, V8 sandbox isolation, kill switch, and financial circuit breakers.
Frequently asked questions
Can I filter agents by specific operating systems or versions?
Yes! The list_agents tool supports WQL (Wazuh Query Language). You can use queries like os.name=ubuntu;os.version>18 to find specific endpoints.
How do I check for unauthorized file changes on my servers?
You can use the get_syscheck tool. It retrieves File Integrity Monitoring (FIM) results, allowing you to audit file modifications, deletions, or additions across your agents.
Is it possible to check the health of the Wazuh manager cluster?
Absolutely. Use get_manager_status to check daemon health or list_cluster_nodes to see the status of all nodes in your Wazuh cluster.
How do I add an MCP server to Claude Code?
Run claude mcp add <name> --transport http "<url>" in your terminal. Claude Code registers the server and discovers all tools immediately.
Can Claude Code run MCP tools in headless mode?
Yes. Claude Code supports non-interactive execution, making it ideal for scripts, cron jobs, and CI/CD pipelines that need MCP tool access.
How do I list all connected MCP servers?
Run claude mcp in your terminal to see all registered servers and their status, or type /mcp inside an active Claude Code session.
Command not found: claude
Ensure Claude Code is installed globally: npm install -g @anthropic-ai/claude-code
Connection timeout
Check your internet connection and verify the Edge URL is reachable
Explore More MCP Servers
View all →
Project Gutenberg
3 toolsUniversal public domain library — search and retrieve thousands of free books via AI.

Storybook
6 toolsConnect your AI to Storybook. Explore your design system, inspect UI components, and retrieve implementation guidance programmatically.

New York Times
9 toolsAccess top stories, article search, best-seller lists, and movie reviews via the NYTimes API.

Moody's
8 toolsCredit ratings and risk analysis — access issuer ratings, issue details, and rating actions via Moody's.
