SentinelOne MCP Server

An MCP server for SentinelOne Singularity. It lets an AI agent ask Purple AI hunting questions, run PowerQueries over the Singularity Data Lake, and read alerts, vulnerabilities, misconfigurations and the asset inventory of one SentinelOne console, plus VirusTotal and public CVE lookups. It is read-only.

The tools come from SentinelOne's own open-source tool library, purple-mcp (MIT), which is installed as a pinned dependency. purple-mcp reads one console's credentials from environment variables when it starts; this server adds what a multi-tenant gateway needs: credentials per request, the standard error envelope, concise tool documentation, and the usual health and isolation guarantees.

• Transport: MCP Streamable HTTP at POST /mcp, health probe at GET /health

• Stateless and multi-tenant: credentials arrive on every request as HTTP headers and are never stored; every tool is listed from the first tools/list

• Python 3.12, uv, FastMCP, purple-mcp

• License: Apache-2.0, Copyright 2026 MSPbots.ai (purple-mcp: MIT, see NOTICE)

Authentication headers

Where to get them:

• In the SentinelOne console create a service user (Policy & Settings -> User Management -> Service Users) at Account or Site scope with a viewer-level role, and generate its API token. The token must cover a single Account or Site; Global-scope tokens are not supported. Purple AI and the Data Lake need the matching licences on the account.

• The console URL is the address you sign in to, e.g. https://your-console.sentinelone.net; a path after the host name is ignored.

• A VirusTotal key comes from the VirusTotal profile page; threat_intel_search needs a key with Intelligence access.

How credentials are used: for each request the server builds purple-mcp's settings from these headers and makes them current only for that request; purple-mcp then calls the console's GraphQL and REST APIs with the token. A request to /mcp without the URL or token gets HTTP 401 naming the missing header; a URL that is not https gets HTTP 400.

Related MCP server: VAST DB MCP Server

Tools

All tools return a JSON string and are read-only. Lists page with first (1-100) and after (pageInfo.endCursor of the previous page); the inventory pages with limit / skip. search_* tools take filters as a JSON string or array (see each tool's parameter description); datetime filters use epoch milliseconds from iso_to_unix_timestamp.

Errors come back as a JSON envelope instead of an exception:

{"error": {"code": "unauthorized", "message": "...401...", "retryable": false}}

code is one of not_configured, unauthorized, not_found, invalid_argument, rate_limited, upstream_error.

Run locally

uv sync
uv run python -m sentinelone_mcp          # listens on 0.0.0.0:8080

or with Docker:

docker build --platform linux/amd64 -t sentinelone-mcp:dev .
docker run --rm -p 8080:8080 sentinelone-mcp:dev

Configuration (environment variables, all optional): MCP_HTTP_HOST (default 0.0.0.0), MCP_HTTP_PORT (default 8080), LOG_LEVEL (default INFO). Credentials are never read from the environment.

Testing example

# list tools
curl -s http://localhost:8080/mcp \
  -H "Content-Type: application/json" \
  -H "Accept: application/json, text/event-stream" \
  -H "X-Purplemcp-Base-Url: https://your-console.sentinelone.net" \
  -H "X-Purplemcp-Token: your-console-token" \
  -d '{"jsonrpc":"2.0","id":1,"method":"tools/list","params":{}}'

# new critical alerts
curl -s http://localhost:8080/mcp \
  -H "Content-Type: application/json" \
  -H "Accept: application/json, text/event-stream" \
  -H "X-Purplemcp-Base-Url: https://your-console.sentinelone.net" \
  -H "X-Purplemcp-Token: your-console-token" \
  -d '{"jsonrpc":"2.0","id":2,"method":"tools/call","params":{"name":"search_alerts","arguments":{"filters":[{"fieldId":"severity","filterType":"string_equals","value":"CRITICAL"},{"fieldId":"status","filterType":"string_equals","value":"NEW"}],"first":10}}}'

Unit tests (no network access needed):

uv run pytest

Delivery notes

• Tool count (33). Names and parameters are purple-mcp's, kept as an existing contract.

• Built on the vendor's library. API calls, GraphQL queries and parsing are purple-mcp's, pinned to a reviewed commit in pyproject.toml; updating it is a one-line change followed by the snapshot tests.

• Per-request credentials. purple-mcp looks its settings up through one function; this server points that function at the current request's settings, so concurrent tenants never share a token, and no process-wide credentials exist.

• Documentation. Tool descriptions are short; filter syntax, field names and enum values are in each parameter's description.

• Threat intelligence needs the optional VirusTotal key; without it those tools say so.

License

Apache License 2.0 - see LICENSE and NOTICE.