Skip to content

README: fix Quick-start (Docker) MCP dispatch arg (s1-secops-mcp -> sentinelone-mcp) - #81

Merged
marcorottigni-s1 merged 1 commit into
Sentinel-One:mainfrom
pmoses-s1:fix/readme-docker-dispatch
Jul 22, 2026
Merged

README: fix Quick-start (Docker) MCP dispatch arg (s1-secops-mcp -> sentinelone-mcp)#81
marcorottigni-s1 merged 1 commit into
Sentinel-One:mainfrom
pmoses-s1:fix/readme-docker-dispatch

Conversation

@pmoses-s1

Copy link
Copy Markdown
Contributor

The bundled ghcr.io/pmoses-s1/s1-mcps image dispatches the SentinelOne server as sentinelone-mcp (the verify command's serverInfo.name = "sentinelone-mcp-server" confirms this), but the Quick-start (Docker) config block and the terminal verify command passed s1-secops-mcp as the image arg, so following the README as written fails to start the server.

Two-line fix:

  • Quick-start (Docker) mcpServers config block: last image arg s1-secops-mcp -> sentinelone-mcp.
  • Terminal verify command: ... s1-mcps:1.2.3 s1-secops-mcp -> ... s1-mcps:1.2.3 sentinelone-mcp.

The client config key stays s1-secops-mcp, and the purple-mcp / virustotal-mcp dispatch args are unchanged.

The s1-mcps image dispatches the SentinelOne server as 'sentinelone-mcp'
(serverInfo.name = sentinelone-mcp-server), not 's1-secops-mcp'. Fixes the
quick-start config block's last arg and the terminal verify command. The client
config key stays 's1-secops-mcp'.

@marcorottigni-s1 marcorottigni-s1 left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Approved

@marcorottigni-s1
marcorottigni-s1 merged commit 16d77cf into Sentinel-One:main Jul 22, 2026
2 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants