Independent by design · no pay-to-rank placements  · How we evaluate tools →
Anclum Submit
L

lordraiden/sophos-firewall-mcp

Independent directory — not the official site. Details below come from the project's public repository.

MCP server for the Sophos Firewall 23 (SFOS 23.0) Configuration REST API — 152 typed tools for firewall, NAT,…

1 ★ measured · checked 2026-11-19

Before you install: no copy-paste command · license Apache-2.0 · link reachable

First step: nothing runnable here yet - start from the repository: https://github.com/lordraiden/sophos-firewall-mcp

★ 1·updated 2026-11-17
View on GitHub ↗Link checked 2026-11-17 · HTTP 200 · opens the vendor's own site
Star count
1 ★ · lordraiden/sophos-firewall-mcp · read from the GitHub search API · (checked 2026-11-19 20:00:48)
Source
read directly from its GitHub page · type: open-source project
Harvest history
first seen 2026-11-17 · last seen 2026-11-20 · seen 4× · listed by 1 sources
Score
score 103 · 1 ★ · 1 sources · repo
FAQ (answers come from our records)
Who is it for?
We filed it under these tags: Open Source. The tags come from the entry itself, not a taxonomy we imposed.
Who maintains it?
repository lordraiden/sophos-firewall-mcp;first catalogued 2026-11-17;last seen 2026-11-20。There is no official certification or quality rating here — we record sources and dates only.
README excerpt (English, untranslated) · Read the full README on GitHub →

# Sophos Firewall 23 MCP Server (SFOS 23.0 REST API)

Excerpted from the repository README (abridged)

A local MCP server for Sophos Firewall 23, built on the
Model Context Protocol: it administers a Sophos Firewall 23
(SFOS 23.0) appliance through the Sophos Firewall Configuration REST API, over STDIO. It is
built for firewall automation and for AI agents — Claude Desktop, Cursor, VS Code, Antigravity
IDE and any other MCP client — that need typed, bounded access to a firewall's configuration instead of
a raw HTTP surface.
It is not the Sophos Central Firewall Management API: the only backend is
https:// : /api/firewall-config/v1 on the appliance itself, authenticated with a
Bearer API key.
> 0.7.1 is the current release. It is a patch release that closes the High finding and the cheap
> findings of the 0.7.0 MCP standards review:
> the four gated delete descriptions now state that the confirmation is best-effort (it fires on
> the legacy handshake path and is skipped, with a logged warning, on the 2026-07-28 path), and
> nat_rule_create now requires position, which the appliance already rejected a create without.
> No tool is renamed and no argument is removed. 0.7.0 remains the breaking release: the 40
> IPv4/IPv6 tool pairs collapse into one tool per concept behind a required ip_family argument,
> and tool arguments are published flat instead of inside a request wrapper. The surface is 112
> tools. The
> migration table maps every removed
> tool name to its replacement. 0.6.0 unified the published output field names on camelCase (the
> Sophos wire names); 0.5.0 unified every published input parameter on snake_case; 0.4.0 was the
> breaking, REST-only migration: the XML transport, the XML credentials, the raw XML tool, the
> semantic router and FastEmbed are gone, with no compatibility mode. See
> CHANGELOG.md, the 0.7.1 release notes, the
> 0.7.0 release notes, the
> 0.6.0 release notes, the
> 0.5.0 release notes and the
> 0.4.0 release notes.
## Contents
What it does
Supported appliance and API
Requirements
Sophos Firewall prerequisites
Tool surface
Calling the tools
Context cost
Configuration
Install and run
MCP client configuration
Container usage
Read-only mode
Domain selection
Security model
Known limitations and accepted regressions
Development
Documentation
License
## What it does
112 typed tools across 11 domains (the complete catalog; SOPHOS_TOOL_DOMAINS publishes a
subset), covering 145 audited operations of the checked-in OpenAPI
contract (firewall_config_openapi.yaml, 700 operations) plus 5 composite tools that add no new
endpoint. The IPv4 and IPv6 families share one tool each, selected by a required ip_family
argument. Every tool maps to a documented operationId; the mapping is in
docs/API-COVERAGE.md.
One shared async REST client (httpx.AsyncClient) created in the MCP lifespan and closed exactly
once on shutdown. No client is created per tool call.
Typed, bounded inputs and outputs. Outputs are Pydantic DTOs with an object root, never raw Sophos
payloads. Listings return one page per call (page, pageSize, pageTotal where the contract
declares them); the server never auto-paginates or returns an entire configuration.
No raw REST tool. No tool accepts a URL, path, header, HTTP method or arbitrary JSON payload, so a
Listed badge (optional)
Copy this line into the README if you want the listing mark. Optional, and it does not affect being listed.
[![Listed on Anclum](https://anclum.com/badge/listed.svg)](https://anclum.com/en/s/lordraiden-sophos-firewall-mcp/)
Source
github · https://github.com/lordraiden/sophos-firewall-mcp
Browse by field
Open source
Traction
1 ★
added
today

More entries

All 1,875 →

Filed under

Every tag opens the full list for that filter. Counts are the live catalogue figures.

Browse all fields →

← Back to index