Prototype · Preview: every server in the official registry, synced every 30 minutes. Sign in with Google to write reviews.Prototype · updated every 30 min
PopNx MCPMCP servers for people who use AI · explained in plain words Sign in

Sophos MCP

by Aaronjacobs000version 0.13.4i★ 19iRuns on your computerRepository ↗
Registry nameio.github.Aaronjacobs000/sophos-mcp

How to install

What it does

Unofficial, not a Sophos product. MCP server for the Sophos Fusion (formerly Sophos Central) APIs.

  • Connects Runs on your computer
  • Account or key Needs SOPHOS_CLIENT_ID, SOPHOS_CLIENT_SECRET
  • Category Other

Why it ranks here

Lists are ordered by a usage score (out of 100) built from these parts

Popularity21/80GitHub stars or weekly downloads: the larger counts 60, the smaller 20
Freshness12/12Full marks for a release or code change within 30 days
Still answering0/8The cloud endpoint answered at the last check
Usage score33/100

Quality: Passed 3/3 basic checks (shown, not used for ordering) · Momentum: No data yet (Used only on the Trending tab)

Install

Pick the AI app you use, then copy the settings.

Let your AI install it with one sentence

Please install Sophos MCP. Follow https://mcp.popnx.com/i/aaronjacobs000-sophos-mcp.md, show me the commands and wait for my OK before running them.

Paste it into an AI that can work on your computer (such as Claude Code or Cursor). It reads our steps, shows you the commands and waits for your OK. No key, no sign-up. · See the full text your AI reads

Passed 3/3 checks · Runs on your computer · ✓ Commands checked Nov 21, 2026

First: which AI do you use?

Pick your app and the steps appear below.

Works with Claude, with some setup first

You need a Sophos MCP key (create it on the maker’s site) · Install Node.js on your computer first (one time) · Only the Claude desktop app (Windows or Mac), not the web or phone

Let AI install it

Copy this message into a Claude chat. The AI checks your computer, tells you which file it will change, and waits for your OK every time.

Please install the MCP server Sophos MCP for Claude on this computer, in this order: 1) Check Node.js with node -v. If it is missing, tell me to install it from https://nodejs.org/en/download; do not install it yourself. 2) Use only this config (already checked by PopNx MCP): { "mcpServers": { "sophos": { "command": "npx", "args": [ "-y", "sophos-central-mcp-server" ], "env": { "SOPHOS_CLIENT_ID": "your-value", "SOPHOS_CLIENT_SECRET": "your-value" } } } } 3) Tell me the full path of the file you will change, or the command you will run, and wait for my OK. 4) For SOPHOS_CLIENT_ID, SOPHOS_CLIENT_SECRET, leave "your-value" in place and tell me to paste the real value myself into the file or the app’s field. Never ask me to type a key in chat. 5) Do what we agreed, then check that the Sophos MCP tools really show up.

This message has no key in it. If a key is needed, the AI will ask you to paste it yourself into the file or the app’s field.

  1. Install Node.js (if you don’t have it)

    Already installed? Check first · Open Terminal, type this command and press Enter

    node -v
    • A version number such as v26.13.1 = installed, skip this step
    • "command not found" (on Windows: "is not recognized") = not installed yet, or installed but Terminal needs to be closed and reopened
    How to open Terminal

    Mac: press ⌘ + Space, type Terminal, press Enter

    Windows: open Start, type Windows PowerShell, then Open

    Not installed: Open the official download page, pick the LTS version and the click-through installer: .pkg on Mac · .msi on Windows. Double-click and follow it to the end. No curl command needed

    Open the Node.js download page ↗

    When it’s done, close Terminal, open it again and run the same command. You should see a version number: node -v

    Install once; it works for everything that needs Node.js

  2. Sign up and create a Sophos MCP key

    Open the maker’s site, sign up and create an API key for the next step. Check the maker’s site for pricing and free plans.

    How to get a key is in the maker’s README below

  3. Open the Claude desktop app’s settings file

    SettingsDeveloperEdit Config

  4. Paste these settings and save the file

    {
      "mcpServers": {
        "sophos": {
          "command": "npx",
          "args": [
            "-y",
            "sophos-central-mcp-server"
          ],
          "env": {
            "SOPHOS_CLIENT_ID": "your-value",
            "SOPHOS_CLIENT_SECRET": "your-value"
          }
        }
      }
    }

    Paste the key only into the app’s field, never into a chat or to anyone

  5. Quit Claude and open it again

  6. Try it

    Use Sophos MCP and tell me what you can do for me, then show me one thing

    ✓ If Claude says it is using Sophos MCP or shows a Sophos MCP tool in the answer, you are connected

