Recommendation

Use Continue’s .continue/mcpServers/ folder for a dedicated MCP block. Continue can also load JSON MCP configs copied from tools such as Claude, Cursor, or Cline.

YAML stdio

Create:

1
.continue/mcpServers/netskope-npa.yaml
1
2
3
4
5
6
7
8
9
10
11
12
13
name: Netskope NPA MCP
version: 0.0.1
schema: v1
mcpServers:
  - name: Netskope NPA
    type: stdio
    command: npx
    args:
      - "-y"
      - "@johnneerdael/ns-private-access-mcp"
    env:
      NETSKOPE_BASE_URL: "https://YOUR-TENANT.goskope.com"
      NETSKOPE_API_TOKEN: "YOUR_NETSKOPE_API_TOKEN"

YAML Streamable HTTP

1
2
3
4
5
6
7
8
9
10
name: Netskope NPA MCP
version: 0.0.1
schema: v1
mcpServers:
  - name: Netskope NPA
    type: streamable-http
    url: https://YOUR-MCP-HOST.example.com/mcp
    headers:
      X-Netskope-Tenant: "https://YOUR-TENANT.goskope.com"
      Authorization: "Bearer YOUR_NETSKOPE_API_TOKEN"

JSON compatibility option

You can also place a JSON MCP config at:

1
.continue/mcpServers/mcp.json

Verify

Use Continue Agent mode. Then ask:

1
List the Netskope NPA MCP tools you can access. Do not call any write tools.

Common issues

Symptom Fix
Tools do not appear Confirm you are in Agent mode.
YAML ignored Include name, version, and schema.
JSON copied but not loaded Place it under .continue/mcpServers/, plural.
Remote server fails Confirm type: streamable-http and the /mcp URL.

Platform notes

Continue documents .continue/mcpServers, YAML MCP blocks, JSON compatibility, stdio, sse, and streamable-http.

Source: Continue MCP setup