Skip to main content
Glama
taegis-magic-mcp

taegis-magic-mcp

by DarkLicornor

taegis-magic-mcp

An MCP (Model Context Protocol) server that wraps taegis-magic — the Secureworks Taegis XDR CLI and SDK — so that AI assistants and agents can query alerts, events, investigations, threat intelligence, and tenants directly from their context window.

How it works

taegis-magic is the official open-source CLI and SDK for Secureworks Taegis XDR. It exposes subcommands like taegis alerts search, taegis investigations search, taegis events search, etc. via a rich Python SDK backed by the Taegis GraphQL API.

This server wraps those CLI commands behind the MCP tool protocol: an agent calls a tool (search_alerts, search_events, …), the server runs the appropriate taegis command as a subprocess, and returns the JSON output to the agent. No Taegis API knowledge is required on the agent side.

Agent / LLM
    │
    │  MCP tool call: search_alerts(query="...", region="charlie")
    ▼
taegis-magic-mcp  (this server)
    │
    │  subprocess: taegis alerts search --cell "..." --region charlie --limit 100
    ▼
taegis-magic CLI  ─────► Secureworks Taegis XDR API

Related MCP server: wazuh-mcp-server

Requirements

Requirement

Notes

Python ≥ 3.11

uv

Used to run the server in an isolated environment

taegis-magic

Must be installed and on PATH — pip install taegis-magic

Authentication

taegis-magic supports two authentication methods:

export TAEGIS_CLIENT_ID=<your-oauth-client-id>
export TAEGIS_CLIENT_SECRET=<your-oauth-client-secret>
export TAEGIS_ENVIRONMENT=<region>   # charlie | delta | us1 | us2 | eu

The MCP server forwards these as CLIENT_ID / CLIENT_SECRET to the taegis-sdk-python environment (the names the SDK reads). TAEGIS_CLIENT_ID / TAEGIS_CLIENT_SECRET are the namespaced forms used here to avoid collisions with other tools.

taegis auth login

The cached token is stored at ~/.taegis_sdk_python/config and reused automatically.

Available MCP tools

Tool

Description

search_alerts

Search Taegis alerts using OCSF query syntax

search_events

Search Taegis security events

search_investigations

List open security investigations

search_threat_intel

Search threat intelligence (IOCs, hashes, IPs, domains …)

list_tenants

List all tenants visible to the authenticated user

run_taegis_command

Escape hatch — run any taegis CLI subcommand and return JSON

All tools accept an optional region parameter (overrides TAEGIS_ENVIRONMENT).

Example queries

search_alerts(query="FROM alert EARLIEST=-1d WHERE severity='High'", region="charlie")
search_events(query="FROM event EARLIEST=-4h WHERE source_ip='10.0.0.1'")
search_threat_intel(query="evil.example.com")
run_taegis_command(args="rules search --region charlie --limit 10")

Installation

With opencode

Clone or add this repo as a submodule, then add to your opencode.jsonc:

"mcp": {
  "taegis": {
    "type": "local",
    "command": ["uv", "run", "--project", "/path/to/taegis-magic-mcp", "taegis-mcp"],
    "environment": {
      "TAEGIS_CLIENT_ID": "${TAEGIS_CLIENT_ID}",
      "TAEGIS_CLIENT_SECRET": "${TAEGIS_CLIENT_SECRET}",
      "TAEGIS_ENVIRONMENT": "${TAEGIS_ENVIRONMENT}"
    },
    "enabled": false
  }
}

Set "enabled": true (or toggle at runtime) when you want the Taegis tools in scope.

Standalone

git clone https://github.com/DarkLicornor/taegis-magic-mcp.git
cd taegis-magic-mcp
uv sync
uv run taegis-mcp

Development

git clone https://github.com/DarkLicornor/taegis-magic-mcp.git
cd taegis-magic-mcp
uv sync --extra dev
uv run taegis-mcp        # run the server
uv run pytest            # run tests
uv run ruff check .      # lint
uv run mypy src          # type-check

