Sophos XGS MCP Server

A read-only Model Context Protocol (MCP) server for the Sophos XGS Firewall XML API. Gives AI assistants like Claude visibility into your firewall configuration without any ability to modify it.

Features

• 60+ read-only tools covering firewall rules, NAT, VPN, web filtering, network config, routing, DHCP, DNS, IPS, SSL/TLS inspection, and admin settings

• Read-only by design — only uses <Get> API operations, no <Set> or <Remove>

• XML injection protection — entity name validation and XML escaping on all inputs

• Credential isolation — credentials loaded from protected config files, never hardcoded

• Error sanitization — passwords are stripped from error messages before reaching the MCP client

• Scoped TLS handling — self-signed cert bypass is scoped per-request, not global

Related MCP server: Technitium MCP Secure

Tools

Prerequisites

• Node.js 18+

• Sophos XGS Firewall with the XML API enabled (port 4444 by default)

• An API admin account (a read-only profile is strongly recommended)

Enabling the Sophos XML API

1. Log into your Sophos XGS web admin

2. Go to Backup & firmware > API

3. Enable the API and allow access from the host running the MCP server

Setup

1. Install

git clone https://github.com/Leon69924/sophos-xgs-mcp.git
cd sophos-xgs-mcp
pnpm install
pnpm build

2. Configure credentials

Create the config directory:

mkdir -p ~/.config/sophos-xgs
chmod 700 ~/.config/sophos-xgs

Create ~/.config/sophos-xgs/config.json:

{
  "host": "your-sophos-hostname-or-ip",
  "port": "4444",
  "username": "your-api-user"
}

Create ~/.config/sophos-xgs/credentials with just the password:

echo -n "your-password" > ~/.config/sophos-xgs/credentials
chmod 600 ~/.config/sophos-xgs/config.json ~/.config/sophos-xgs/credentials

Alternatively, use environment variables:

export SOPHOS_HOST=your-sophos-hostname-or-ip
export SOPHOS_PORT=4444
export SOPHOS_USERNAME=your-api-user
export SOPHOS_PASSWORD=your-password

3. Add to your MCP client

For Claude Code, add to ~/.mcp.json:

{
  "mcpServers": {
    "sophos-xgs": {
      "type": "stdio",
      "command": "node",
      "args": ["/path/to/sophos-xgs-mcp/dist/index.js"]
    }
  }
}

Security

• Read-only — the server only uses <Get> XML API operations

• No hardcoded credentials — loaded from ~/.config/sophos-xgs/ or environment variables

• XML injection prevention — entity names are validated against ^[A-Za-z][A-Za-z0-9]*$, all interpolated values are XML-escaped

• Error sanitization — credentials are stripped from error messages

• TLS — all connections use HTTPS; self-signed cert bypass is scoped to the Sophos connection only

• Best practice: Create a dedicated read-only admin profile on your Sophos for API access

License

AGPL-3.0-only — see LICENSE