Waf MCP Server

MCP server for ModSecurity WAF management — monitor, analyze, and configure OWASP CRS via AI assistants

Local serverstdioTypeScript

What is the Waf MCP MCP server?

MCP server for ModSecurity WAF management — monitor, analyze, and configure OWASP CRS via AI assistants. That is what the waf mcp mcp server brings to an AI assistant: the same capability, reachable through the Model Context Protocol rather than a separate app or dashboard.

The short version

An MCP (Model Context Protocol) server for managing OWASP ModSecurity CRS via Docker. Gives AI assistants like Claude direct access to WAF monitoring, analysis, and configuration through a structured drill-down pipeline.

The tools it exposes

The server publishes 1 tool. What each one is for:

  • Actions — The Actions tool exposed by this server

What it needs from you

Configuration is passed through the environment: WAF_COMPOSE_DIR, WAF_DOMAIN, IPINFO_TOKEN. Treat anything key-shaped as a real credential — scope it to the minimum the server needs, and rotate it if it ever lands in a shared config.

  • Docker with a running owasp/modsecurity-crs container - Docker Compose managing the ModSecurity container - Node.js 18+ - ModSecurity configured with JSON Serial audit log (SecAuditLogFormat JSON)

Getting it running

npm on npm is all you need. Most clients run it directly, so configuration is a few lines and a restart.

How it compares

This sits in the developer tooling group, where several servers overlap in what they claim to do but differ sharply once you actually set them up. Waf MCP's toolset — Actions — is a fair guide to whether it matches your workflow. It is maintained by kratosuae; worth a glance at recent repository activity before you build anything load-bearing on it.

We check each listing at SyncDev against the project's documentation before it goes live — if something here drifts out of date, it is a bug worth reporting.

Things to watch

  • It runs with your machine's permissions. That is convenient and also the reason to think about what you point it at before you approve a tool call.
  • Missing credentials fail quietly in some clients — if no tools show up, check the environment block first.
  • Keep per-call confirmation enabled while you learn its behaviour; it is the cheapest safeguard you have.

Available tools

ToolWhat it does
ActionsThe Actions tool exposed by this server.

How to install the Waf MCP MCP server

Or manually add to `~/.claude.json`:

```json
{
  "mcpServers": {
    "waf": {
      "type": "stdio",
      "command": "node",
      "args": ["/path/to/waf_mcp/dist/index.js"],
      "env": {
        "WAF_COMPOSE_DIR": "/path/to/your/compose/dir",
        "WAF_DOMAIN": "https://your-domain.com"
      }
    }
  }
}

Configuration as documented by the project. Restart the client after saving.

Configuration

  • Docker with a running owasp/modsecurity-crs container - Docker Compose managing the ModSecurity container - Node.js 18+ - ModSecurity configured with JSON Serial audit log (SecAuditLogFormat JSON)
VariableDescriptionRequired
WAF_COMPOSE_DIRFilesystem location the server is allowed to use.Optional
WAF_DOMAINConfiguration value read at startup.Optional
IPINFO_TOKENCredential the server authenticates with.Yes

Example prompts to try

  • Use Waf MCP to Actions.

Frequently asked questions

It connects Waf MCP to MCP-compatible AI assistants such as Claude and Cursor, exposing 1 tool (Actions) that the assistant can call on your behalf. Instead of copying data back and forth by hand, the assistant works with Waf MCP directly.