1 optional setting(s) (works without them)

The command above works without these. Add them only if you want to change something, following the maker’s description.

  • TRANSPORT Fixed to stdio. The server defaults to streamable HTTP without it. · default stdio

Descriptions are as written by the maker.

Menu names checked against Anthropic’s help page on Nov 11, 2026 · your screen may differ slightly by app version

ChatGPT cannot connect Sophos MCP yet

Sophos MCP runs on your computer, but ChatGPT can only connect servers that run on the web

What you can do instead

A · Use an app that can connect Sophos MCP

  • You need a Sophos MCP key (create it on the maker’s site) · Install Node.js on your computer first (one time) · Only the Claude desktop app (Windows or Mac), not the web or phone
  • You need a Sophos MCP key (create it on the maker’s site) · Install Node.js on your computer first (one time)
  • You need a Sophos MCP key (create it on the maker’s site) · Install Node.js on your computer first (one time)
  • You need a Sophos MCP key (create it on the maker’s site) · Install Node.js on your computer first (one time)

B · Others in Other that work with ChatGPT

Picked from the most used in the same category, only ones that connect by address with no key

Works with Claude Code, with some setup first

You need a Sophos MCP key (create it on the maker’s site) · Install Node.js on your computer first (one time)

Let AI install it

Copy this message into a Claude Code chat. The AI checks your computer, tells you which file it will change, and waits for your OK every time.

Please install the MCP server Sophos MCP for Claude Code on this computer, in this order: 1) Check Node.js with node -v. If it is missing, tell me to install it from https://nodejs.org/en/download; do not install it yourself. 2) Use only this config (already checked by PopNx MCP): claude mcp add --scope user sophos --env SOPHOS_CLIENT_ID=your-value --env SOPHOS_CLIENT_SECRET=your-value -- npx -y sophos-central-mcp-server 3) Tell me the full path of the file you will change, or the command you will run, and wait for my OK. 4) For SOPHOS_CLIENT_ID, SOPHOS_CLIENT_SECRET, leave "your-value" in place and tell me to paste the real value myself into the file or the app’s field. Never ask me to type a key in chat. 5) Do what we agreed, then check that the Sophos MCP tools really show up.

This message has no key in it. If a key is needed, the AI will ask you to paste it yourself into the file or the app’s field.

  1. Install Node.js (if you don’t have it)

    Already installed? Check first · Open Terminal, type this command and press Enter

    node -v
    • A version number such as v26.13.1 = installed, skip this step
    • "command not found" (on Windows: "is not recognized") = not installed yet, or installed but Terminal needs to be closed and reopened
    How to open Terminal

    Mac: press ⌘ + Space, type Terminal, press Enter

    Windows: open Start, type Windows PowerShell, then Open

    Not installed: Open the official download page, pick the LTS version and the click-through installer: .pkg on Mac · .msi on Windows. Double-click and follow it to the end. No curl command needed

    Open the Node.js download page ↗

    When it’s done, close Terminal, open it again and run the same command. You should see a version number: node -v

    Install once; it works for everything that needs Node.js

  2. Sign up and create a Sophos MCP key

    Open the maker’s site, sign up and create an API key for the next step. Check the maker’s site for pricing and free plans.

    How to get a key is in the maker’s README below

  3. Open Terminal

    Mac: press Command+Space and type Terminal · Windows: open PowerShell

  4. Paste this command and press Enter

    claude mcp add --scope user sophos --env SOPHOS_CLIENT_ID=your-value --env SOPHOS_CLIENT_SECRET=your-value -- npx -y sophos-central-mcp-server

    Replace “your-value” with your key before pressing Enter

    Paste the key only into the app’s field, never into a chat or to anyone

  5. Type /mcp in Claude Code

    You should see Sophos MCP listed as connected

  6. Try it

    Use Sophos MCP and tell me what you can do for me, then show me one thing

    ✓ If Claude Code says it is using Sophos MCP or shows a Sophos MCP tool in the answer, you are connected

