SentinelOne MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| S1_BASE_URL | Yes | Your management console URL, e.g. https://your-console.sentinelone.net | |
| S1_API_TOKEN | Yes | API token — generate in the console under My User → Actions → API Token Operations | |
| S1_ENABLE_RAW_API | No | Optional — set to true to expose s1_api_call for arbitrary endpoints. Leave unset for team deployments. |
Capabilities
Features and capabilities supported by this server
| Capability | Details |
|---|---|
| tools | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| s1_list_sitesA | List sites in the SentinelOne management console. In an MSP/MSSP console, sites are how clients are segmented — use this to discover the client list, then feed site IDs into the other tools. Returns name, state, licence counts (active/total), SKU/suite, expiration and health status per site. |
| s1_estate_overviewA | Estate-wide endpoint health overview grouped by site — one call answers "what is the state of every client's endpoints?". Sweeps all agents server-side and returns a table per site: agent count, online/offline, infected, agents needing an update, reboot-required, stale agents (not seen for N days) and OS breakdown. This is the primary tool for MSP health/AV reporting. Use s1_agents to drill into the individual machines afterwards. |
| s1_agentsA | List endpoint agents with filters — the drill-down tool for machines. Returns each agent's computer name, site, OS, agent version, online/infected/up-to-date status, last active date, last logged-in user and network status. Filter by site, name, health flags or OS. Returns a compact summary per agent by default; set full_details=true for complete raw records (large). Call s1_list_sites first to resolve site IDs. |
| s1_threatsA | List threats/detections with filters — the drill-down tool for incidents. Returns each threat's name, classification, confidence level (malicious/suspicious), analyst verdict, incident status, mitigation status and actions, detection engine, file path/hash, affected machine and site, sorted newest first. Returns a compact summary per threat by default; set full_details=true for complete raw records. Use s1_threat_summary for aggregated counts across the estate. |
| s1_threat_summaryA | Aggregated threat counts grouped by site — the reporting/dashboard tool. Sweeps ALL matching threats server-side and returns compact counts: per site by incident status, analyst verdict and classification, plus estate-wide totals, the most common threat names and the machines with the most detections. Ideal for "threats this month across all clients" reporting — pass created_after for the period. Use s1_threats to drill into individual detections afterwards. |
| s1_activitiesA | Activity/audit log from the management console: threat mitigations, agent installs/upgrades, policy changes, user logins, exclusion changes and more, newest first. Useful as evidence of actions taken (e.g. "show what was done about the threat on machine X"). |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
Latest Blog Posts
- Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)By Om-Shree-0709 on .mcpAgent IdentityOAuth 2.1
- Your AI Chatbot Just Exposed Your CEO's Salary to an InternBy Om-Shree-0709 on .Agent IdentityMCP SecurityOAuth Delegation
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/jamescash1976/sentinelone-mcp'
If you have feedback or need assistance with the MCP directory API, please join our Discord server