Alertlogic Mcp

For incident responders: Query Alert Logic MDR incidents, elaborate raw log evidence, kick off SOAR playbooks, and search logs with SQL — all through Claude. Designed for MSSP-scale multi-account operations.

Table of Contents

• Overview
• Features
• Architecture
• Prerequisites
• Installation
• Configuration
• Claude Code Integration
• Claude Desktop Integration
• Module Overview
• SOC Quick Start
• Built-in SOC Playbooks
• Multi-Account MSSP Usage
• Security Notes
• Testing
• Troubleshooting
• Contributing
• License

Overview

This MCP server wraps the Alert Logic MDR platform API and exposes it as 473+ structured tools that any MCP-compatible AI client can call directly. It covers the full Alert Logic API surface — incident response, SQL-based log search, SOAR playbook automation, asset management, vulnerability analysis, user and credential management, billing, and more — organized into 46 domain modules. Auth, retries, pagination, token management, and JSON shaping are handled server-side; your AI client simply calls the tool by name.

Features

• Incident Response — List, get, elaborate (raw log evidence), complete, reopen, add notes, and add feedback to incidents. Friendly-ID lookup included.
• SQL Log Search — Submit Alert Logic log search queries in SQL, poll status, retrieve results, and release sessions.
• SOAR Playbook Automation — List, get, execute, and monitor SOAR playbooks; manage inquiries, triggers, and execution state.
• Asset Topology — Query the full asset inventory, declare and remove assets, set properties, and retrieve topology graphs for any deployment.
• Vulnerability Management — List exposures by severity, retrieve per-asset vulnerabilities, search the vulnerability knowledge base, and manage remediation items.
• User & Access Key Management — Full CRUD on users, roles, access keys, MFA settings, and password resets across accounts.
• Multi-Account MSSP Support — Per-tool account_id override and bulk cross-account operations (bulk deployments, bulk health checks, partner incidents).
• Built-in SOC Playbooks — Six tools that surface pre-written IR guides, threat-hunt workflows, MITRE ATT&CK mappings, and tool reference guides directly in-context.
• Tickets & Watchlist — Create, update, and close tickets; manage the alerting watchlist.
• Cloud & Azure Explorer — Browse cloud resource topology across AWS and Azure environments.
• Analytics Engine — Access AE content, rules, analytics, tags, tuning, and publication across multiple AE subsystems.
• Infrastructure Operations — Manage environments, scan schedules, scan results, network controls, ingest sources, and log integrations.

Architecture

+--------------------+      stdio / streamable-HTTP (MCP)     +--------------------------------+|   MCP Client       | <-------------------------------------> |   AlertLogic MCP Server        || (Claude Desktop,   |                                        |   (this repo, main.py)         ||  Claude Code, …)   |                                        |                                |+--------------------+                                        |  46 modules (~473 tools):      |                                                              |  incidents, soc, soar,         |                                                              |  assets, vuln, users, …        |                                                              |         |                      |                                                              |   base.py (HTTP, AIMS auth,    |                                                              |   token cache, retries)        |                                                              +----------+---------------------+                                                                         |                                                                         v  HTTPS + AIMS Bearer token                                                              +-----------------------------+                                                              |   AlertLogic MDR Platform   |                                                              |   api.cloudinsight....com   |                                                              +-----------------------------+

Transport: The server supports three MCP transports selectable via MCP_TRANSPORT:

• stdio (default) — launched on demand by your MCP client; no network port opened.
• streamable-http — persistent HTTP server; suitable for Claude Code and remote clients.
• sse — Server-Sent Events transport for SSE-capable clients.

Authentication: Alert Logic uses AIMS Bearer token auth. The server exchanges your access_key_id:secret_key API key for a short-lived Bearer token on first use, caches it, and re-authenticates automatically when the token expires — no manual token rotation required.

base.py centralizes HTTP method helpers (_get, _post, _put, _delete), per-service URL routing (Account-Topology service, global service, _at-prefixed routes), error translation, and the AIMS token cache.

Prerequisites

• Python 3.10 or newer
• uv (recommended) or pip
• An Alert Logic account with API access enabled
• An Alert Logic API key (access key ID + secret key; see Configuration)

Installation

# 1. Clone the repositorygit clone https://github.com/rijul170/alertlogic-mcp.gitcd alertlogic-mcp
# 2. Create a virtual environment and install dependenciespython -m venv .venvsource .venv/bin/activate          # Windows: .venv\Scripts\activatepip install -r requirements.txt
# Or with uv (faster):uv venvuv pip install -r requirements.txt
# 3. Configure credentialscp .env.example .env$EDITOR .env                        # fill in the required variables (see below)

Configuration

All configuration is via environment variables, loaded from .env at startup.

Required variables

Optional variables

Optional service URL overrides

These default to Alert Logic's standard endpoints. Override only if you have a custom deployment:

ALERTLOGIC_GLOBAL_BASE_URL=https://api.global-services.global.alertlogic.comALERTLOGIC_AETUNER_BASE_URL=https://aetuner.mdr.global.alertlogic.comALERTLOGIC_CONNECTORS_BASE_URL=https://connectors.mdr.global.alertlogic.comALERTLOGIC_RESPONDER_BASE_URL=https://api.responder.alertlogic.com

Creating an API key

1. Sign in to the Alert Logic console.
2. Navigate to Manage → Users, select your user, then open Access Keys → Create.
3. Copy the Access Key ID and Secret Key.
4. Combine them as access_key_id:secret_key (with the colon) and set that as ALERTLOGIC_API_KEY.

