How do I install SentinelOne (Purple)?

Copy the stdio config for Cursor, Claude Desktop, Claude Code, or VS Code on this page. It uses the publisher's install, not a PlugMCP proxy.

Does SentinelOne (Purple) need an API key?

The publisher lists these environment variables: PORT, IDLE_EVICT_MS, SPAWN_READY_TIMEOUT_MS, LOG_LEVEL.

What transport does SentinelOne (Purple) use?

SentinelOne (Purple) runs locally over stdio.

When was SentinelOne (Purple) last checked?

Last checked 2026-11-12. Multitenant Streamable HTTP wrapper for the SentinelOne purple-mcp server.

SentinelOne (Purple) MCP server

Power your agent

Add this server

The publisher's own command. Not a PlugMCP endpoint.

Add to Cursor Add to VS Code Run on PlugMCP

Host a copy with our keys and logs.

Local command

docker run -i --rm ghcr.io/wyre-ai/sentinelone-mcp:v1.0.10

Credentials from the publisher

PORT — Public listen port for the proxy (POST /mcp, GET /health)
IDLE_EVICT_MS — Idle tenant timeout before a purple-mcp child is evicted (ms)
SPAWN_READY_TIMEOUT_MS — How long to wait for a spawned child to start serving HTTP (ms, default 90s). A still-starting child is kept after the first timeout for reuse by the next request instead of killing and respawning it; a second timeout cleans it up.
LOG_LEVEL — Fastify log level: debug, info, warn, error

Claude Code has no install link for a local command. Copy the command below and run it in a terminal.

shClaude Code

1PORT=<value> IDLE_EVICT_MS=<value> SPAWN_READY_TIMEOUT_MS=<value> LOG_LEVEL=<value> claude mcp add io.github.wyre-ai-sentinelone-mcp -- docker run -i --rm ghcr.io/wyre-ai/sentinelone-mcp:v1.0.10

Run in a terminal.

jsonClaude Desktop

1{2  "mcpServers": {3    "io.github.wyre-ai-sentinelone-mcp": {4      "command": "docker",5      "args": [6        "run",7        "-i",8        "--rm",9        "ghcr.io/wyre-ai/sentinelone-mcp:v1.0.10"10      ],11      "env": {12        "PORT": "<value>",13        "IDLE_EVICT_MS": "<value>",14        "SPAWN_READY_TIMEOUT_MS": "<value>",15        "LOG_LEVEL": "<value>"16      }17    }18  }19}

claude_desktop_config.json

Local · ociPublisher installStep-by-step: add this in Claude

Remote URL or a command on your machine? How the two installs differ

Run on PlugMCP

Host a copy with our keys and logs.

A new server you create. It is not this listing's official endpoint. Use the publisher install when you want their URL and their credentials.

Launch

Server facts

Local

Transport: stdio
Version

Tools

No tool list yet. Remote servers get one after the first health check.

FAQ

Questions

sentinelone-mcp

Multitenant Streamable HTTP wrapper for sentinel-one/purple-mcp, built so the wyre-technology MCP gateway can forward per-tenant SentinelOne credentials as HTTP headers.

Why

purple-mcp is a great first-party MCP server, but it reads its SentinelOne console token + URL from environment variables at process startup, which makes it single-tenant per container. Our gateway is multi-tenant: every request carries the calling org's credentials as HTTP headers, and the vendor container has to translate those headers into something the upstream understands.

This image bundles purple-mcp plus a small Node/Fastify proxy. The proxy:

Listens on :8080 with POST /mcp and GET /health.
Requires a valid X-Gateway-S2S proof, then reads X-S1-API-Token and X-S1-Console-URL from that request (legacy x-purplemcp-token / x-purplemcp-base-url still accepted). A request missing either the token or the console URL, after per-field fallback, gets 401, which Conduit's vendor-monitor treats as reachable but auth-gated. There is no fallback to PURPLEMCP_CONSOLE_* in the environment.
Lazily spawns one purple-mcp --mode streamable-http child per (token, base-url) tenant on a private loopback port, with the right env vars set.
Proxies the request body to that child and streams the response back.
Evicts idle children after 60 minutes (IDLE_EVICT_MS).

The result is a single container that the gateway can talk to like any other vendor MCP server.

Configuration

