mcp s
MCP server from CheckPointSW/mcp-servers
claude mcp add --transport stdio checkpointsw-mcp-servers npx @chkp/quantum-gaia-mcp
How to use
This MCP repository hosts a suite of server implementations, each providing a structured, machine-readable API for various Check Point security domains. You can run any of the included MCP servers individually via the npm/npx workflow described here. Each server exposes domain-specific data (policies, logs, threat intel, GAIA network data, documentation guidance, and more) in a consistent MCP format that AI copilots can consume. To start a server, choose the package you need (for example, management or threat-prevention) and run it with the corresponding MCP package via npx. Once running, you can query the server for its domain data—policies, objects, logs, configurations, or real-time diagnostics—using your MCP client. The repository also includes development and Nx workspace tooling to build and test individual servers or the whole monorepo.
How to install
Prerequisites:
- Node.js (recommended LTS) and npm installed on your machine
- Git installed to clone the repository
- Optional: a Check Point environment if you plan to connect to live management data
Install steps:
-
Clone the repository: git clone https://github.com/your-org/checkpoint-mcp-servers.git
-
Navigate into the project and install dependencies: cd checkpoint-mcp-servers npm install
-
Build all packages (optional but recommended for development): npm run build
-
Run a specific MCP server (example for management): npx nx run @chkp/quantum-management-mcp:dev
-
If you prefer individual package execution without the Nx graph, you can run via npx directly: npx @chkp/quantum-management-mcp
-
Refer to each package’s README for any package-specific configuration requirements.
Additional notes
Tips and common considerations:
- This repository uses Nx to manage multiple packages. You can run tasks for specific packages using the provided aliases or direct nx commands.
- Each MCP server may require environment-specific configuration (e.g., connections to Check Point management systems, credentials, or policy contexts). Do not expose credentials to the model; use dedicated secure env vars and secrets management.
- If you plan to run multiple MCP servers locally, ensure your environment has sufficient resources (CPU, memory) to host multiple Node processes concurrently.
- The npm_package field is null because this is a monorepo containing many MCP server packages rather than a single npm package you install directly.
Related MCP Servers
zen
Selfhosted notes app. Single golang binary, notes stored as markdown within SQLite, full-text search, very low resource usage
MCP -Deepseek_R1
A Model Context Protocol (MCP) server implementation connecting Claude Desktop with DeepSeek's language models (R1/V3)
mcp-fhir
A Model Context Protocol implementation for FHIR
mcp
Inkdrop Model Context Protocol Server
mcp-appium-gestures
This is a Model Context Protocol (MCP) server providing resources and tools for Appium mobile gestures using Actions API..
dubco -npm
The (Unofficial) dubco-mcp-server enables AI assistants to manage Dub.co short links via the Model Context Protocol. It provides three MCP tools: create_link for generating new short URLs, update_link for modifying existing links, and delete_link for removing short links.