1 optional setting(s) (works without them)

The command above works without these. Add them only if you want to change something, following the maker’s description.

  • TRANSPORT Fixed to stdio. The server defaults to streamable HTTP without it. · default stdio

Descriptions are as written by the maker.

Menu names checked against Anthropic’s help page on Nov 11, 2026 · your screen may differ slightly by app version

Works with Cursor, with some setup first

You need a Sophos MCP key (create it on the maker’s site) · Install Node.js on your computer first (one time)

Let AI install it

Copy this message into a Cursor chat. The AI checks your computer, tells you which file it will change, and waits for your OK every time.

Please install the MCP server Sophos MCP for Cursor on this computer, in this order: 1) Check Node.js with node -v. If it is missing, tell me to install it from https://nodejs.org/en/download; do not install it yourself. 2) Use only this config (already checked by PopNx MCP): { "mcpServers": { "sophos": { "command": "npx", "args": [ "-y", "sophos-central-mcp-server" ], "env": { "SOPHOS_CLIENT_ID": "your-value", "SOPHOS_CLIENT_SECRET": "your-value" } } } } 3) Tell me the full path of the file you will change, or the command you will run, and wait for my OK. 4) For SOPHOS_CLIENT_ID, SOPHOS_CLIENT_SECRET, leave "your-value" in place and tell me to paste the real value myself into the file or the app’s field. Never ask me to type a key in chat. 5) Do what we agreed, then check that the Sophos MCP tools really show up.

This message has no key in it. If a key is needed, the AI will ask you to paste it yourself into the file or the app’s field.

  1. Install Node.js (if you don’t have it)

    Already installed? Check first · Open Terminal, type this command and press Enter

    node -v
    • A version number such as v26.13.1 = installed, skip this step
    • "command not found" (on Windows: "is not recognized") = not installed yet, or installed but Terminal needs to be closed and reopened
    How to open Terminal

    Mac: press ⌘ + Space, type Terminal, press Enter

    Windows: open Start, type Windows PowerShell, then Open

    Not installed: Open the official download page, pick the LTS version and the click-through installer: .pkg on Mac · .msi on Windows. Double-click and follow it to the end. No curl command needed

    Open the Node.js download page ↗

    When it’s done, close Terminal, open it again and run the same command. You should see a version number: node -v

    Install once; it works for everything that needs Node.js

  2. Sign up and create a Sophos MCP key

    Open the maker’s site, sign up and create an API key for the next step. Check the maker’s site for pricing and free plans.

    How to get a key is in the maker’s README below

  3. Click this button to open Cursor

    Open in Cursor

    Cursor asks you to confirm; click Install

  4. Fill in your key

    In the Sophos MCP settings, SOPHOS_CLIENT_ID, SOPHOS_CLIENT_SECRET is empty; add your key and save

    Paste the key only into the app’s field, never into a chat or to anyone

  5. Open the AI chat in Cursor in Agent mode

  6. Try it

    Use Sophos MCP and tell me what you can do for me, then show me one thing

    ✓ If Cursor says it is using Sophos MCP or shows a Sophos MCP tool in the answer, you are connected

1 optional setting(s) (works without them)

The command above works without these. Add them only if you want to change something, following the maker’s description.

  • TRANSPORT Fixed to stdio. The server defaults to streamable HTTP without it. · default stdio

Descriptions are as written by the maker.

Menu names checked against Cursor’s help page on Nov 11, 2026 · your screen may differ slightly by app version

Works with VS Code, with some setup first

You need a Sophos MCP key (create it on the maker’s site) · Install Node.js on your computer first (one time)

Let AI install it

Copy this message into a VS Code chat. The AI checks your computer, tells you which file it will change, and waits for your OK every time.

