SentinelOne MCP
mcpotherEvery SentinelOne v2.1 management endpoint, plus an offline SQLite store and cross-entity analytics
run it
on your own machines, one way per deploy method# once, as root:
docker build -t mcp-local/sentinelone:latest https://github.com/servosity/msp-skills.git#:skills/sentinelone
#!/usr/bin/env bash
# sentinelone (io.github.Servosity/sentinelone-mcp), recipe docker (generated).
# Generated by Hub for toolset "my-agent"; started by mcp-my-agent-sentinelone.service.
set -euo pipefail
export HOST=127.0.0.1 PORT=8101
exec docker run --rm --name mcp-my-agent-sentinelone -p 127.0.0.1:${PORT}:8000 --env-file /etc/mcp/my-agent.env mcp-local/sentinelone:latest
[Unit]
Description=MCP server sentinelone (toolset my-agent), generated by Hub
After=network-online.target docker.service
Wants=network-online.target
[Service]
Type=simple
User=mcp
Group=mcp
SupplementaryGroups=docker
EnvironmentFile=/etc/mcp/my-agent.env
Environment=HOME=/var/lib/mcp/sentinelone
WorkingDirectory=/var/lib/mcp/sentinelone
ExecStart=/opt/mcp/my-agent/bin/sentinelone.sh
Restart=on-failure
RestartSec=5
NoNewPrivileges=true
ProtectSystem=strict
ProtectHome=true
PrivateTmp=true
ReadWritePaths=/var/lib/mcp/sentinelone
[Install]
WantedBy=multi-user.target
docker build -t sentinelone https://github.com/servosity/msp-skills.git#:skills/sentinelone docker run --rm -p 127.0.0.1:8101:8000 -e SENTINELONE_API_TOKEN -e SENTINELONE_BASE_URL -e SENTINELONE_USER_AGENT -e SENTINELONE_MCP_HTTP_TOKEN -e PRINTING_PRESS_CLIENT_PROFILE sentinelone
# Generated by Hub for toolset "my-agent" (2026-10-18T04:28:45+00:00).
# Each package server runs behind a stdio->HTTP bridge and listens on localhost only.
# cp .env.example .env # fill the ${VAR}s
# docker compose up -d && bash smoke.sh
# Remote servers are not here: clients reach them directly (see clients/).
name: mcp-my-agent
services:
sentinelone:
build:
context: https://github.com/servosity/msp-skills.git#:skills/sentinelone
ports:
- 127.0.0.1:8101:8000
restart: unless-stopped
x-note: 'CHANGE_ME: built from the repository''s Dockerfile, assuming it serves streamable HTTP at
:8000/mcp. Nothing has run this yet; the worker replaces it with a tested recipe.'
environment:
SENTINELONE_API_TOKEN: ${SENTINELONE_API_TOKEN}
SENTINELONE_BASE_URL: ${SENTINELONE_BASE_URL}
SENTINELONE_USER_AGENT: ${SENTINELONE_USER_AGENT}
SENTINELONE_MCP_HTTP_TOKEN: ${SENTINELONE_MCP_HTTP_TOKEN}
PRINTING_PRESS_CLIENT_PROFILE: ${PRINTING_PRESS_CLIENT_PROFILE}
volumes:
npm-cache: {}
uv-cache: {}
# Generated by Hub for toolset "my-agent" (2026-10-18T04:28:45+00:00).
# kubectl create namespace mcp
# kubectl -n mcp create secret generic mcp-credentials --from-env-file=.env
# kubectl apply -f kubernetes.yaml
# Services are cluster-internal: <name>.mcp.svc.cluster.local:8000/mcp. Put an ingress
# with auth in front before exposing any of them.
apiVersion: v1
kind: Namespace
metadata:
name: mcp
---
apiVersion: apps/v1
kind: Deployment
metadata:
name: sentinelone
namespace: mcp
labels: &id001
app: sentinelone
spec:
replicas: 1
selector:
matchLabels: *id001
template:
metadata:
labels: *id001
spec:
containers:
- name: sentinelone
image: CHANGE_ME
ports:
- containerPort: 8000
name: http
env:
- name: SENTINELONE_API_TOKEN
valueFrom:
secretKeyRef:
name: mcp-credentials
key: SENTINELONE_API_TOKEN
- name: SENTINELONE_BASE_URL
valueFrom:
secretKeyRef:
name: mcp-credentials
key: SENTINELONE_BASE_URL
- name: SENTINELONE_USER_AGENT
valueFrom:
secretKeyRef:
name: mcp-credentials
key: SENTINELONE_USER_AGENT
- name: SENTINELONE_MCP_HTTP_TOKEN
valueFrom:
secretKeyRef:
name: mcp-credentials
key: SENTINELONE_MCP_HTTP_TOKEN
- name: PRINTING_PRESS_CLIENT_PROFILE
valueFrom:
secretKeyRef:
name: mcp-credentials
key: PRINTING_PRESS_CLIENT_PROFILE
---
apiVersion: v1
kind: Service
metadata:
name: sentinelone
namespace: mcp
spec:
selector:
app: sentinelone
ports:
- port: 8000
targetPort: http
name: http
# Generated by Hub for toolset "my-agent" (2026-10-18T04:28:45+00:00).
# Credentials come from the Secret 'mcp-credentials' (kubectl create secret generic ... --from-env-file=.env).
# Each server under `servers` is one Deployment + Service; the keys after it configure
# upstream charts a worker verified.
servers:
sentinelone:
enabled: true
replicas: 1
port: 8000
path: /mcp
container:
name: sentinelone
image: CHANGE_ME
ports:
- containerPort: 8000
name: http
env:
- name: SENTINELONE_API_TOKEN
valueFrom:
secretKeyRef:
name: mcp-credentials
key: SENTINELONE_API_TOKEN
- name: SENTINELONE_BASE_URL
valueFrom:
secretKeyRef:
name: mcp-credentials
key: SENTINELONE_BASE_URL
- name: SENTINELONE_USER_AGENT
valueFrom:
secretKeyRef:
name: mcp-credentials
key: SENTINELONE_USER_AGENT
- name: SENTINELONE_MCP_HTTP_TOKEN
valueFrom:
secretKeyRef:
name: mcp-credentials
key: SENTINELONE_MCP_HTTP_TOKEN
- name: PRINTING_PRESS_CLIENT_PROFILE
valueFrom:
secretKeyRef:
name: mcp-credentials
key: PRINTING_PRESS_CLIENT_PROFILE
# helm install my-agent helm/my-agent -n mcp
in the cloud
one click: the provider's deploy form opens filled in, in your own account- koyeb
-
The form opens with CHANGE_ME for each value you supply: SENTINELONE_API_TOKEN, SENTINELONE_BASE_URL, SENTINELONE_USER_AGENT, SENTINELONE_MCP_HTTP_TOKEN, PRINTING_PRESS_CLIENT_PROFILE. Fill them in before you deploy.
Koyeb builds the repository's Dockerfile from branch main; change the branch in the form if the default one has another name.
Clients connect to the service's https://…koyeb.app address plus /mcp.
- cloud run
-
Cloud Shell clones the repository, builds its Dockerfile and deploys it to Cloud Run.
Cloud Run sends requests to $PORT (8080); the recipe expects :8000, so the server has to read PORT, or set the container port on the service afterwards.
Set SENTINELONE_API_TOKEN, SENTINELONE_BASE_URL, SENTINELONE_USER_AGENT, SENTINELONE_MCP_HTTP_TOKEN, PRINTING_PRESS_CLIENT_PROFILE on the service afterwards: the button asks only for what the repository's own app.json lists.
connect to it
copy what your client needs{
"mcpServers": {
"sentinelone": {
"command": "CHANGE_ME",
"args": []
}
}
}
#!/usr/bin/env bash # Registers every server with Claude Code (run once; `claude mcp list` to check). set -euo pipefail set -a; [ -f .env ] && source .env; set +a claude mcp add sentinelone -- CHANGE_ME
{
"mcpServers": {
"sentinelone": {
"command": "CHANGE_ME",
"args": []
}
}
}
{
"servers": {
"sentinelone": {
"type": "stdio",
"command": "CHANGE_ME",
"args": []
}
}
}
name: my-agent target: local servers: - hub: io.github.Servosity/sentinelone-mcp
- not probed yet: tools unpinned, ingest lists them
- no recipe for target 'local': fill the files by hand