4,000+ servers built on vurb.ts
Vinkius

Wazuh (SIEM) MCP Server for CursorGive Cursor instant access to 21 tools to Create Agent, Create Security Role, Delete Agents, and more

MCP Inspector GDPR Free for Subscribers

Cursor is an AI-first code editor built on VS Code that integrates LLM-powered coding assistance directly into the development workflow. Its Agent mode enables autonomous multi-step coding tasks, and MCP support lets agents access external data sources and APIs during code generation.

Ask AI about this MCP Server for Cursor

The Wazuh (SIEM) MCP Server for Cursor is a standout in the Fort Knox category — giving your AI agent 21 tools to work with, ready to go from day one.

Built for AI Agents by Vinkius

Vinkius delivers Streamable HTTP and SSE to any MCP client

ClaudeClaude
ChatGPTChatGPT
CursorCursor
GeminiGemini
WindsurfWindsurf
VS CodeVS Code
JetBrainsJetBrains
VercelVercel
+ other MCP clients
Classic Setup·json
{
  "mcpServers": {
    "wazuh-siem": {
      "url": "https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp"
    }
  }
}
RecommendedModern Approach — Zero Configuration

Vinkius Desktop App

The modern way to manage MCP Servers — no config files, no terminal commands. Install Wazuh (SIEM) and 4,000+ MCP Servers from a single visual interface.

Vinkius Desktop InterfaceVinkius Desktop InterfaceVinkius Desktop InterfaceVinkius Desktop Interface
Download Free Open SourceNo signup required
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

About Wazuh (SIEM) MCP Server

Connect your Wazuh SIEM to any AI agent to streamline security operations and endpoint monitoring through natural language.

Cursor's Agent mode turns Wazuh (SIEM) into an in-editor superpower. Ask Cursor to generate code using live data from Wazuh (SIEM) and it fetches, processes, and writes. all in a single agentic loop. 21 tools appear alongside file editing and terminal access, creating a unified development environment grounded in real-time information.

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.

The Wazuh (SIEM) MCP Server exposes 21 tools through the Vinkius. Connect it to Cursor in under two minutes — credentials fully managed, no infrastructure to provision, no vendor lock-in. Your configuration, your data, your control.

All 21 Wazuh (SIEM) tools available for Cursor

When Cursor connects to Wazuh (SIEM) through Vinkius, your AI agent gets direct access to every tool listed below — spanning siem, threat-detection, vulnerability-management, and more. Every call runs in a secure, isolated environment with full audit visibility. Beyond a simple connection, you get real-time monitoring of agent activity, enterprise governance, and optimized token usage.

create

Create agent on Wazuh (SIEM)

Enroll a new Wazuh agent

create

Create security role on Wazuh (SIEM)

Create a new Wazuh security role

delete

Delete agents on Wazuh (SIEM)

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

get

Get logtest on Wazuh (SIEM)

Test rules and decoders against logs

get

Get manager logs on Wazuh (SIEM)

Retrieve Wazuh manager logs

get

Get manager status on Wazuh (SIEM)

Get Wazuh manager daemon status

get

Get mitre on Wazuh (SIEM)

Supports WQL filtering. Get MITRE ATT&CK results

get

Get rootcheck on Wazuh (SIEM)

Supports WQL filtering. Get Rootcheck results

get

Get sca on Wazuh (SIEM)

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

get

Get syscheck on Wazuh (SIEM)

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

get

Get syscollector on Wazuh (SIEM)

Supports WQL filtering. Get Syscollector inventory

list

List agents on Wazuh (SIEM)

Supports WQL filtering. List all Wazuh agents

list

List cluster nodes on Wazuh (SIEM)

List Wazuh cluster nodes

list

List decoders on Wazuh (SIEM)

Supports WQL filtering. List loaded Wazuh decoders

list

List rules on Wazuh (SIEM)

Supports WQL filtering. List loaded Wazuh rules

list

List security users on Wazuh (SIEM)

List Wazuh API users

restart

Restart agents on Wazuh (SIEM)

Restart Wazuh agents

restart

Restart cluster on Wazuh (SIEM)