Please install the MCP server Sophos MCP for VS Code on this computer, in this order: 1) Check Node.js with node -v. If it is missing, tell me to install it from https://nodejs.org/en/download; do not install it yourself. 2) Use only this config (already checked by PopNx MCP): { "servers": { "sophos": { "type": "stdio", "command": "npx", "args": [ "-y", "sophos-central-mcp-server" ], "env": { "SOPHOS_CLIENT_ID": "your-value", "SOPHOS_CLIENT_SECRET": "your-value" } } } } 3) Tell me the full path of the file you will change, or the command you will run, and wait for my OK. 4) For SOPHOS_CLIENT_ID, SOPHOS_CLIENT_SECRET, leave "your-value" in place and tell me to paste the real value myself into the file or the app’s field. Never ask me to type a key in chat. 5) Do what we agreed, then check that the Sophos MCP tools really show up.

This message has no key in it. If a key is needed, the AI will ask you to paste it yourself into the file or the app’s field.

  1. Install Node.js (if you don’t have it)

    Already installed? Check first · Open Terminal, type this command and press Enter

    node -v
    • A version number such as v26.13.1 = installed, skip this step
    • "command not found" (on Windows: "is not recognized") = not installed yet, or installed but Terminal needs to be closed and reopened
    How to open Terminal

    Mac: press ⌘ + Space, type Terminal, press Enter

    Windows: open Start, type Windows PowerShell, then Open

    Not installed: Open the official download page, pick the LTS version and the click-through installer: .pkg on Mac · .msi on Windows. Double-click and follow it to the end. No curl command needed

    Open the Node.js download page ↗

    When it’s done, close Terminal, open it again and run the same command. You should see a version number: node -v

    Install once; it works for everything that needs Node.js

  2. Sign up and create a Sophos MCP key

    Open the maker’s site, sign up and create an API key for the next step. Check the maker’s site for pricing and free plans.

    How to get a key is in the maker’s README below

  3. Click this button to open VS Code

    Open in VS Code

    VS Code asks you to confirm; click Install

  4. Fill in your key

    In the Sophos MCP settings, SOPHOS_CLIENT_ID, SOPHOS_CLIENT_SECRET is empty; add your key and save

    Paste the key only into the app’s field, never into a chat or to anyone

  5. Open the AI chat in VS Code in Agent mode

  6. Try it

    Use Sophos MCP and tell me what you can do for me, then show me one thing

    ✓ If VS Code says it is using Sophos MCP or shows a Sophos MCP tool in the answer, you are connected

1 optional setting(s) (works without them)

The command above works without these. Add them only if you want to change something, following the maker’s description.

  • TRANSPORT Fixed to stdio. The server defaults to streamable HTTP without it. · default stdio

Descriptions are as written by the maker.

Menu names checked against VS Code’s help page on Nov 11, 2026 · your screen may differ slightly by app version

Other apps that use MCP, such as Windsurf, Zed or Gemini CLI, each add servers differently. See how in the app list.

See every app that uses MCP →

JSON settings are under “For developers” below

Stuck? Ask people who use Sophos MCP💬 Discussion →
For developers: Terminal commands and JSON settings

Installed on your computer

Claude Code

claude mcp add --scope user sophos --env SOPHOS_CLIENT_ID=your-value --env SOPHOS_CLIENT_SECRET=your-value -- npx -y sophos-central-mcp-server

Claude Desktop (claude_desktop_config.json)

{
  "mcpServers": {
    "sophos": {
      "command": "npx",
      "args": [
        "-y",
        "sophos-central-mcp-server"
      ],
      "env": {
        "SOPHOS_CLIENT_ID": "your-value",
        "SOPHOS_CLIENT_SECRET": "your-value"
      }
    }
  }
}

Cursor (~/.cursor/mcp.json)

{
  "mcpServers": {
    "sophos": {
      "command": "npx",
      "args": [
        "-y",
        "sophos-central-mcp-server"
      ],
      "env": {
        "SOPHOS_CLIENT_ID": "your-value",
        "SOPHOS_CLIENT_SECRET": "your-value"
      }
    }
  }
}

