L
lordraiden/sophos-firewall-mcp
MCP server for the Sophos Firewall 23 (SFOS 23.0) Configuration REST API — 152 typed tools for firewall, NAT,…
★ 1·更新 2026-11-17
在 GitHub 查看 ↗链接已于 2026-11-17 核查 · HTTP 200 · 打开的是厂商自己的官网
- ★ 数取值
- 1 ★ · lordraiden/sophos-firewall-mcp · 取自 GitHub 搜索 API · (2026-11-19 20:00:48 核对)
- 来源明细
- 从该仓库的 GitHub 页面直接读取 · 条目类型:开源项目
- 收录与活跃
- 收录于 2026-11-17 · 最近见到 2026-11-20 · 共见到 4 次 · 被 1 个来源列出
- 评分构成
- 综合分 103 · 1 ★ · 1 个来源 · repo
常见问题(答案都来自我们的记录)
它适合谁 / 用来做什么?
我们把它归在这些标签下: 开源项目。标签来自条目自身,不是我们强加的分类。
谁维护它、还在更新吗?
仓库
lordraiden/sophos-firewall-mcp;我们收录于 2026-11-17;最近见到 2026-11-20。这里没有"官方认证"或"质量评级"——我们只记录来源与时间。README 原文(英文,未翻译) · 在 GitHub 读完整 README →
# Sophos Firewall 23 MCP Server (SFOS 23.0 REST API)
以下摘录自该仓库的 README(片段)
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
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
收录徽章(可选)
想把收录标记放进 README 就复制这行,可选,不影响收录。
[](https://anclum.com/zh/s/lordraiden-sophos-firewall-mcp/)
- 来源
- github · https://github.com/lordraiden/sophos-firewall-mcp
- 按领域浏览
- 开源项目
- Traction
- 1 ★
- 收录于
- 今天
更多条目
所属领域与标签
每个标签都能点进去看同类的全部条目。数字是当前库里的真实条数。