What runtime is required?

The server runs on Node.js. Install dependencies with `npm install`, then build and start with `npm run build` and `npm start`.

How do I authenticate?

Supply `NETSKOPE_BASE_URL` and `NETSKOPE_API_TOKEN` as environment variables, or pass the token via an `Authorization` header and tenant URL via `X-Netskope-Tenant` header in the MCP client configuration.

What transport does it use?

It exposes a streamable HTTP endpoint at `/mcp` and a liveness endpoint at `/healthz`. A generic JSON client config can target a URL like `https://YOUR-MCP-HOST.example.com/mcp`.

What credentials does it need?

It reads `NETSKOPE_BASE_URL`, `NETSKOPE_TOKEN`, `YOUR_NETSKOPE_API_TOKEN`, `PUBLIC_URL`, `NETSKOPE_API_TOKEN` from the environment. Store these in your client's env block or a secrets manager — never commit them to a repository — and grant the narrowest scope that still covers your use case.

Netskope NPA MCP Server — Setup Guide for Claude

Name: Netskope NPA MCP Server
Author: johnneerdael

What is the Netskope NPA MCP server?

Netskope NPA MCP server exists for a simple reason — assistants are far more useful when they can act on Netskope NPA directly instead of describing what you should do. # Netskope NPA MCP Server A comprehensive Model Context Protocol (MCP) server for managing Netskope Private Access (NPA) infrastructure through AI-powered automation. ## 📚 Complete Documentation This project includes extensive.

Setting it up

Being a remote server, there is no local install. You register the endpoint with your client, authorise it once, and the tools appear.

Configuration and credentials

You will need 5 environment variables: NETSKOPE_BASE_URL, NETSKOPE_TOKEN, YOUR_NETSKOPE_API_TOKEN, PUBLIC_URL, NETSKOPE_API_TOKEN. The server will not start without them, which is usually why the tools fail to appear on a first run. Keep credentials in your client's env block or a secrets manager rather than in a file you might commit.

Choosing this one

Plenty of cloud and infrastructure servers cover similar ground. The differences that matter in practice are scope of access and how much setup stands between you and a working tool call. It is maintained by johnneerdael; worth a glance at recent repository activity before you build anything load-bearing on it.

We check each listing at SyncDev against the project's documentation before it goes live — if something here drifts out of date, it is a bug worth reporting.

Before you rely on it

Your data travels to the provider's service, so the usual questions apply about what you send and what they retain.
Missing credentials fail quietly in some clients — if no tools show up, check the environment block first.
MCP clients confirm each tool call by default. Leave that on until you have watched what the netskope npa mcp server does with a few real requests.

How to install the Netskope NPA MCP server

{
     "mcpServers": {
       "netskope-npa": {
         "command": "node",
         "args": ["/path/to/privateaccess-mcp/build/index.js"],
         "env": {
           "NETSKOPE_BASE_URL": "https://your-tenant.goskope.com",
           "NETSKOPE_TOKEN": "your-api-token"
         }
       }
     }
   }

Configuration as documented by the project. Restart the client after saving.

Configuration

Variable	Description	Required
NETSKOPE_BASE_URL	Endpoint or connection string the server talks to.	Yes
NETSKOPE_TOKEN	Credential the server authenticates with.	Yes
YOUR_NETSKOPE_API_TOKEN	Credential the server authenticates with.	Yes
PUBLIC_URL	Endpoint or connection string the server talks to.	Yes
NETSKOPE_API_TOKEN	Credential the server authenticates with.	Yes

Netskope NPA MCP Server

What is the Netskope NPA MCP server?

Setting it up

Configuration and credentials

Choosing this one

Before you rely on it

How to install the Netskope NPA MCP server

Configuration

Frequently asked questions

Alternatives to the Netskope NPA MCP server

Supabase

n8n

AWS

Browserbase

Cloudflare

Grafana