Restart the Wazuh cluster

update

Update rule file on Wazuh (SIEM)

Update a Wazuh rule file

update

Update security config on Wazuh (SIEM)

Update Wazuh security configuration

upgrade

Upgrade agents on Wazuh (SIEM)

Upgrade Wazuh agents

Connect Wazuh (SIEM) to Cursor via MCP

Follow these steps to wire Wazuh (SIEM) into Cursor. The entire setup takes under two minutes — your credentials stay safe behind Vinkius.

01

Open MCP Settings

Press Cmd+Shift+P (macOS) or Ctrl+Shift+P (Windows/Linux) → search "MCP Settings"
02

Add the server config

Paste the JSON configuration above into the mcp.json file that opens
03

Save the file

Cursor will automatically detect the new MCP server
04

Start using Wazuh (SIEM)

Open Agent mode in chat and ask: "Using Wazuh (SIEM), help me...". 21 tools available

Why Use Cursor with the Wazuh (SIEM) MCP Server

Cursor AI Code Editor provides unique advantages when paired with Wazuh (SIEM) through the Model Context Protocol.

01

Agent mode turns Cursor into an autonomous coding assistant that can read files, run commands, and call MCP tools without switching context

02

Cursor's Composer feature can generate entire files using real-time data fetched through MCP. no copy-pasting from external dashboards

03

MCP tools appear alongside built-in tools like file reading and terminal access, creating a unified agentic environment

04

VS Code extension compatibility means your existing workflow, keybindings, and extensions all work alongside MCP tools

Wazuh (SIEM) + Cursor Use Cases

Practical scenarios where Cursor combined with the Wazuh (SIEM) MCP Server delivers measurable value.

01

Code generation with live data: ask Cursor to generate a security report module using live DNS and subdomain data fetched through MCP

02

Automated documentation: have Cursor query your API's tool schemas and generate TypeScript interfaces or OpenAPI specs automatically

03

Infrastructure-as-code: Cursor can fetch domain configurations and generate corresponding Terraform or CloudFormation templates

04

Test scaffolding: ask Cursor to pull real API responses via MCP and generate unit test fixtures from actual data

Example Prompts for Wazuh (SIEM) in Cursor

Ready-to-use prompts you can give your Cursor agent to start working with Wazuh (SIEM) immediately.

01

"List all Wazuh agents that are currently active."

02

"Show me the latest Security Configuration Assessment (SCA) results."

03

"Check the Wazuh manager logs for any recent errors."

Troubleshooting Wazuh (SIEM) MCP Server with Cursor

Common issues when connecting Wazuh (SIEM) to Cursor through Vinkius, and how to resolve them.

01

Tools not appearing in Cursor

Ensure you are in Agent mode (not Ask mode). MCP tools only work in Agent mode.
02

Server shows as disconnected

Check Settings → Features → MCP and verify the server status. Try clicking the refresh button.

Wazuh (SIEM) + Cursor FAQ

Common questions about integrating Wazuh (SIEM) MCP Server with Cursor.

01

What is Agent mode and why does it matter for MCP?

Agent mode is Cursor's autonomous execution mode where the AI can perform multi-step tasks: reading files, editing code, running terminal commands, and calling MCP tools. Without Agent mode, Cursor operates in a simpler ask-and-answer mode that doesn't support tool calling. Always ensure you're in Agent mode when working with MCP servers.
02

Where does Cursor store MCP configuration?

Cursor looks for MCP server configurations in a mcp.json file. You can configure servers at the project level (.cursor/mcp.json in your project root) or globally (~/.cursor/mcp.json). Project-level configs take precedence.
03

Can Cursor use MCP tools in inline edits?

No. MCP tools are only available in Agent mode through the chat panel. Inline completions and Tab suggestions do not trigger MCP tool calls. This is by design. tool calls require user visibility and approval.
04

How do I verify MCP tools are loaded?

Open Settings → Features → MCP and look for your server name. A green indicator means the server is connected. You can also check Agent mode's available tools by clicking the tools dropdown in the chat panel.

Explore More MCP Servers

View all →