Skip to main content
Glama
paoloamato2

FortiOS 7.6.x MCP Server

by paoloamato2
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

Related Servers

Alternatives to FortiOS 7.6.x MCP Server

No user-submitted related servers found.

    Related Servers

    • fortigate-mcp-server

      ry-ops
      A
      license
      B
      quality
      A
      maintenance
      Lets 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.
      88
      4
      MIT

    • FortiGate MCP Server

      humyai99
      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

    • fortigate-mcp

      irfanharis
      A
      license
      A
      quality
      D
      maintenance
      An MCP server for managing and monitoring FortiGate firewalls via the FortiOS REST API, enabling natural language queries for status, policies, VPNs, and sessions.
      9
      MIT

    • fortigate-mcp

      oscardagrach
      A
      license
      Not graded
      quality
      C
      maintenance
      An MCP server that enables natural language management of FortiGate firewalls via the FortiOS REST API, offering 393 tools for system, policy, routing, VPN, and security configuration.
      MIT
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    B3/5.0

    Scored across 240 tools

    Disambiguation2/5

    Generic cmdb_*, monitor_get, log_get, and service_call tools overlap heavily with the many specific resource tools, creating ambiguity about which to invoke (e.g., cmdb_get vs firewall_policy_get). Duplicate concepts like certificate_local_list vs vpn_certificate_local_list further blur boundaries.

    Naming Consistency4/5

    The majority of tools follow a consistent domain_resource_action pattern such as firewall_policy_list/create/update/delete and vpn_ipsec_phase1_get. A few outliers like system_resource_usage, monitor_get, and service_call break the pattern, but they are minor relative to the overall set.

    Tool Count1/5

    240 tools is an extreme count that creates significant context and selection burden for an agent. Many tools are redundant with generic pass-through tools, and the overall surface is far beyond what is typically manageable or well-scoped.

    Completeness4/5

    The tool set covers most major FortiOS domains, including firewall, VPN, routing, user authentication, UTM, WiFi, logging, and monitoring. Some resource-specific CRUD cycles are incomplete, such as IP pools lacking get/update/delete and VIPs lacking update, but the generic cmdb_* tools can cover those gaps.

    Maintenance

    ActivityInactive
    ResponsivenessUnresponsive

    Resources