MCP server for Check Point Avanan (Harmony Email & Collaboration) — security event management and MSP multi-tenant operations
概览
A Model Context Protocol (MCP) server for Check Point Avanan (Harmony Email & Collaboration). Enables AI assistants to manage security events, investigate threats, and handle multi-tenant MSP operations across your email security environment. This is a Model Context Protocol (MCP) server that connects Claude (or any MCP-compatible AI) to your Check Point Avanan environment. — a growing suite of AI integrations for the MSP stack. Built by MSPs, for MSPs. - : hec_get_event renders as a read-only interactive card in MCP Apps hosts (Claude Desktop/web) showing severity, state, platform, and remediation status; neutral by default, brandable via window. injection or MCP_BRAND_* env vars; plain-JSON behavior is unchanged in other hosts Copy .env.example and set the variables below. Leave CONDUIT_S2S_SECRET empty in that file. /health stays unauthenticated. The stdio transport does not use CONDUIT_S2S_SECRET.
README
以下为原文 README 节选，完整内容请查看原文。
Avanan (Check Point) MCP Server
A Model Context Protocol (MCP) server for Check Point Avanan (Harmony Email & Collaboration). Enables AI assistants to manage security events, investigate threats, and handle multi-tenant MSP operations across your email security environment.
This is a Model Context Protocol (MCP) server that connects Claude (or any MCP-compatible AI) to your Check Point Avanan environment.
Part of the MSP Claude Plugins ecosystem — a growing suite of AI integrations for the MSP stack. Built by MSPs, for MSPs.
Features
- Interactive Security Event Card (MCP Apps):
hec_get_eventrenders as a read-only interactive card in MCP Apps hosts (Claude Desktop/web) showing severity, state, platform, and remediation status; neutral by default, brandable viawindow.__BRAND__injection orMCP_BRAND_*env vars; plain-JSON behavior is unchanged in other hosts
Installation
npm install @wyre-ai/avanan-mcp
Configuration
Copy .env.example and set the variables below. Leave CONDUIT_S2S_SECRET empty in that file.
| Variable | Required | Description |
|---|---|---|
CHECKPOINT_CLIENT_ID |
For stdio and AUTH_MODE=env |
Checkpoint/Avanan OAuth2 client ID |
CHECKPOINT_CLIENT_SECRET |
For stdio and AUTH_MODE=env |
Checkpoint/Avanan OAuth2 client secret |
CHECKPOINT_REGION |
No | API region (us, eu, au, in). Auto-detected from the JWT when omitted. |
MCP_TRANSPORT |
No | stdio (default) or http |
AUTH_MODE |
No | gateway (Docker image and Compose default) or env. Gateway mode requires X-Checkpoint-Client-Id and X-Checkpoint-Client-Secret on each /mcp request and never falls back to CHECKPOINT_*. env uses those variables only after S2S auth succeeds. |
CONDUIT_S2S_SECRET |
Yes for HTTP | Service-to-service HMAC secret. The HTTP server logs an error and exits non-zero when this is empty or a known placeholder (changeme, replace-with-a-real-secret, your-s2s-secret, and the other public example values). MCP_ALLOW_INSECURE_DEV=1 does not accept a placeholder. Compose will not start without it. Never commit a real value. The value is never logged. Generate one with openssl rand -hex 32. |
MCP_ALLOW_INSECURE_DEV |
No | Set to exactly 1 only for local development to start HTTP without CONDUIT_S2S_SECRET. The process logs a warning, does not enforce X-Gateway-S2S, and binds 127.0.0.1 only. A non-loopback MCP_HTTP_HOST (including 0.0.0.0) is overridden and the override is logged. |
安装
npx @wyre-ai/avanan-mcp配置
{
"mcpServers": {
"avanan-mcp": {
"command": "npx",
"args": ["@wyre-ai/avanan-mcp"],
"env": {
"CHECKPOINT_CLIENT_ID": "your-checkpoint-client-id"
"CHECKPOINT_CLIENT_SECRET": "your-checkpoint-client-secret"
}
}
}
}