fortigate-mcp
Related Servers
Alternatives to fortigate-mcp
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityDmaintenanceProvides programmatic access to FortiGate devices for managing firewall policies, routing, virtual IPs, and device operations, enabling integration with MCP-compatible clients like Claude Desktop.MIT
- AlicenseBqualityAmaintenanceLets Claude or any MCP client manage a Fortinet FortiGate firewall through the FortiOS 7.6 REST API, covering firewall policies, NAT and port forwards, DNS and DHCP, application control, certificates, and live traffic and logs. It adds read-only and dry-run guardrails, clear FortiOS error explanations, and optional k3s and Proxmox integrations that keep firewall objects in sync with clusters and hypervisors.884MIT
- AlicenseBqualityDmaintenanceA complete MCP server for Fortinet FortiOS 7.6.x that exposes the entire REST API as typed MCP tools for use with MCP-compatible clients like Claude Desktop.10011MIT
- FlicenseNot gradedqualityAmaintenanceConnects Claude Desktop, Claude Code, or any MCP client to a pfSense firewall so users can inspect and modify firewall rules, NAT, VPNs, routing, DNS, DHCP, certificates, packages, and services through natural language. Every destructive action requires explicit confirmation, with guardrails, rate limits, and a captured config revision for rollback.-
- FlicenseNot gradedqualityAmaintenanceConnects Claude Desktop, Claude Code, or any MCP client to a pfSense firewall so users can query, diagnose, and change firewall rules, NAT, VPNs, DNS, DHCP, certificates, and other subsystems in natural language. Every destructive action is gated by confirmation prompts, rate limits, input validation, and config-revision rollback points, with tool request formats verified against the pfSense REST API.-
- FlicenseNot gradedqualityNot gradedmaintenanceConnects MCP clients such as Claude Desktop or Claude Code to a pfSense firewall so users can inspect and change rules, NAT, VPNs, DNS, DHCP, certificates, services, and diagnostics through plain-language conversation. Every destructive action is rate-limited, confirmation-gated, validated against the pfSense REST API wire format, and paired with a captured config revision for rollback.-
TDQS
Scored across 18 tools
Each tool has a clear, distinct purpose targeting specific resources (address, address group, policy, service, web filter profile, system status). No overlapping functionality; get and list are appropriately separated.
All tools follow the consistent pattern 'fortigate_verb_noun' with lowercase and underscores. Verbs are uniform: create, delete, get, list, update. No mixing of conventions.
18 tools is slightly above the typical 3-15 range but still well-scoped for managing a FortiGate firewall. Each tool serves a necessary function without redundancy.
Covers CRUD for addresses and address groups, and list/get for policies, services, and web filter profiles. Notable gaps: missing delete for policies, and no create/update/delete for services and web filter profiles.