Sophos Central Mcp

Sophos Central MCP Server

[Node.js] [License] [MCP Protocol] [Tools] [GitHub Stars]

[Build & Test] [npm] [MCP Registry]

For MSP/MSSP teams: Manage endpoint security, email threats, and firewall policy across all your Sophos tenants through natural language. Ask Claude to investigate an alert, isolate a host, run Live Discover queries, and correlate with XDR data — without leaving your AI workflow.

Overview

A Model Context Protocol (MCP) server for the Sophos Central API, enabling AI-powered security operations through Claude and other MCP-compatible clients. Designed for MSP/MSSP environments with Partner Super Admin credentials, it provides multi-tenant management across all customer tenants from a single server instance — covering endpoint protection, threat detection, Live Discover forensics, XDR hunting, email security, firewall management, and more.

Features

• 334 tools across 33 API domains — comprehensive Sophos Central API coverage
• Multi-tenant MSSP support — enumerate and target any customer tenant via Partner Super Admin credentials
• Endpoint isolation and investigation — isolate endpoints, check tamper protection, trigger scans
• Alert triage — list, filter, acknowledge, and action Sophos alerts across tenants
• Live Discover SQL queries — run real-time forensic SQL queries directly on managed endpoints
• XDR Data Lake hunting — historical threat hunting with SQL against the Sophos XDR data lake
• Threat detections — query, group, and count behavioral detections
• Case management — create and manage investigation cases end-to-end
• Email security — quarantine management, mailbox listing, post-delivery message clawback
• Firewall management — CRUD operations, group management, firmware upgrades
• DNS protection — location policies, custom domain allow/block lists
• SOC playbooks — built-in sophos_playbook_* tools for guided IR and threat hunting workflows
• Three transport modes — stdio (Claude Desktop), SSE, and Streamable HTTP (Claude Code)
• Automatic OAuth2 token management — token refresh with no manual intervention
• Regional routing — requests automatically routed to the correct data region (US, EU, CA, AU, JP, BR)

Prerequisites

• Node.js v18 or later (native fetch support required)
• npm v8 or later
• Sophos Central Partner Super Admin API credentials — see Configuration for how to create these

Installation

git clone https://github.com/rijul170/sophos-central-mcp.gitcd sophos-central-mcpnpm installnpm run build

Configuration

1. Create a .env file

cp .env.example .env

Edit .env with your credentials:

# RequiredSOPHOS_CLIENT_ID=your-client-id-hereSOPHOS_CLIENT_SECRET=your-client-secret-here
# Optional — transport mode: stdio | sse | streamable-http (default: stdio)MCP_TRANSPORT=stdio
# Optional — host for HTTP transports (default: 127.0.0.1)MCP_HOST=127.0.0.1
# Optional — port for HTTP transports (default: 3001)MCP_PORT=3001

2. Create API Credentials in Sophos Central

1. Log in to Sophos Central Partner Dashboard
2. Navigate to Settings & Policies → API Credentials Management
3. Click Add Credential
4. Set the role to Service Principal Super Admin
5. Copy the Client ID and Client Secret — the secret is displayed only once

Claude Code Integration (HTTP Mode)

HTTP mode is recommended for Claude Code — it supports concurrent sessions and does not require restarting the server between conversations.

Start the server:

MCP_TRANSPORT=streamable-http MCP_PORT=3001 node build/index.js

Or set MCP_TRANSPORT=streamable-http in your .env and run:

node build/index.js

Add to your Claude Code MCP configuration (.claude/settings.json or global settings):

{  "mcpServers": {    "sophos-mcp": {      "type": "http",      "url": "http://localhost:3001/mcp"    }  }}

A /health endpoint is available at http://localhost:3001/health for liveness checks.

Claude Desktop Integration (stdio Mode)

stdio mode is the standard transport for Claude Desktop. The server process is managed by Claude Desktop directly.

Add to your Claude Desktop MCP configuration (claude_desktop_config.json):

{  "mcpServers": {    "sophos-mcp": {      "command": "node",      "args": ["/path/to/sophos-central-mcp/build/index.js"],      "env": {        "SOPHOS_CLIENT_ID": "your-client-id",        "SOPHOS_CLIENT_SECRET": "your-client-secret"      }    }  }}

Replace /path/to/sophos-central-mcp with the absolute path to your cloned repository.

SSE Mode

SSE (Server-Sent Events) mode is available for legacy MCP clients that do not support Streamable HTTP.

MCP_TRANSPORT=sse MCP_PORT=3001 node build/index.js

The SSE endpoint is available at http://localhost:3001/sse.

Tool Domains

MSSP Multi-Tenant Support

The server is built around Sophos Partner Super Admin credentials, which have visibility across all managed customer tenants.

How it works:

1. On startup, the server authenticates to Sophos Central using your Partner credentials and discovers your organization type (partner or organization).
2. Use sophos_list_tenants (or sophos_list_org_tenants for organization accounts) to enumerate all managed tenants and their IDs.
3. Pass the tenantId parameter to any tenant-scoped tool to target a specific customer environment.
4. All API calls are automatically routed to the correct regional endpoint (US, EU, CA, AU, JP, BR) based on the tenant's data residency.

Example workflow:

1. sophos_list_tenants          → get all tenant IDs and names2. sophos_list_alerts           → pass tenantId for a specific customer3. sophos_isolate_endpoint      → isolate an endpoint in that tenant4. sophos_live_discover_run_query → run forensic SQL on the isolated host

