Bring Siem
to CrewAI
Learn how to connect Wazuh (SIEM) to CrewAI and start using 21 AI agent tools in minutes. Fully managed, enterprise secure, and ready to use without writing a single line of code.
GDPR Free for SubscribersCompatible with every major AI agent and IDE
Gemini
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 CrewAI?
When paired with CrewAI, Wazuh (SIEM) becomes a first-class tool in your multi-agent workflows. Each agent in the crew can call Wazuh (SIEM) tools autonomously, one agent queries data, another analyzes results, a third compiles reports, all orchestrated through Vinkius with zero configuration overhead.
- —
Multi-agent collaboration lets you decompose complex workflows into specialized roles, one agent researches, another analyzes, a third generates reports, each with access to MCP tools
- —
CrewAI's native MCP integration requires zero adapter code: pass Vinkius Edge URL directly in the
mcpsparameter and agents auto-discover every available tool at runtime - —
Built-in task delegation and shared memory mean agents can pass context between steps without manual state management, enabling multi-hop reasoning across tool calls
- —
Sequential and hierarchical crew patterns map naturally to real-world workflows: enumerate subdomains → analyze DNS history → check WHOIS records → compile findings into actionable reports
Wazuh (SIEM) in CrewAI
Wazuh (SIEM) and 4,000+ other MCP servers. One platform. One governance layer.
Teams that connect Wazuh (SIEM) to CrewAI 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 CrewAI
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 CrewAI 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 CrewAI
Every tool call from CrewAI 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 does CrewAI discover and connect to MCP tools?
CrewAI connects to MCP servers lazily. when the crew starts, each agent resolves its MCP URLs and fetches the tool catalog via the standard tools/list method. This means tools are always fresh and reflect the server's current capabilities. No tool schemas need to be hardcoded.
Can different agents in the same crew use different MCP servers?
Yes. Each agent has its own mcps list, so you can assign specific servers to specific roles. For example, a reconnaissance agent might use a domain intelligence server while an analysis agent uses a vulnerability database server.
What happens when an MCP tool call fails during a crew run?
CrewAI wraps tool failures as context for the agent. The LLM receives the error message and can decide to retry with different parameters, fall back to a different tool, or mark the task as partially complete. This resilience is critical for production workflows.
Can CrewAI agents call multiple MCP tools in parallel?
CrewAI agents execute tool calls sequentially within a single reasoning step. However, you can run multiple agents in parallel using process=Process.parallel, each calling different MCP tools concurrently. This is ideal for workflows where separate data sources need to be queried simultaneously.
Can I run CrewAI crews on a schedule (cron)?
Yes. CrewAI crews are standard Python scripts, so you can invoke them via cron, Airflow, Celery, or any task scheduler. The crew.kickoff() method runs synchronously by default, making it straightforward to integrate into existing pipelines.
MCP tools not discovered
Ensure the Edge URL is correct. CrewAI connects lazily when the crew starts. check console output.
Agent not using tools
Make the task description specific. Instead of "do something", say "Use the available tools to list contacts".
Timeout errors
CrewAI has a 10s connection timeout by default. Ensure your network can reach the Edge URL.
Rate limiting or 429 errors
Vinkius enforces per-token rate limits. Check your subscription tier and request quota in the dashboard. Upgrade if you need higher throughput.
Explore More MCP Servers
View all →
WorkflowMax
12 toolsManage jobs, clients, and timesheets via WorkflowMax by BlueRock directly from your AI agent.
DeepL
14 toolsTranslate text between 30+ languages with neural machine translation that captures nuance and tone better than generic engines.
ArcGIS Alternative
6 toolsAccess GIS services via ArcGIS — geocode addresses, search places, get routes, check elevation and discover basemap styles from any AI agent.
Twilio SendGrid
10 toolsEquip your AI agent with capabilities to natively dispatch HTML emails, prune suppression bounce lists, and manage marketing contacts via the SendGrid API.