Claude Code Integration (HTTP mode)

Start the server in HTTP mode:

MCP_TRANSPORT=streamable-http python main.py

Then register it in your Claude Code project or user MCP config (.claude/settings.json or ~/.claude/settings.json):

{  "mcpServers": {    "alertlogic-mcp": {      "type": "http",      "url": "http://localhost:8000/mcp"    }  }}

Or via the CLI:

claude mcp add --transport http alertlogic-mcp http://localhost:8000/mcp

Claude Desktop Integration (stdio mode)

Edit claude_desktop_config.json:

• macOS: ~/Library/Application Support/Claude/claude_desktop_config.json
• Windows: %AppData%\Claude\claude_desktop_config.json

{  "mcpServers": {    "alertlogic-mcp": {      "command": "/absolute/path/to/.venv/bin/python",      "args": ["/absolute/path/to/alertlogic-mcp/main.py"]    }  }}

Use absolute paths. Tilde (~) is not expanded by Claude Desktop. Point command at the venv Python, not the system Python.

Restart Claude Desktop. Alert Logic tools will appear in the tool picker.

Module Overview

46 modules, ~473 tools, organized by domain:

Incident Response

Asset Management

SOAR

Vulnerabilities & Compliance

Users & Authentication

Infrastructure & Deployments

Analytics Engine

Ticketing & Watchlist

Operations & Platform

SOC Quick Start

Once connected, try these prompts in Claude:

Show me all open critical incidents from the last 24 hours

Get the elaborations (raw log evidence) for incident INC-12345

Search logs for SSH login failures from 10.0.0.5 in the last hour using SQL

Add a note to incident INC-12345: Confirmed malicious, escalating to customer

List all deployments and their health status across all accounts

Show me the top 10 critical vulnerabilities for host web-prod-01

Run the SOC IR playbook to walk me through incident response steps

Built-in SOC Playbooks

The soc_playbooks module provides six tools that surface curated, in-context operational guides — no external documentation lookups required:

These tools are designed to be called at the start of an investigation to load relevant context before querying live data.

Multi-Account MSSP Usage

The server is designed for MSSP environments where a single API key manages multiple child accounts:

Partner incident listing — incidents_list_partner returns incidents across all managed accounts in a single call, with account ownership labels.

Per-tool account override — Most tools accept an optional account_id parameter. Pass a child account's ID to scope any query to that account without changing your .env configuration:

Get all open incidents for account <child-account-id>

Bulk operations — bulk_list_deployments fans out a deployments query across all managed accounts and returns aggregated results. bulk_health_check does the same for health status.

Account topology — aims_get_account_topology and aims_list_accounts_by_relationship map the parent/child account hierarchy, useful for scoping operations before running them.

Tenant isolation: When working across multiple accounts, always confirm the target account before running write operations (containment, note-adding, ticket creation). The server does not enforce cross-tenant guards beyond what the Alert Logic API provides.

Security Notes

• Read-only mode: Set ALERTLOGIC_MCP_READONLY=true to register only read tools at startup. Write and destructive tools are never exposed to the AI client, regardless of what is asked.

• Destructive operation gating: Even with writes enabled, destructive tools (user/asset deletes, SOAR playbook execution, scan launches, key revocation, ...) are suppressed by default. Arm them explicitly via ALERTLOGIC_MCP_ALLOW_DESTRUCTIVE — the recommended approach is a comma-separated list of specific tool names rather than true:

  bash

  # Enable only incident completion workflow deletesALERTLOGIC_MCP_ALLOW_DESTRUCTIVE=user_delete,playbook_execute

• Every tool carries MCP readOnlyHint/destructiveHint annotations so compliant clients can apply their own confirmation policies.

• Never commit .env. It is excluded by .gitignore; only .env.example (with placeholders) is tracked.

• Treat ALERTLOGIC_API_KEY like a password. Rotate it immediately if you suspect exposure (chat logs, screen shares, lost device).

• AIMS token handling: The server exchanges your API key for a short-lived Bearer token on first use and caches it in memory. The token is refreshed automatically on expiry. The raw secret_key is not logged or transmitted after the initial AIMS authentication call.

• In stdio mode, the server opens no network port. In streamable-http or sse mode, bind to 127.0.0.1 (the default) unless you specifically need remote access, in which case add appropriate network controls.

• base.py does not log request bodies, response bodies, or credential material. If you fork and add logging, take care to exclude token and secret values.

• This repository ships no credentials of any kind.

Testing

A standalone smoke-test script exercises a representative cross-section of tools without going through an MCP client:

python smoke_test.py

This verifies credential validity, network reachability, and base configuration before wiring the server into your MCP client.

Troubleshooting

Contributing

PRs and issues are welcome.

1. Fork the repository, create a feature branch, commit your changes, and open a PR.
2. Add new Alert Logic endpoints as additional @server.tool definitions in the matching module file under modules/.
3. For a new module: create modules/<name>.py with a setup(server) function, then add it to the MODULES list in main.py.
4. Keep tool docstrings accurate and descriptive — the docstring is what the LLM sees when deciding whether and how to call the tool.
5. Run python smoke_test.py before submitting to verify basic functionality.

Related MCP Servers

These three servers cover complementary layers of a security stack — network/log (Alert Logic), endpoint protection (Sophos), and EDR/threat intel (CrowdStrike). Use them together for full-stack AI-powered SOC operations.

License

MIT License. See LICENSE for full text.