The MCP Server Start Guide

🚧
This documentation may contain references to third party software or websites. N-able has no control over third party software or content and is not responsible for the availability, security, or operation, of any third-party software. If you decide to utilize a release involving third-party software, you do so entirely at your own risk and subject to the applicable third party’s terms and conditions of the use of such software. No information obtained by you from N-able or this documentation shall create any warranty for such software.

Adlumin MCP Setup

Connect your AI assistant to the Adlumin security platform for real-time threat intelligence and SOC workflows. This guide walks through configuring the Adlumin MCP server in Claude Desktop, ChatGPT, and GitHub Copilot for VS Code.

Download the MCP Server and Documentation HERE

Prerequisites

Before starting, make sure you have the following:

Adlumin API key — Obtain a Bearer token from your Adlumin platform admin. Pass it as Authorization: Bearer <token> to https://api.adlumin.com/v1.
Node.js v18+ — Required for the remote proxy method in Claude Desktop. Download it from nodejs.org. Verify your version:
```
node --version
```
Python 3.10+ — Required only if you run the server locally. Verify your version:
```
python3 --version
```

shield
Keep your API key private. Never commit it to git or share it in screenshots.

Option 1: Claude Desktop

There are two ways to connect Claude Desktop to Adlumin:

Remote proxy — Recommended. No Python required.
Local Python server — Use this if you need to modify the server or work in a restricted network environment.

Method A: Remote proxy

This method uses mcp-remote, an npm package that bridges Claude Desktop's stdio transport to the hosted Adlumin MCP server over HTTP.

Open Claude Desktop.
Go to Settings → Developer → Edit Config to open claude_desktop_config.json.

File locations:
- macOS: ~/Library/Application Support/Claude/claude_desktop_config.json
- Windows: %APPDATA%\Claude\claude_desktop_config.json

Add the following block inside the mcpServers object. Create the object if it does not exist:

{
  "mcpServers": {
    "adlumin-mcp": {
      "command": "npx",
      "args": [
        "mcp-remote",
        "https://<ADLUMIN_MCP_SERVER_URL>/mcp",
        "--header",
        "Authorization: Bearer <YOUR_API_KEY>",
        "--transport",
        "http"
      ]
    }
  }
}

Replace <ADLUMIN_MCP_SERVER_URL> and <YOUR_API_KEY> with the values from your Adlumin admin.
Save the file.
Fully quit and reopen Claude Desktop.
Verify the connection. In a new chat, click the tools icon or type /. You should see Adlumin tools listed, such as get_detections and get_firewall_events.

If tools do not appear, check the Claude Desktop logs:

~/Library/Logs/Claude/mcp-server-adlumin-mcp.log

Method B: Local Python server

Run the server directly from the Python source. Use this method if you need to modify the server or work in a restricted network environment.

Unzip adlumin-mcp-python.zip to a known location, for example:
```
~/tools/adlumin-mcp-python/
```

Install dependencies:

cd ~/tools/adlumin-mcp-python
pip install -r requirements.txt

Add this block to claude_desktop_config.json:

{
  "mcpServers": {
    "adlumin-mcp": {
      "command": "python3",
      "args": ["/Users/you/tools/adlumin-mcp-python/server.py"],
      "env": {
        "ADLUMIN_API_KEY": "<YOUR_API_KEY>",
        "ADLUMIN_BASE_URL": "https://api.adlumin.com/v1"
      }
    }
  }
}

Replace <YOUR_API_KEY> with your Adlumin API key.
Save the file.
Fully quit and reopen Claude Desktop.
Verify that the Adlumin tools appear in Claude Desktop.

Option 2: ChatGPT

Native MCP support in ChatGPT is in early access as of 2025. The steps below use the Custom GPT and Actions method, which works with OpenAI plans that include GPT Builder access.

The Adlumin MCP server speaks HTTP and JSON, so you can expose it to ChatGPT by wrapping the endpoints you want to use in an OpenAPI schema as a GPT Action.