SOC Playbooks

The server ships with five built-in playbook tools that provide structured, step-by-step guidance for common SOC workflows. These are designed to be invoked at the start of an investigation to orient the response.

SOC Quick Start

Once the server is connected to Claude, you can use natural language to drive security operations. Example prompts:

Alert triage:

"List all critical and high severity open alerts for tenant <tenant-id> from the last 24 hours, grouped by type."

Endpoint investigation:

"Isolate endpoint <hostname> in tenant <tenant-id>, then run a Live Discover SQL query to list all running processes and active network connections."

XDR threat hunting:

"Run an XDR Data Lake query against tenant <tenant-id> to find any PowerShell executions with encoded commands in the last 7 days."

MSSP overview:

"Enumerate all my managed tenants, then show me any tenants with open critical alerts."

Email security:

"Show me all quarantined messages for tenant <tenant-id> in the last 48 hours and release any flagged as false positives."

Development

# Run with hot-reload (no build step required)npm run dev
# Build TypeScript to JavaScriptnpm run build
# Run the built servernpm start
# Inspect tools interactively with MCP Inspectornpx @modelcontextprotocol/inspector node build/index.js

Project Structure

src/├── index.ts                          # Entry point — transport setup, registers all 33 modules├── config.ts                         # Environment variable validation├── auth/│   └── auth-manager.ts               # OAuth2 token management with auto-refresh├── client/│   ├── sophos-client.ts              # HTTP client (retry, rate limiting, backoff)│   └── tenant-router.ts             # Tenant → regional API host mapping├── tools/                            # 33 tool files, 334 tools total│   ├── auth-tools.ts                 # 2 tools│   ├── partner-tools.ts              # 23 tools│   ├── organization-tools.ts         # 2 tools│   ├── endpoint-tools.ts             # 26 tools│   ├── group-tools.ts                # 8 tools│   ├── policy-tools.ts               # 7 tools│   ├── alert-tools.ts                # 5 tools│   ├── detections-tools.ts           # 7 tools│   ├── siem-tools.ts                 # 2 tools│   ├── xdr-tools.ts                  # 10 tools│   ├── live-discover-tools.ts        # 11 tools│   ├── firewall-tools.ts             # 20 tools│   ├── dns-protection-tools.ts       # 15 tools│   ├── email-tools.ts                # 31 tools│   ├── directory-tools.ts            # 15 tools│   ├── settings-tools.ts             # 16 tools│   ├── allowed-blocked-tools.ts      # 12 tools│   ├── exploit-mitigation-tools.ts   # 8 tools│   ├── ips-exclusion-tools.ts        # 10 tools│   ├── tenant-admin-tools.ts         # 14 tools│   ├── account-health-tools.ts       # 4 tools│   ├── cases-tools.ts                # 9 tools│   ├── software-tools.ts             # 9 tools│   ├── audit-events-tools.ts         # 2 tools│   ├── business-automation-tools.ts  # 3 tools│   ├── licensing-tools.ts            # 2 tools│   ├── mobile-tools.ts               # 38 tools│   ├── switch-tools.ts               # 3 tools│   ├── wifi-tools.ts                 # 3 tools│   ├── cloud-security-tools.ts       # 6 tools│   ├── user-activity-tools.ts        # 2 tools│   ├── account-management-tools.ts   # 4 tools│   └── playbook-tools.ts             # 5 tools└── types/    └── sophos-types.ts               # TypeScript interfaces for all Sophos API types

Security Considerations

• Read-only mode — set SOPHOS_MCP_READONLY=true to register only read tools at startup. Write and destructive tools are never exposed to the AI client, regardless of what is asked. XDR Data Lake and detections queries stay available (they are read analytics); Live Discover does not (it executes osquery on managed endpoints).

• Destructive operation gating — even with writes enabled, destructive tools (endpoint isolation, deletes, email clawback, Live Discover execution, firmware upgrades, ...) are suppressed by default. Arm them explicitly via SOPHOS_MCP_ALLOW_DESTRUCTIVE. The recommended approach is a comma-separated list of specific tool names rather than true:

  bash

  # Enable only endpoint isolation for IR workflowsSOPHOS_MCP_ALLOW_DESTRUCTIVE=sophos_isolate_endpoint,sophos_deisolate_endpoint

• Tool annotations — every tool carries MCP readOnlyHint/destructiveHint annotations so compliant clients can apply their own confirmation policies.

• Credential handling — API credentials are read from environment variables at startup and are never logged or transmitted except to the Sophos authentication endpoint. Do not commit .env files to source control — .env is listed in .gitignore.

• Partner Super Admin scope — these credentials have read/write access across all managed tenants. Treat them with the same care as privileged service account credentials. Rotate them immediately if compromised.

• Read-only operations where possible — where your use case only requires visibility (alert triage, threat hunting, reporting), consider creating a separate credential with a more restricted role. Partner Super Admin is required only for write operations (isolation, policy changes, user management).

• Network binding — HTTP transports default to 127.0.0.1. Do not expose the MCP server port publicly. If you need remote access, put it behind an authenticated reverse proxy or use a VPN.

• Audit trail — all Sophos API calls made through this server are logged in Sophos Central's audit events, attributable to the API credential used.

Related MCP Servers

These three servers cover complementary layers of a security stack — network/log (AlertLogic), endpoint protection (Sophos), and EDR/threat intel (CrowdStrike). Use them together for full-stack AI-powered SOC operations.

License

MIT