DETECTION ENGINEERING / Timescale
RSigma MCP
Exposes Sigma rule parsing, linting, evaluation and conversion, with separately enabled incident-triage and operational-write tools.
“Exposes the toolchain to AI agents (Cursor, Claude Code, ...) as structured MCP tools over stdio or Streamable HTTP with rsigma mcp serve”
01 / THE REASONING
Why this made the selection.
- Supports a concrete rule-authoring loop with structured parse, lint and evaluation results.
- Daemon read tools and operational writes require separate configuration, making their scope explicit.
02 / THE REVIEW RECORD
What we actually inspected.
Source review has boundaries.
A clear record is more useful than a “safe” badge.
Material inspected
- README.md at bd6741886c4924fb99ebcade1ae2b0b54079cecc (MCP server section, installation)
- Cargo.toml, crates/rsigma-cli/Cargo.toml and crates/rsigma-mcp/Cargo.toml at bd6741886c4924fb99ebcade1ae2b0b54079cecc
- crates/rsigma-mcp/src/lib.rs, crates/rsigma-mcp/src/tools.rs and crates/rsigma-mcp/src/tools/fix_rules.rs at bd6741886c4924fb99ebcade1ae2b0b54079cecc
- crates/rsigma-cli/src/commands/mcp.rs at bd6741886c4924fb99ebcade1ae2b0b54079cecc
- LICENSE at bd6741886c4924fb99ebcade1ae2b0b54079cecc
- RSigma MCP server guide (rsigma.io/guide/mcp-server/), read 2026-10-13: feature/build, client setup, tool reference, Operate-cycle flags, HTTP authentication and TLS
Our findings
- The guide identifies the opt-in mcp feature and states prebuilt binaries include it; the CLI defines stdio and optional Streamable HTTP mounted at /mcp.
- Daemon writes require --allow-operate-writes; HTTP bearer authentication (--auth-token or RSIGMA_MCP_AUTH_TOKEN) and TLS are configured separately.
- Content failures may arrive as successful MCP responses containing ok:false, which a client must inspect.
- crates/rsigma-cli/Cargo.toml at the pin, and the crates.io metadata for 0.24.0, define the mcp feature as enabling rsigma-mcp with its http feature.
- The guide lists 15 Engineer-cycle tools that always register (parse_rule, parse_condition, lint_rules, validate_rules, evaluate_events, convert_rules, reverse_convert, list_backends, list_fields, resolve_pipeline, list_builtin_pipelines, fix_rules, author_ads, tune_rules, test_exemplars), six Operate-cycle read tools with --daemon-url, and two write tools (create_silence, post_disposition) with --allow-operate-writes.
- configExample is the guide's Cursor block, read 2026-10-13.
- Correction: this page's earlier command, cargo install --locked rsigma --features mcp, was composed; neither the README nor the guide gives it as one line. The README's launch line rsigma mcp serve --rules-dir rules/ is shown now.
- Re-pinned from 7cadc4aa617a938d0664a0a3f02121b295cd52c6 to bd6741886c4924fb99ebcade1ae2b0b54079cecc; the upstreamDescription now quotes the README's MCP server line instead of its two-word link text.
Not established by this review
- Server startup, authentication and tool execution were not tested.
The review applies to the material and revision named here. A newer upstream release can change its behavior.
03 / PUT IT TO WORK
Connect a server deliberately.
DOCUMENTED COMMAND
rsigma mcp serve --rules-dir rules/ Copying does not execute this command. It may retrieve a newer version than the reviewed source.
- Get an MCP-enabled build: a prebuilt release binary or the Docker image, which the guide says include it, or a source build with --features mcp. The README's cargo install --locked rsigma line alone does not enable it.
- The command above is the README's launch line; register it in the client (the configExample is the guide's Cursor entry). It was not run.
- Add --daemon-url, and --allow-operate-writes, only when daemon access and writes are required.
Before you start
- A Rust toolchain for the source-build command, or a documented prebuilt binary; Sigma rules/event samples.
Documented configuration example
Use the client and authentication context described in the setup guidance. Configuration formats vary between hosts.
{
"mcpServers": {
"rsigma": {
"command": "rsigma",
"args": [
"mcp",
"serve",
"--rules-dir",
"/path/to/rules"
]
}
}
} 04 / FOLLOW THE EVIDENCE
The source trail.
Our notes are separate from the original resource.
Check upstream before adopting a new version.
- Official documentation ↗Checked
https://github.com/timescale/rsigma/blob/bd6741886c4924fb99ebcade1ae2b0b54079cecc/README.md
Supports: summary, whySelected, bestFor, limitations, install, access, compatibility, transports, upstreamDescription
- Applicable source licence ↗Checked
https://github.com/timescale/rsigma/blob/bd6741886c4924fb99ebcade1ae2b0b54079cecc/LICENSE
Supports: license
- Implementation: Cargo.toml ↗Checked
https://github.com/timescale/rsigma/blob/bd6741886c4924fb99ebcade1ae2b0b54079cecc/Cargo.toml
Supports: language, review
https://github.com/timescale/rsigma/blob/bd6741886c4924fb99ebcade1ae2b0b54079cecc/crates/rsigma-mcp/Cargo.toml
Supports: language, review
https://github.com/timescale/rsigma/blob/bd6741886c4924fb99ebcade1ae2b0b54079cecc/crates/rsigma-mcp/src/lib.rs
Supports: language, review
https://github.com/timescale/rsigma/blob/bd6741886c4924fb99ebcade1ae2b0b54079cecc/crates/rsigma-mcp/src/tools.rs
Supports: language, review
https://github.com/timescale/rsigma/blob/bd6741886c4924fb99ebcade1ae2b0b54079cecc/crates/rsigma-cli/src/commands/mcp.rs
Supports: language, review
- RSigma MCP guide ↗Checked
https://rsigma.io/guide/mcp-server/
Supports: install, review, limitations, access, transports, configExample
https://crates.io/api/v1/crates/rsigma
Supports: install, review, transports
https://github.com/timescale/rsigma/blob/bd6741886c4924fb99ebcade1ae2b0b54079cecc/crates/rsigma-cli/Cargo.toml
Supports: install, review, limitations
https://github.com/timescale/rsigma/blob/bd6741886c4924fb99ebcade1ae2b0b54079cecc/crates/rsigma-mcp/src/tools/fix_rules.rs
Supports: limitations, access