See also

License

MIT

Available Tools

6 tools
list_tenantsA

List all Taegis tenants visible to the authenticated user.

Returns: JSON array of tenant objects.

Inputs: no named parameters. Returns: result

run_taegis_commandA

Run an arbitrary taegis CLI command and return JSON output.

Use this as an escape hatch for commands not yet wrapped as dedicated tools (e.g. "rules search --region charlie").

Args: args: Space-separated CLI arguments after the taegis binary, e.g. "audits search --region charlie --limit 10".

Returns: Raw JSON output from the taegis CLI.

Inputs: args (required). Returns: result

search_alertsA

Search Taegis alerts using OCSF query syntax.

Args: query: OCSF query string, e.g. "FROM alert EARLIEST=-1d WHERE severity='High'" region: Taegis environment/region (charlie, delta, us1, us2, eu …). Defaults to the TAEGIS_ENVIRONMENT env var, then "charlie". limit: Maximum number of results to return (default 100, max 10 000).

Returns: JSON array of alert objects.

Inputs: query (required), limit, region. Returns: result

search_eventsA

Search Taegis security events.

Args: query: Event query string. region: Taegis environment/region. Defaults to TAEGIS_ENVIRONMENT or "charlie". limit: Maximum number of results (default 100).

Returns: JSON array of event objects.

Inputs: query (required), limit, region. Returns: result

search_investigationsA

List and search open security investigations in Taegis.

Args: region: Taegis environment/region. Defaults to TAEGIS_ENVIRONMENT or "charlie". limit: Maximum number of investigations to return (default 25).

Returns: JSON array of investigation objects.

Inputs: limit, region. Returns: result

search_threat_intelA

Search Taegis threat intelligence (IOCs, hashes, IPs, domains …).

Args: query: Search query — indicator value or free-text search. region: Taegis environment/region. Defaults to TAEGIS_ENVIRONMENT or "charlie".

Returns: JSON array of threat intelligence objects.

Inputs: query (required), region. Returns: result

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    TDQS

    A4.2/5.0

    Scored across 6 tools

    Disambiguation5/5

    Each tool targets a distinct resource type (alerts, events, investigations, tenants, threat intel) with clear search/list semantics. The escape hatch command is explicitly for arbitrary CLI calls, so there's no overlap with the dedicated tools.

    Naming Consistency5/5

    All tool names follow a consistent verb_noun snake_case pattern (search_alerts, list_tenants, run_taegis_command). The pattern is uniform across the set with no mixed conventions.

    Tool Count5/5

    Six tools is well within the ideal 3-15 range. The server covers the core Taegis search use cases without redundancy, and the escape hatch avoids the need for many narrow wrappers.

    Completeness4/5

    The dedicated tools cover the most common read/search operations for a security platform. Minor gaps exist (e.g., no dedicated get-by-id tools or investigation management), but the run_taegis_command escape hatch fills any missing functionality, making the surface effectively complete.

    Related MCP Connectors

    Related MCP Servers

    • A
      license
      Not graded
      quality
      C
      maintenance
      Universal MCP server that wraps any CLI tool, enabling AI assistants to run commands via natural language.
      1
      MIT
    • A
      license
      A
      quality
      B
      maintenance
      AI-powered MCP server that enables security analysts to query Wazuh SIEM/XDR for alert triage, threat hunting, compliance audits, and incident response through natural language prompts.
      28
      13
      MIT
    • F
      license
      Not graded
      quality
      D
      maintenance
      A robust MCP server that bridges AI development tools with Palo Alto Cortex platforms (XSOAR/XSIAM), enabling natural language-driven development, testing, and automation of security workflows.
      2
      -
    • A
      license
      Not graded
      quality
      B
      maintenance
      A modular, multi-transport Model Context Protocol server that connects AI assistants to the CrowdStrike Falcon platform. Query NG-SIEM logs, triage alerts, inspect endpoints, manage detection rules, and audit cloud security posture — all through natural language.
      14
      MIT