Skip to main content
Glama
ry-ops

fortigate-mcp-server

by ry-ops

Related Servers

Alternatives to fortigate-mcp-server

No user-submitted related servers found.

    Related Servers

    • A
      license
      Not graded
      quality
      D
      maintenance
      Provides 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
    • F
      license
      Not graded
      quality
      A
      maintenance
      Enables managing a pfSense firewall in plain English from Claude Desktop, Claude Code, or any MCP client, covering firewall rules, NAT, VPNs, routing, DNS, DHCP, certificates, and diagnostics across 332 wire-format-verified tools. Destructive changes pass through layered safety guardrails with explicit confirmation, rate limiting, config-revision backup and rollback, and secrets-redacted logging.
      -
    • F
      license
      Not graded
      quality
      A
      maintenance
      Enables natural-language management of a pfSense firewall from Claude Desktop, Claude Code, or any MCP client, covering firewall rules, NAT, VPNs, routing, DNS, DHCP, certificates, and diagnostics across 332 wire-format-verified tools. Every destructive change passes through confirmation guardrails, rate limits, and config-revision rollback with secrets redacted from logs.
      -
    • F
      license
      Not graded
      quality
      B
      maintenance
      Enables natural-language management of a pfSense firewall from Claude Desktop, Claude Code, or any MCP client, covering firewall rules, NAT, VPNs, DNS, DHCP, certificates, logs, and diagnostics across 332 tools. Includes safety guardrails such as explicit confirmation for destructive actions, rate limits, config-revision backups for rollback, and input validation with secret redaction.
      -

    TDQS

    B3.1/5.0

    Scored across 88 tools

    Disambiguation4/5

    Most tools target distinct resources and actions (e.g., list_addresses vs create_address_group vs list_firewall_policies), and descriptions clarify boundaries. Some overlap exists between the generic API tools (get_config/set_config/fortigate_api) and dedicated update/create tools, and audit_admin_access overlaps with audit_hardening, but descriptions generally resolve which to use.

    Naming Consistency4/5

    The set predominantly follows a consistent verb_noun snake_case pattern (list_, get_, create_, update_, delete_, audit_, set_). A couple of tools break the pattern (forticonverter_setup_prompt and fortigate_api are noun phrases), but overall naming is predictable and readable.

    Tool Count1/5

    88 tools is far beyond the typical 3-15 range and qualifies as an extreme mismatch. The presence of generic config tools (search_api, get_config, set_config, fortigate_api) makes many dedicated tools redundant, bloating the surface and increasing selection cost.

    Completeness5/5

    Coverage is exceptionally thorough: firewall policies, addresses, services, DNS/DHCP, routing, interfaces, licenses, HA, audits, logs, security profiles, certificates, and a generic REST escape hatch. There are no obvious gaps for managing a FortiGate.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues