MCP server for Alert Logic MDR β incident response, log search, SOAR, and SOC workflows
Copy the AI prompt to install this server into Claude Code, Cursor, or another agent β or use 1-click editor setup below.
π‘ Paste the JSON block into your client's configuration file under mcpServers, then restart the application.
Bring the full Alert Logic MDR platform into your AI assistant.
A Model Context Protocol server that exposes the complete Alert Logic API surface as structured tools any MCP-compatible client (Claude Desktop, Claude Code, Cursor, β¦) can call directly β enabling AI-powered security operations, incident response, and threat hunting at MSSP scale.
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.
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.
account_id override and bulk cross-account operations (bulk deployments, bulk health checks, partner incidents).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.
uv (recommended) or pipAll configuration is via environment variables, loaded from .env at startup.
| Variable | Description |
|---|---|
ALERTLOGIC_API_KEY | API key in access_key_id:secret_key format (see below for how to create one) |
ALERTLOGIC_BASE_URL | API base URL β https://api.cloudinsight.alertlogic.com (US) or https://api.cloudinsight.alertlogic.co.uk (UK) |
ALERTLOGIC_ACCOUNT_ID | Your Alert Logic account ID (visible in the console URL and account settings) |
| Variable | Default | Description |
|---|---|---|
MCP_TRANSPORT | stdio | Transport: stdio, sse, or streamable-http |
MCP_HOST | 127.0.0.1 | Bind host (HTTP transports only) |
MCP_PORT | 8000 | Bind port (HTTP transports only) |
ALERTLOGIC_MCP_READONLY | (off) | Set to true to register only read tools β write and destructive tools are never exposed to the AI client |
ALERTLOGIC_MCP_ALLOW_DESTRUCTIVE | (off) | Destructive tools (deletes, SOAR playbook execution, scan launches, ...) are suppressed by default. Set to true to arm all of them, or a comma-separated list of tool names to arm selectively |
These default to Alert Logic's standard endpoints. Override only if you have a custom deployment:
No reviews yet β be the first to share how this listing worked for you.
Showcase your server listing on GitHub or your project documentation. Embed this dynamic SVG badge to highlight official listing status and live engagement.
[](https://allmcps.com/mcp/alertlogic-mcp)<a href="https://allmcps.com/mcp/alertlogic-mcp"><img src="https://allmcps.com/api/badge/alertlogic-mcp?style=directory" alt="Alertlogic MCP on AllMCPs" /></a>