QRadar MCP Server
Bridges LLMs with IBM QRadar SIEM by providing access to over 728 REST API endpoints through four intelligent tool definitions. It enables security analysts to interact with offenses, assets, and rules using natural language while maintaining high token efficiency.
README
QRadar MCP Server
Model Context Protocol (MCP) server for IBM QRadar SIEM - Access 728+ QRadar REST API endpoints through just 4 intelligent MCP tools.
🎯 What is This?
QRadar MCP Server bridges the gap between Large Language Models (LLMs) and IBM QRadar SIEM. It enables natural language interactions with your security data—no need to memorize 728 API endpoints.
The Problem
- QRadar has 728+ REST API endpoints — overwhelming for developers and LLMs alike
- Traditional approach: Define each endpoint as a separate tool → massive token consumption
- Result: Expensive API calls, slow responses, context limits exceeded
The Solution
Instead of exposing 728 tools, we expose just 4 intelligent tools:
| Traditional Approach | MCP Server Approach |
|---|---|
| 728 tool definitions | 4 tool definitions |
| ~50,000 tokens/request | ~2,000 tokens/request |
| Context overflow risk | Fits any LLM context |
| Slow tool discovery | Instant endpoint lookup |
Token Efficiency
- 96% reduction in tool definition tokens
- 25x faster LLM processing
- Works with any LLM (Claude, GPT, Gemini, Llama)
Who Should Use This?
- Security analysts wanting natural language QRadar queries
- DevOps teams automating security workflows
- AI developers building QRadar-integrated applications
- SOC teams needing quick incident data access
🌐 Experience It Live
IBM MCP Client (Web UI)
Try the full experience with our React + FastAPI client:
Live Demo: http://9.30.147.112:8000 🚀
Container Registry: ghcr.io/addanuj/ibm-mcp-client:latest
Try: "Show me top 10 offenses", "How many assets?", "Get QRadar version", "List 5 rules"
🏗️ Architecture
graph TB
subgraph "Client Layer"
A[MCP Client/LLM]
end
subgraph "MCP Server Container"
B[Python FastAPI Server<br/>Port: 8001]
C[4 MCP Tools]
D[QRadar API Wrapper<br/>728 Endpoints]
end
subgraph "QRadar SIEM"
E[REST API<br/>v26.0+]
F[Offenses]
G[Assets]
H[Rules]
I[Ariel Search]
end
A -->|HTTP/SSE or stdio| B
B --> C
C --> D
D -->|HTTPS REST| E
E --> F
E --> G
E --> H
E --> I
style A fill:#e1f5ff
style B fill:#fff3e0
style C fill:#f3e5f5
style D fill:#e8f5e9
style E fill:#fce4ec
📦 What's Inside
4 Intelligent Tools
| Tool | Description | Example |
|---|---|---|
qradar_get |
Fetch data from 728 endpoints | Get offenses, assets, rules |
qradar_execute |
Create/update resources | Create reference sets, update rules |
qradar_delete |
Remove resources | Delete offense notes |
qradar_discover |
Auto-discover endpoints | Find correct API paths |
Supported Endpoints (728 total)
- SIEM: Offenses, sources, destinations
- Assets: Asset model, vulnerabilities, compliance
- Analytics: Rules, building blocks, searches
- Ariel: AQL queries, searches, results
- Reference Data: Sets, maps, collections
- Config: Domains, log sources, users
- System: Health, licensing, servers
🚀 Quick Start
Option 1: Pull Public Image from GitHub (Recommended)
No build required! Pull our pre-built multi-architecture image and run instantly.
Public Container Registry: ghcr.io/addanuj/qradar-mcp-server:latest
Step 1: Pull the image
docker pull ghcr.io/addanuj/qradar-mcp-server:latest
Step 2: Prepare your QRadar credentials
- QRadar Console URL:
https://your-qradar-console.com - API Token: Get from QRadar Console → Admin → Authorized Services
Step 3: Run the container
docker run -d \
--name qradar-mcp-server \
-p 8001:8001 \
-e QRADAR_HOST="https://your-qradar-console.com" \
-e QRADAR_API_TOKEN="your-sec-token-here" \
-e QRADAR_VERIFY_SSL="false" \
ghcr.io/addanuj/qradar-mcp-server:latest \
--host 0.0.0.0 --port 8001
Step 4: Verify it's running
# Check container status
docker ps | grep qradar-mcp-server
# Check health endpoint
curl http://localhost:8001/health
# Expected: {"status":"healthy","mode":"http","tools":4,"endpoints":728}
Supported Architectures:
- ✅ AMD64 (x86_64) - Intel/AMD processors
- ✅ ARM64 (aarch64) - Apple Silicon, AWS Graviton
Image Details:
- Registry: GitHub Container Registry (ghcr.io)
- Image:
ghcr.io/addanuj/qradar-mcp-server:latest - Public Access: No authentication needed
- Auto-updated: New commits trigger automatic builds
Option 2: Build from Source (Run as Container)
# Clone repository
git clone https://github.ibm.com/ashrivastava/QRadar-MCP-Server.git
cd QRadar-MCP-Server
# Build container image
docker build -t qradar-mcp-server:latest -f container/Dockerfile .
# Run as container
docker run -d \
--name qradar-mcp-server \
-p 8001:8001 \
-e QRADAR_HOST="https://your-qradar.com" \
-e QRADAR_API_TOKEN="token" \
qradar-mcp-server:latest \
--host 0.0.0.0 --port 8001
Option 3: Local Development (Run as Python Service)
# Install dependencies
pip install -e .
# Set environment variables
export QRADAR_HOST="https://your-qradar.com"
export QRADAR_API_TOKEN="your-token"
# Run in stdio mode (for Claude Desktop)
python -m src.server
# OR run in HTTP mode for local testing
python -m src.server --host 0.0.0.0 --port 8001
🔧 Configuration
Environment Variables
| Variable | Required | Default | Description |
|---|---|---|---|
QRADAR_HOST |
✅ Yes | - | Full QRadar console URL (https://...) |
QRADAR_API_TOKEN |
✅ Yes | - | QRadar API authorization token |
QRADAR_VERIFY_SSL |
❌ No | false |
Verify SSL certificates |
QRADAR_API_VERSION |
❌ No | 26.0 |
QRadar API version |
Runtime Modes
HTTP/SSE Mode (Recommended for Containers)
python -m src.server --host 0.0.0.0 --port 8001
- Exposes REST API on port 8001
- Health check:
http://localhost:8001/health - Tools list:
http://localhost:8001/tools - SSE streaming support
stdio Mode (for Claude Desktop)
python -m src.server
- Communicates via stdin/stdout
- Use in Claude Desktop MCP configuration
- No network exposure needed
Usage Examples
Check Server Health
curl http://localhost:8001/health
# Response: {"status":"healthy","mode":"http","tools":4,"endpoints":728}
List Available Tools
curl http://localhost:8001/tools
Call a Tool (Get Offenses)
curl -X POST http://localhost:8001/tools/call \
-H "Content-Type: application/json" \
-d '{
"name": "qradar_get",
"arguments": {
"endpoint": "/siem/offenses",
"limit": 10,
"qradar_host": "https://your-qradar.com",
"qradar_token": "your-token"
}
}'
Discover Endpoints
curl -X POST http://localhost:8001/tools/call \
-H "Content-Type: application/json" \
-d '{
"name": "qradar_discover",
"arguments": {
"search": "offenses",
"qradar_host": "https://your-qradar.com",
"qradar_token": "your-token"
}
}'
📁 Project Structure
QRadar-MCP-Server/
├── container/
│ └── Dockerfile # Multi-arch container definition
├── src/
│ ├── __init__.py
│ ├── __main__.py # Entry point
│ ├── server.py # FastAPI server (HTTP mode)
│ ├── client.py # QRadar API client wrapper
│ └── tools.py # 4 MCP tools with 728 endpoint definitions
└── pyproject.toml # Python package config
🚦 Supported QRadar Versions
- QRadar 7.3.x ✅ (tested)
- QRadar 7.4.x ✅ (tested)
- QRadar 7.5.x ✅ (tested)
📞 Support
Reporting Issues & Feature Requests
Found a bug?
- Go to: https://github.ibm.com/ashrivastava/QRadar-MCP-Server/issues
- Click "New Issue"
- Provide: clear title, steps to reproduce, QRadar version, and logs (
docker logs qradar-mcp-server)
Have a suggestion?
- Open issue with [Feature Request] prefix
- Describe use case and expected behavior
Need help?
- Check logs:
docker logs qradar-mcp-server - Search existing issues: https://github.ibm.com/ashrivastava/QRadar-MCP-Server/issues
- Contact: ashrivastava@ibm.com
⚠️ Disclaimer
This is a Minimum Viable Product (MVP) for testing and demonstration purposes only.
- NOT for production use
- No warranty or support guarantees
- Use at your own risk
- For production deployments, conduct thorough security review and testing
- IBM is not responsible for any issues arising from the use of this software
推荐服务器
Baidu Map
百度地图核心API现已全面兼容MCP协议,是国内首家兼容MCP协议的地图服务商。
Playwright MCP Server
一个模型上下文协议服务器,它使大型语言模型能够通过结构化的可访问性快照与网页进行交互,而无需视觉模型或屏幕截图。
Magic Component Platform (MCP)
一个由人工智能驱动的工具,可以从自然语言描述生成现代化的用户界面组件,并与流行的集成开发环境(IDE)集成,从而简化用户界面开发流程。
Audiense Insights MCP Server
通过模型上下文协议启用与 Audiense Insights 账户的交互,从而促进营销洞察和受众数据的提取和分析,包括人口统计信息、行为和影响者互动。
VeyraX
一个单一的 MCP 工具,连接你所有喜爱的工具:Gmail、日历以及其他 40 多个工具。
graphlit-mcp-server
模型上下文协议 (MCP) 服务器实现了 MCP 客户端与 Graphlit 服务之间的集成。 除了网络爬取之外,还可以将任何内容(从 Slack 到 Gmail 再到播客订阅源)导入到 Graphlit 项目中,然后从 MCP 客户端检索相关内容。
Kagi MCP Server
一个 MCP 服务器,集成了 Kagi 搜索功能和 Claude AI,使 Claude 能够在回答需要最新信息的问题时执行实时网络搜索。
e2b-mcp-server
使用 MCP 通过 e2b 运行代码。
Neon MCP Server
用于与 Neon 管理 API 和数据库交互的 MCP 服务器
Exa MCP Server
模型上下文协议(MCP)服务器允许像 Claude 这样的 AI 助手使用 Exa AI 搜索 API 进行网络搜索。这种设置允许 AI 模型以安全和受控的方式获取实时的网络信息。