VS Code (mcp.json)

{
  "servers": {
    "sophos": {
      "type": "stdio",
      "command": "npx",
      "args": [
        "-y",
        "sophos-central-mcp-server"
      ],
      "env": {
        "SOPHOS_CLIENT_ID": "your-value",
        "SOPHOS_CLIENT_SECRET": "your-value"
      }
    }
  }
}

Values you fill in

  • SOPHOS_CLIENT_ID secret required env
    Client ID of a Sophos Central API credential (tenant, partner or organisation).
  • SOPHOS_CLIENT_SECRET secret required env
    Client secret that pairs with the client ID.
  • TRANSPORT env
    Fixed to stdio. The server defaults to streamable HTTP without it.

Descriptions are as written by the maker.

These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.

At a glance

Downloads per weeki
461/wk
Connection
Runs on your computer
Latest versioni
0.13.4
Categoryi
Other
Published to registryi
Nov 21, 2026
Code last changedi
Nov 21, 2026
Maker
Aaronjacobs000
Packages
npm: sophos-central-mcp-server
Registry status
Active

Which apps can use it

Based on how this server connects and on each app’s own docs, checked Nov 10, 2026.

Run on your computer in

ClaudeGooseLM StudioMsty StudioCherry StudioCursorVS Code + GitHub CopilotVisual StudioWindsurf (Devin Desktop)ZedKiroClineContinueJetBrains AI AssistantClaude CodeCodex CLIGemini CLIOpenCodenodecodeWarpLibreChatRaycast

All apps, with pros and cons →

Related guides

What it can do

Runs on your computer; the tool list appears in your AI app after you install it.

Basic checksi

We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 21, 2026

  • ✓ Pass

    Maker matches the repo

    The registry name was verified with the GitHub account Aaronjacobs000, which owns the repo

  • ✓ Pass

    Still maintained

    Code last changed today

  • ✓ Pass

    Has a licence

    Uses MIT

  • – Not applicable

    Endpoint responds

    This one runs on your computer; there is no internet endpoint

  • – Not applicable

    Sign-in with OAuth

    Runs on your computer and uses local settings instead

  • … Not checked yet

    No hidden instructions in tool descriptions

    Runs on your computer; we can only read tool lists from internet endpoints

Published vulnerabilities (OSV.dev)

No entries on OSV.dev for sophos-central-mcp-server@0.13.4

Checks only this package version, not every dependency · checked Nov 21, 2026

What we check → · JSON

Makers: ask for a re-check or report wrong info
For makers: add a badge to your README

If you made this, paste this code into your README. The badge links back to this page.

