SentinelOne MCP — Claude Code MCP server: install
This MCP server connects agents to the SentinelOne API and adds an offline SQLite store with cross-entity analytics.
Open on GitHubWhat SentinelOne MCP does
SentinelOne MCP exposes SentinelOne v2.1 management endpoints to an AI agent. It also maintains an offline SQLite store and derives views for fleet health, threat triage, blast radius, and drift. These cross-entity views are not available in the console.
The server supports Claude Code, Codex, Cursor, GitHub Copilot, Windsurf (Devin Desktop), Cline, and Zed. It ships with sentinelone-cli, while agents that read SKILL.md can discover the skill from that file. SentinelOne authentication is required.
Do not start HTTP mode in this build, including on localhost; use the default stdio transport. MCP tools can make changes with your credentials, so a remote tunnel should be shut down.
What it helps with
- query SentinelOne management endpoints
- store SentinelOne data in local SQLite
- inspect the health of an endpoint fleet
- trace a threat’s blast radius
- spot drift across SentinelOne entities
Example prompts for the agent
- Show the SentinelOne fleet health and flag affected devices.
- Triage this SentinelOne threat and map its blast radius.
- Compare SentinelOne entities and report any drift.
How to install SentinelOne MCP
Install
The MCP registry has no launch command for it: see the repository README
Step by step, with commands for each platform: How to add an MCP server to Claude Code, Codex, Cursor, VS Code, Gemini CLI and more
Questions about SentinelOne MCP
How do I install SentinelOne MCP in Claude Code?
Add the marketplace with /plugin marketplace add Servosity/msp-skills, then install the plugin with /plugin install sentinelone@msp-skills.
What does SentinelOne MCP do?
It connects an agent to SentinelOne v2.1 management endpoints, keeps an offline SQLite store, and provides analytics for fleet health, threats, blast radius, and drift.
Which transport should SentinelOne MCP use?
Use the default stdio transport. HTTP mode must not run, even on localhost, because this build lacks request-size and execution-time limits for that mode.