4,000+ servers built on vurb.ts
Vinkius
LlamaIndexFramework
LlamaIndex
Wazuh (SIEM) MCP Server

Bring Siem
to LlamaIndex

Learn how to connect Wazuh (SIEM) to LlamaIndex and start using 21 AI agent tools in minutes. Fully managed, enterprise secure, and ready to use without writing a single line of code.

MCP Inspector GDPR Free for Subscribers
Create AgentCreate Security RoleDelete AgentsGet LogtestGet Manager LogsGet Manager StatusGet MitreGet RootcheckGet ScaGet SyscheckGet SyscollectorList AgentsList Cluster NodesList DecodersList RulesList Security UsersRestart AgentsRestart ClusterUpdate Rule FileUpdate Security ConfigUpgrade Agents

Compatible with every major AI agent and IDE

ClaudeClaude
ChatGPTChatGPT
CursorCursor
GeminiGemini
WindsurfWindsurf
VS CodeVS Code
JetBrainsJetBrains
VercelVercel
+ other MCP clients
Wazuh (SIEM)

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

  1. Subscribe to this server
  2. Provide your Wazuh API URL, Username, and Password
  3. 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)

create_agent

Enroll a new Wazuh agent

create_security_role

Create a new Wazuh security role

delete_agents

Use WQL to specify which agents to delete. Remove Wazuh agents

get_logtest

Test rules and decoders against logs

get_manager_logs

Retrieve Wazuh manager logs

get_manager_status

Get Wazuh manager daemon status

get_mitre

Supports WQL filtering. Get MITRE ATT&CK results

get_rootcheck

Supports WQL filtering. Get Rootcheck results

get_sca

Supports WQL filtering. Get Security Configuration Assessment (SCA) results

get_syscheck

Supports WQL filtering. Get File Integrity Monitoring (Syscheck) results

get_syscollector

Supports WQL filtering. Get Syscollector inventory

list_agents

Supports WQL filtering. List all Wazuh agents

list_cluster_nodes

List Wazuh cluster nodes

list_decoders

Supports WQL filtering. List loaded Wazuh decoders

list_rules

Supports WQL filtering. List loaded Wazuh rules

list_security_users

List Wazuh API users

restart_agents

Restart Wazuh agents

restart_cluster

Restart the Wazuh cluster

update_rule_file

Update a Wazuh rule file

update_security_config

Update Wazuh security configuration

upgrade_agents

Upgrade Wazuh agents

Why LlamaIndex?

LlamaIndex agents combine Wazuh (SIEM) tool responses with indexed documents for comprehensive, grounded answers. Connect 21 tools through Vinkius and query live data alongside vector stores and SQL databases in a single turn. ideal for hybrid search, data enrichment, and analytical workflows.

  • Data-first architecture: LlamaIndex agents combine Wazuh (SIEM) tool responses with indexed documents for comprehensive, grounded answers

  • Query pipeline framework lets you chain Wazuh (SIEM) tool calls with transformations, filters, and re-rankers in a typed pipeline

  • Multi-source reasoning: agents can query Wazuh (SIEM), a vector store, and a SQL database in a single turn and synthesize results

  • Observability integrations show exactly what Wazuh (SIEM) tools were called, what data was returned, and how it influenced the final answer

L
See it in action

Wazuh (SIEM) in LlamaIndex

AI AgentVinkius
High Security·Kill Switch·Plug and Play
Why Vinkius

Wazuh (SIEM) and 4,000+ other MCP servers. One platform. One governance layer.

Teams that connect Wazuh (SIEM) to LlamaIndex 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.

4,000+MCP Servers ready
<40msCold start
60%Token savings
Raw MCP
Vinkius
Server catalogFind and host yourself4,000+ managed
InfrastructureSelf-hostedSandboxed V8 isolates
Credential handlingPlaintext in configVault + runtime injection
Data loss preventionNoneConfigurable DLP policies
Kill switchNoneGlobal instant shutdown
Financial circuit breakersNonePer-server limits + alerts
Audit trailNoneEd25519 signed logs
SIEM log streamingNoneSplunk, Datadog, Webhook
HoneytokensNoneCanary alerts on leak
Custom domainsNot applicableDNS challenge verified
GDPR complianceManual effortAutomated purge + export
Enterprise Security

Why teams choose Vinkius for Wazuh (SIEM) in LlamaIndex

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 LlamaIndex 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.

Wazuh (SIEM)
Fully ManagedVinkius Servers
60%Token savings
High SecurityEnterprise-grade
IAMAccess control
EU AI ActCompliant
DLPData protection
V8 IsolateSandboxed
Ed25519Audit chain
<40msKill switch
Stream every event to Splunk, Datadog, or your own webhook in real-time

* 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

The Vinkius Advantage

How Vinkius secures Wazuh (SIEM) for LlamaIndex

Every tool call from LlamaIndex to the Wazuh (SIEM) MCP Server is protected by DLP redaction, cryptographic audit chains, V8 sandbox isolation, kill switch, and financial circuit breakers.

< 40msCold start
Ed25519Signed audit chain
60%Token savings
FAQ

Frequently asked questions

01

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.

02

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.

03

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.

04

How does LlamaIndex connect to MCP servers?

Use the MCP client adapter to create a connection. LlamaIndex discovers all tools and wraps them as query engine tools compatible with any LlamaIndex agent.

05

Can I combine MCP tools with vector stores?

Yes. LlamaIndex agents can query Wazuh (SIEM) tools and vector store indexes in the same turn, combining real-time and embedded data for grounded responses.

06

Does LlamaIndex support async MCP calls?

Yes. LlamaIndex's async agent framework supports concurrent MCP tool calls for high-throughput data processing pipelines.

07

BasicMCPClient not found

Install: pip install llama-index-tools-mcp

Explore More MCP Servers

View all →