[![Featured on PopNx MCP](https://mcp.popnx.com/badge/aaronjacobs000-sophos-mcp.svg)](https://mcp.popnx.com/en/servers/aaronjacobs000-sophos-mcp)

Discussion

Ask, share a tip or report that it does not work. Sorted by what people marked helpful.

No posts yet. Be the first to ask or share.

Posts here are written by users, not the PopNx team.

Sign in to post

User reviews

No reviews yet

Sign in to write a review

Compared with others in Otheri

  • More stars than 97% of the other 21107 servers in this category
  • Published to the registry more recently than 98% of the other 21107 servers in this category
  • Basic checks equal to or better than 99% of the other 21107 servers in this category

Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.

Common questions

Is Sophos MCP safe?

It passed 3 of 3 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.

What keys or codes does it need?

You need to fill in: SOPHOS_CLIENT_ID, SOPHOS_CLIENT_SECRET

Does it run on my computer or in the cloud?

It runs on your computer. Your AI app starts it when needed, and data does not pass through the maker’s servers (unless it calls an online service itself).

Is it still maintained?

The GitHub repo last changed today, and the latest version (0.13.4) reached the registry today.

Which apps can use it?

Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. You also need Node.js on your computer.

What can I use instead?

In the same category: World Monitor, openstatus, Oh My Posh Validator, Strata, Jitsu

Similar alternatives

Same category, other makers, commands already checked. Official ones first, then by stars.

Reading a card:↓ Downloads per weeki★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi

World Monitor

Real-time global intelligence on conflict, markets, energy, trade, shipping and cyber. 100 tools.

by koala73Widely used★ 91KUpdated 5 days ago

Runs in the cloud✓ service owner · worldmonitor.app

openstatus

Manage monitors, status pages, incidents and maintenances in your openstatus workspace.

by openstatusHQWidely used★ 9.3KUpdated 2 months ago

Runs in the cloud✓ service owner · openstatus.dev

Oh My Posh Validator

Validate oh-my-posh configurations and segment snippets against the official schema.

by JanDeDobbeleerWidely used★ 23.8K Stars for the whole repoUpdated 32 days ago

Runs in the cloud✓ service owner · ohmyposh.dev

Strata

MCP server for progressive tool usage at any scale (see https://klavis.ai)

by Klavis-AIGrowing★ 5.8KUpdated 14 months ago

Runs in the cloudRepo archived✓ klavis.ai

Jitsu

Manage Jitsu data pipelines: destinations, streams, connections, functions, live events.

by jitsucomWidely used★ 5.1KUpdated 4 months ago

Runs in the cloud✓ service owner · jitsu.com
Compared with similar ones
This one
Sophos MCP
World MonitoropenstatusOh My Posh ValidatorStrataJitsu
Runs whereInstalls on your computerRuns in the cloud, nothing to installRuns in the cloud, nothing to installRuns in the cloud, nothing to installRuns in the cloud, nothing to installRuns in the cloud, nothing to install
Needs a keyYesNoNoNoNoNo
Add with + in ClaudeNoNoNoNoNoNo
Basic checks3/34/44/44/41/44/4
LicenseMITAGPL-3.0AGPL-3.0MITApache-2.0MIT
PriceNo cost listed in the registryNo cost listed in the registryNo cost listed in the registryNo cost listed in the registryNo cost listed in the registryNo cost listed in the registry

README from the maker

Open the README

Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.

Sophos Fusion MCP Server (formerly Sophos Central)

Unofficial project, not from Sophos. This is a personal project by an individual. It is

not an official Sophos product and it is not built, endorsed, supported, or warranted by

Sophos. It calls the public Sophos APIs using credentials you supply. Use it at your own

risk, and raise problems as issues on this repository rather than with Sophos support.

MCP (Model Context Protocol) server for the Sophos Fusion and Sophos Central APIs. Supports partner, organisation, and single-tenant credential types with automatic region routing. 360 tools covering 25 Sophos API namespaces: the Sophos Central REST APIs plus the Sophos Fusion GraphQL APIs (sophos_fusion_*). Install it as a Claude Desktop extension (.mcpb), run it with npx, or host it yourself over streamable HTTP.

The npm package, the .mcpb bundle and the binaries keep the sophos-central-mcp-server name so existing installs update in place.

Prerequisites

You need these before any of the install options below.

Sophos Central API credentials

Every install method needs a Client ID and Client Secret. The same credential authorises both the Sophos Central REST tools and the Sophos Fusion GraphQL tools; there is no second credential. The credential type decides what the server can see:

  • Tenant-level: In Sophos Central, go to Settings > API Credentials Management and create a new credential. The server operates on that one tenant.
  • Partner-level: In the Sophos Partner Dashboard, create API credentials under Settings > API Credentials. The server can query every tenant the partner manages.
  • Organisation-level: In Sophos Central Enterprise, use Global Settings > API Credentials Management. Same cross-tenant behaviour as partner credentials.
Node.js 22 or later (npm and self-hosted installs only)

The .mcpb bundle for Claude Desktop does not need Node.js on your machine: Claude Desktop ships its own Node.js runtime and the bundle carries the server and all of its dependencies. Install Node.js 22+ only if you use the Claude Code or self-hosted options.

If you run the server in HTTP mode, use Node.js 22.23.4, 24.22.1, 26.12.1 or later, which fix the Brotli decoder bug CVE-2026-111497.

Install

Pick one:

OptionBest forNeeds Node.js?
Claude Desktop extension (.mcpb)Claude Desktop users who want a two-minute installNo
Claude CodeTerminal use with Claude CodeYes
Self-hosted with npmRunning the server yourself for any MCP client, over streamable HTTP or stdioYes
Option 1: Claude Desktop extension (.mcpb, recommended)

The .mcpb file is an MCP Bundle: a zip containing the built server, its production dependencies, and a manifest that tells Claude Desktop how to run it and which settings to ask for. No terminal and no config file edits.

  1. Download sophos-central-mcp-server- .mcpb from the latest GitHub release.
  2. Open the file with Claude Desktop. Double-clicking it works on macOS and Windows. You can also go to Settings > Extensions > Advanced settings, find the Extension Developer section, click Install Extension... and pick the file.
  3. Claude Desktop shows the extension details and asks for your Sophos Central Client ID and Client Secret. Both fields are marked sensitive in the manifest, so Claude Desktop keeps them in the operating system's secure storage instead of a config file.
  4. Click Install, make sure the extension is enabled, then start a new chat. The sophos_* tools are available straight away.

To update, download the newer .mcpb and install it the same way. To remove it, open Settings > Extensions and uninstall the extension.

To change the credentials later, open Settings > Extensions and click this extension. The Sophos Central Client ID and Client Secret fields are editable there. They are stored in the operating system's secure storage and show masked, so you replace a value rather than read the old one back. The server reads them at startup, so toggle the extension off and on, or restart Claude Desktop, if a change does not take effect.

The bundle runs the server in stdio mode and sets TRANSPORT=stdio for you. Which tools you get depends on the credential type, exactly as with the other install options: partner and organisation credentials unlock the cross-tenant tools, tenant credentials do not.

Option 2: Claude Code

Requires Node.js. Run this once in your terminal. The -e flags save the credentials permanently to Claude Code's MCP config so you don't need to re-export them each session:

macOS / Linux:

claude mcp add sophos-central \

-e SOPHOS_CLIENT_ID="your-client-id" \ -e SOPHOS_CLIENT_SECRET="your-client-secret" \ -e TRANSPORT="stdio" \ -- npx -y sophos-central-mcp-server

Windows (Command Prompt):

claude mcp add sophos-central ^

-e SOPHOS_CLIENT_ID="your-client-id" ^ -e SOPHOS_CLIENT_SECRET="your-client-secret" ^ -e TRANSPORT="stdio" ^ -- cmd /c npx -y sophos-central-mcp-server

Option 3: Self-hosted with npm (streamable HTTP or stdio)

Use this when you want to run the server yourself, on a workstation, a jump box, or in a container, for any MCP client that speaks streamable HTTP or can spawn a stdio process. Nothing here depends on the .mcpb bundle.

Install from npm:

npm install -g sophos-central-mcp-server

Or from source:

git clone https://github.com/Aaronjacobs000/sophos-mcp.git

cd sophos-mcp npm install npm run build

Configure. Either export the variables in your shell or put them in a .env file in the directory you start the server from. The full table is under Configuration.

SOPHOS_CLIENT_ID=your-client-id

SOPHOS_CLIENT_SECRET=your-client-secret PORT=3100 TRANSPORT=http

Run:

sophos-central-mcp      # global npm install

npm start # from a source checkout

With TRANSPORT=http (the default) the server listens on http://127.0.0.1:3100/mcp (MCP_HTTP_HOST and PORT change that) and answers GET /health with {"status":"ok","server":"sophos-central-mcp-server"}. The MCP endpoint is stateless: every request gets a fresh server and transport, so concurrent tool calls work. Point any streamable HTTP client at it, for example Claude Code:

claude mcp add --transport http sophos-central http://127.0.0.1:3100/mcp

With TRANSPORT=stdio the server speaks MCP over stdin/stdout and is meant to be spawned by the client, which is what Options 1 and 2 do for you.

By default the HTTP server binds to 127.0.0.1 and has no authentication. It refuses any request with a browser Origin other than localhost, 127.0.0.1, [::1] or one listed in MCP_ALLOWED_ORIGINS, so a web page cannot drive it by cross-site POST or DNS rebinding. MCP clients that are not browsers send no Origin, so this does not affect them, on this machine or another.

Using it from other machines

To let agents on other machines use the server:

  1. Make a token, for example openssl rand -hex 32.
  2. Start the server listening on the network, with the token:
   MCP_HTTP_HOST=0.0.0.0 MCP_HTTP_TOKEN=<token> TRANSPORT=http npm start

0.0.0.0 listens on every interface. To listen on one only, use that interface's address, such as a LAN or Tailscale IP.

  1. Point each client at http:// :3100/mcp and have it send Authorization: Bearer . In Claude Code:
   claude mcp add --transport http sophos-central http://<server>:3100/mcp --header "Authorization: Bearer <token>"

Every /mcp request without the right token gets a 401. /health stays open. Without a token, anyone who can reach the port can use every tool with your Sophos credentials, and the server prints a warning at startup saying so.

Plain HTTP sends the token and tool results in clear text. On any network you don't fully trust, encrypt it: TLS through a reverse proxy (Caddy or nginx, say), or reach the server over Tailscale.

A browser based MCP client on another machine sends an Origin and is refused until you add that origin to MCP_ALLOWED_ORIGINS. Agents and CLI clients need nothing there.

Build the .mcpb yourself (maintainers)

The bundle is produced by scripts/build-mcpb.mjs using the mcpb CLI, which is a dev dependency. From a source checkout:

npm install

npm run build:mcpb

The script:

  1. Compiles TypeScript to dist/ (via npm run build).
  2. Rewrites manifest.json so its version matches package.json and its tools list matches every registerTool call in src/tools/. Commit the result. The manifest in git is always the one that was last built.
  3. Validates the manifest with mcpb validate.
  4. Stages dist/, package.json, LICENSE, and manifest.json in build/mcpb/ and runs npm ci --omit=dev there, so only production dependencies are bundled. .mcpbignore adds a few exclusions on top of the CLI's defaults.
  5. Packs the staging directory into release/sophos-central-mcp-server- .mcpb.

build/ and release/ are git-ignored. To inspect a bundle without installing it, npx mcpb info release/ .mcpb prints its size and signature state, and npx mcpb unpack release/ .mcpb extracts it. Signing is optional; npx mcpb sign --self-signed release/ .mcpb adds a self-signed signature if you want one.

Tests (maintainers)
npm test

Builds, then runs the node:test suites in test/ with fetch stubbed: the Fusion GraphQL transport (including the HTTP 200 with errors case), the QL builder, the reference-data cache, and the path-keyed retry for the intermittent case-write fault, the migration guard, the policy assignment and web profile writes (body shapes, refusals, target lookups and read-back) against an in-memory policy store, the no-retry rule for a POST or mutation after a 5xx, the read-modify-write and PATCH update tools, the request shapes of the tools checked against the published specs, the request shapes of the October 2026 bulk endpoint, S/MIME and Search tools, the item and page totals the REST list tools report, the endpoint inventory's reduction to the latest snapshot and its stale flag, the AI Defense tools (request shapes, the HTTP 200 with errors case, not-found and deleted policies, the stale version hint, and the input checks that refuse before any call), a registration check that lists all 360 tools over an in-memory transport and checks the descriptions for the measured warnings, the SOPHOS_FUSION_GRAPHQL_URL check, and the HTTP transport (Origin guard, bearer token, listen address, concurrent calls) run against an in-memory Sophos. Nothing in npm test reaches Sophos.

To exercise the Fusion tools against a live tenant, put credentials in .env (or export them) and run:

node scripts/fusion-smoke.mjs                  # read-only, tenant credential

node scripts/fusion-smoke.mjs # read-only, partner or organisation credential node scripts/fusion-smoke.mjs --write # plus the Fusion write tools on one new case node scripts/fusion-smoke.mjs --write-classic # plus the Classic case tools on one new case node scripts/fusion-smoke.mjs --write-ai-defense # plus the AI Defense policy writes on test policies node scripts/fusion-smoke.mjs --all # everything

It spawns the built server over stdio and calls the tools through an MCP client, so what runs is what a host runs. Read-only mode covers the reference data, the case list with filter and cursor variants, the newest case

Only the beginning is shown; read the rest in the repo