Bring Siem
to LangChain
Learn how to connect Wazuh (SIEM) to LangChain 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 LangChain?
LangChain's ecosystem of 500+ components combines seamlessly with Wazuh (SIEM) through native MCP adapters. Connect 21 tools via Vinkius and use ReAct agents, Plan-and-Execute strategies, or custom agent architectures. with LangSmith tracing giving full visibility into every tool call, latency, and token cost.
- —
The largest ecosystem of integrations, chains, and agents. combine Wazuh (SIEM) MCP tools with 500+ LangChain components
- —
Agent architecture supports ReAct, Plan-and-Execute, and custom strategies with full MCP tool access at every step
- —
LangSmith tracing gives you complete visibility into tool calls, latencies, and token usage for production debugging
- —
Memory and conversation persistence let agents maintain context across Wazuh (SIEM) queries for multi-turn workflows
Wazuh (SIEM) in LangChain
Wazuh (SIEM) and 4,000+ other MCP servers. One platform. One governance layer.
Teams that connect Wazuh (SIEM) to LangChain 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 LangChain
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 LangChain 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 LangChain
Every tool call from LangChain 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 LangChain connect to MCP servers?
Use langchain-mcp-adapters to create an MCP client. LangChain discovers all tools and wraps them as native LangChain tools compatible with any agent type.
Which LangChain agent types work with MCP?
All agent types including ReAct, OpenAI Functions, and custom agents work with MCP tools. The tools appear as standard LangChain tools after the adapter wraps them.
Can I trace MCP tool calls in LangSmith?
Yes. All MCP tool invocations appear as traced steps in LangSmith, showing input parameters, response payloads, latency, and token usage.
MultiServerMCPClient not found
Install: pip install langchain-mcp-adapters
Explore More MCP Servers
View all →
U.S. Treasury Full — Complete Fiscal & Debt Intelligence
13 toolsThe definitive U.S. Treasury Mega-Server: 13 tools covering national debt ($34T+), interest rates, auction results, federal budget accounting (revenue, spending, deficit), daily cash balances, and official exchange rates. Total access to the financial pulse of the U.S. government without API keys.
FreshBooks
12 toolsManage small business accounting via FreshBooks — track clients and invoices, handle payments and billing via AI agents.
Base64 & Binary Encoder
1 toolsStop corrupting file payloads. Safely encode and decode strings to Base64, Hex, or Base64URL local.
Mela
12 toolsTeam communication and project management.