Go to chatgpt.com → Explore GPTs → Create.
Click Configure → Add actions → Create new action.

In the Schema field, paste an OpenAPI 3.1 definition for the Adlumin endpoints you want to expose.

Example for get_detections:

openapi: 3.1.0
info:
  title: Adlumin API
  version: "1"
servers:
  - url: https://api.adlumin.com/v1
paths:
  /detections:
    get:
      operationId: get_detections
      summary: List security detections
      parameters:
        - name: severity
          in: query
          schema:
            type: string
        - name: status
          in: query
          schema:
            type: string
      responses:
        "200":
          description: Detection list

Under Authentication, choose API Key.
Set the authentication type to Bearer and paste your Adlumin API key.
Click Save and Publish. Choose Only me to keep it private.
Test the GPT with:
```
Show me the latest critical detections.
```

If OpenAI adds native MCP support to your account, you can skip the OpenAPI schema and connect the MCP server URL directly in Connectors settings.

Option 3: GitHub Copilot in VS Code

VS Code supports MCP servers as of Copilot Chat v1.99+ from May 2025. This connects Adlumin tools directly into Copilot's agent mode.

Make sure you have VS Code 1.99+ and the GitHub Copilot Chat extension installed.
Sign in to GitHub Copilot.
Open the Command Palette:
- macOS: Cmd+Shift+P
- Windows/Linux: Ctrl+Shift+P
Run MCP: Add Server....

If you do not see this command, update VS Code and the Copilot Chat extension.
Choose HTTP (Server-Sent Events) as the transport type.
Enter the Adlumin MCP server URL when prompted:
```
http://<ADLUMIN_MCP_SERVER_URL>/mcp
```

VS Code opens your workspace .vscode/mcp.json file or user settings. Add the authorization header manually:

{
  "servers": {
    "adlumin-mcp": {
      "type": "http",
      "url": "http://<ADLUMIN_MCP_SERVER_URL>/mcp",
      "headers": {
        "Authorization": "Bearer <YOUR_API_KEY>"
      }
    }
  }
}

Save the file.
Open Copilot Chat with Ctrl+Alt+I.
Switch to Agent mode from the dropdown next to the send button.
Verify that Adlumin tools appear in the tools list.

Test with:

Use Adlumin to show me endpoint data for any offline agents.

If the server URL uses plain HTTP, VS Code may warn about insecure connections. You can suppress this per server with allowInsecure: true, or use the HTTPS endpoint if your admin has one configured.

Available tools

Tool	Category	Description
`get_detections`	Detections	List and filter security detections by severity, status, date range, or free text. Max 100 per page.
`acknowledge_detections`	Detections	Acknowledge one or more detections by ID, removing them from the active dashboard.
`get_at_risk_groups`	At-Risk Assets	List Active Directory groups flagged at risk due to overly broad or privileged permissions.
`get_at_risk_shares`	At-Risk Assets	List network shares flagged at risk, such as world-readable shares or shares accessible to privileged groups.
`get_at_risk_systems`	At-Risk Assets	List hosts flagged at risk due to misconfiguration, stale patches, or anomalous activity.
`get_endpoint_data`	Endpoint	List endpoint security agent telemetry for SentinelOne, CrowdStrike, Carbon Black, and Defender.
`get_complete_endpoint_data`	Endpoint	Tenant-wide summary of at-risk counts, sensor health, compliance posture, and network health score.
`get_device_data`	Endpoint	Base device inventory, including hostname, IP, MAC, OS, and domain, regardless of agent status.
`get_network_data`	Network	Network health score from 0–100 and per-metric breakdown, including stale accounts and GPO violations.
`get_firewall_events`	Firewall	Raw firewall log events with source and destination IPs, geo data, action, and UBA risk score.
`get_firewall_geo_aggregation`	Firewall	Top source and destination countries by firewall event volume.

Download the MCP Server and Documentation HERE