Skip to main content
Glama
mkol5222

CheckPoint MCP Servers Explorer

by mkol5222
README.md
# CheckPoint MCP Servers Explorer

MCP server for exploring and introspecting CheckPoint MCP servers. Provides tools to fetch server information, list available servers, and introspect their tools.

## Installation

This project uses `uv` for Python project management.

```bash
# Install dependencies
uv sync
```

## Usage

Run the server:

```bash
# Using the CLI entry point
uv run chkp-mcp-servers-mcp-server

# Or directly with Python
uv run python -m chkp_mcp_servers
```

Run directly with uvx (no installation needed):

```bash
uvx --from . chkp-mcp-servers-mcp-server
```

## Claude Desktop Configuration

### Option 1: Using MCPB File (Recommended)

Double-click the `chkp-mcp-servers-local.mcpb.json` file to install directly into Claude Desktop.

### Option 2: Manual Configuration

Add to your `~/Library/Application Support/Claude/claude_desktop_config.json`:

```json
{
  "mcpServers": {
    "chkp-mcp-servers": {
      "command": "/Users/YOUR_USERNAME/.local/bin/uv",
      "args": [
        "--directory",
        "/path/to/chkp_mcps",
        "run",
        "chkp-mcp-servers-mcp-server"
      ]
    }
  }
}
```

Replace `/path/to/chkp_mcps` with the absolute path to this project directory.

**Note**: Use the full path to `uv` (find it with `which uv`) because Claude Desktop doesn't inherit your shell's PATH.

### Option 3: Install from GitHub (After Publishing)

Use the `chkp-mcp-servers.mcpb.json` file after publishing to GitHub:

```bash
# Update the repository URL in chkp-mcp-servers.mcpb.json first
# Then double-click to install
```

## Tools

- **echo**: Echoes back the provided message
  - Arguments:
    - `message` (str): The message to echo back

- **fetch_readme**: Fetches the README content from CheckPointSW/mcp-servers repository
  - Arguments: None
  - Returns: The content of the README.md file as text

- **list_chkp_mcp_servers**: Lists all CheckPoint MCP servers from the repository
  - Arguments: None
  - Returns: A structured list of MCP servers with:
    - `server_name`: Name of the server
    - `package_name`: NPM package name
    - `description`: Server description

- **get_chkp_mcp_server_tools**: Gets all tools from a CheckPoint MCP server
  - Arguments:
    - `package_name` (str): The NPM package name (e.g., "@chkp/quantum-gw-cli-mcp")
  - Returns: A list of tools with:
    - `name`: Tool name
    - `description`: Tool description
    - `inputSchema`: JSON schema for the tool's input parameters

- **get_chkp_mcp_server_prompts**: Gets all prompts from a CheckPoint MCP server
  - Arguments:
    - `package_name` (str): The NPM package name (e.g., "@chkp/quantum-gw-cli-mcp")
  - Returns: A list of prompts with:
    - `name`: Prompt name
    - `description`: Prompt description
    - `arguments`: List of prompt arguments with name, description, and required flag

- **get_chkp_mcp_server_documentation**: Gets NPM package documentation
  - Arguments:
    - `package_name` (str): The NPM package name (e.g., "@chkp/quantum-management-mcp")
  - Returns: Package documentation as markdown, including README, configuration details, and environment variables

TDQS

A4.2/5.0

Scored across 6 tools

Disambiguation4/5

Most tools have distinct purposes: fetch_raw vs parse list, retrieve tools, prompts, or docs. echo is unrelated but clearly separate. Slight overlap between fetch_readme and list_chkp_mcp_servers since both read the README, but their outputs differ.

Naming Consistency4/5

The main tools follow a consistent pattern with prefixes like list_chkp_mcp_servers and get_chkp_mcp_server_*. However, 'echo' and 'fetch_readme' deviate from the dominant naming convention, creating minor inconsistency.

Tool Count5/5

With 6 tools, the set is well-scoped for an explorer server focused on discovering and inspecting CheckPoint MCP servers. Each tool adds distinct value without redundancy.

Completeness4/5

The server covers the exploration lifecycle well: listing servers, fetching tools/prompts/documentation, and raw README access. Minor gaps include lack of direct config retrieval or server metadata details, but these are workarounds via documentation.

Maintenance

ActivityInactive
ResponsivenessNo issues