Env var	Default	Notes
`PORT`	`8080`	Public listen port.
`MCP_HTTP_HOST`	`0.0.0.0` when a real secret is set	Bind address. A configured `CONDUIT_S2S_SECRET` honors this value, including `0.0.0.0`. Unset keeps that historical bind. The image and Compose set `0.0.0.0` inside the container and publish `127.0.0.1:8080:8080` on the host.
`CONDUIT_S2S_SECRET`	—	Required. Service-to-service secret. The process logs an error and exits non-zero when this is empty or a known placeholder (`changeme`, `secret`, `replace-me`, `replace-with-a-real-secret`, and the other example values). Generate one with `openssl rand -hex 32`. Compose will not start without it. The value is never logged.
`MCP_ALLOW_INSECURE_DEV`	unset	Set to exactly `1` only for local development to start without `CONDUIT_S2S_SECRET`. The process logs a warning, does not enforce `X-Gateway-S2S`, and binds `127.0.0.1` only. A non-loopback `MCP_HTTP_HOST` refuses to start. A known placeholder secret still refuses to start.
`PURPLE_MCP_DIR`	`/opt/purple-mcp`	Where purple-mcp source + venv live.
`PURPLE_MCP_PYTHON`	`/opt/purple-mcp/.venv/bin/python`	Python interpreter from the upstream venv.
`IDLE_EVICT_MS`	`3600000`	Idle tenant timeout (60 min). Longer keeps children warm and avoids repeated cold starts.
`SPAWN_READY_TIMEOUT_MS`	`30000`	How long to wait for a child to start serving HTTP.
`MAX_CHILDREN`	`50`	Cap on distinct concurrent tenant children. A new-tenant spawn beyond the cap is rejected (`502`) rather than evicting an existing child.
`LOG_LEVEL`

Copy .env.example. Leave CONDUIT_S2S_SECRET empty in that file; put a real value only in an uncommitted .env or the process environment.

Request headers

This server is gateway mode. It does not read PURPLEMCP_CONSOLE_TOKEN or PURPLEMCP_CONSOLE_BASE_URL from the environment for an incoming request. The gateway must forward these headers on every /mcp request. Names are case-insensitive. When both pairs are present, the X-S1-* value wins per field.

Header	SentinelOne credential
`X-Gateway-S2S`	Service-to-service proof. Required on `/mcp` when `CONDUIT_S2S_SECRET` is set. Not a SentinelOne credential.
`X-S1-API-Token`	`PURPLEMCP_CONSOLE_TOKEN` passed to that request's child (Account- or Site-level service user token). Catalog `headerMapping` name.
`X-S1-Console-URL`	`PURPLEMCP_CONSOLE_BASE_URL` passed to that request's child (e.g. `https://yourtenant.sentinelone.net`). Catalog `headerMapping` name.
`x-purplemcp-token`	Legacy alias for the API token.
`x-purplemcp-base-url`	Legacy alias for the console URL.

X-Gateway-S2S

With CONDUIT_S2S_SECRET set, every POST /mcp must include X-Gateway-S2S. The check is verifyS2sHeader in src/s2s-verify.ts: the header value is t=<unix seconds>,v1=<hex>, where the hex is HMAC-SHA256 of the literal string t=<unix seconds> keyed with CONDUIT_S2S_SECRET (64 lowercase hex characters). The timestamp must be within 300 seconds of the server clock. A missing or invalid header is HTTP 401, before tenant credentials are read, and the secret is not logged.

X-Gateway-S2S: t=1710000000,v1=<hmac-sha256 hex of "t=1710000000">

In gateway mode, /mcp also requires X-S1-API-Token and X-S1-Console-URL (or the legacy x-purplemcp-* pair, including a mixed pair). A request missing either credential is HTTP 401 (JSON-RPC -32001) and does not fall back to PURPLEMCP_CONSOLE_* in the process environment. Vendor-monitor's credless initialize probe relies on that: 401/403 means the sidecar is up but auth-gated, while 400 marks the slug DOWN.

GET /health stays unauthenticated and does not read credentials.

Build

docker build -t ghcr.io/wyre-ai/sentinelone-mcp:latest .

The image listens on 0.0.0.0 inside the container (MCP_HTTP_HOST) and refuses to start until CONDUIT_S2S_SECRET is set. Publish the port on loopback. SentinelOne credentials arrive on each request as headers; they are not read from the environment.

docker run --rm \
  -e CONDUIT_S2S_SECRET="$(openssl rand -hex 32)" \
  -p 127.0.0.1:8080:8080 \
  ghcr.io/wyre-ai/sentinelone-mcp:latest

Compose refuses to start when CONDUIT_S2S_SECRET is unset, publishes 127.0.0.1:8080:8080, and does not inject PURPLEMCP_CONSOLE_TOKEN or PURPLEMCP_CONSOLE_BASE_URL:

CONDUIT_S2S_SECRET="$(openssl rand -hex 32)" docker compose up --build

Local HTTP without a secret is development-only. It binds 127.0.0.1 and logs a warning. A non-loopback MCP_HTTP_HOST (including 0.0.0.0) makes startup exit:

npm run build
MCP_ALLOW_INSECURE_DEV=1 npm start

License

Apache-2.0. The bundled purple-mcp is MIT-licensed by SentinelOne.

Add this server

Host a copy with our keys and logs.

Server facts

Tools

Questions

How do I install SentinelOne (Purple)?

Does SentinelOne (Purple) need an API key?

What transport does SentinelOne (Purple) use?

When was SentinelOne (Purple) last checked?

Documentation

sentinelone-mcp

Why

Configuration

Request headers

X-Gateway-S2S

Build

License