Skip to main content
Glama
Sign In
FortiManager MCP Server

FortiManager MCP Server

by rstierli
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

Related Servers

Alternatives to FortiManager MCP Server

No user-submitted related servers found.

    Related Servers

    • FortiAnalyzer MCP Server

      rstierli
      A
      license
      Not graded
      quality
      A
      maintenance
      Enables AI assistants to interact with FortiAnalyzer for log analysis, reporting, security monitoring, and SOC operations via the JSON-RPC API.
      16
      MIT

    • FortiGate MCP Server

      Serrinho02
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI assistants to manage FortiGate firewalls from bootstrap to production, with safe preview/apply changes and secure credential handling. Covers inventory, VDOMs, interfaces, routing, firewall policies, VPN, security analysis, and documentation generation.
      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-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
    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.4/5.0

    Scored across 233 tools

    Disambiguation4/5

    Tool boundaries are unusually well-delineated: descriptions explicitly disambiguate near-neighbors (create_local_in_policy vs create_firewall_policy, create_device_sniffer vs create_device_on_demand_sniffer vs FMG's own packet-capture tools, get_device_sdwan vs get_device_sdwan_monitor, find_object_usage vs search_objects). Residual confusion exists among the four template-listing tools (list_templates, list_system_templates, list_template_groups, list_cli_template_groups) and the fire-and-forget type-split address creators, but an agent can generally tell tools apart.

    Naming Consistency4/5

    Names follow a consistent snake_case verb_noun convention (list_/get_/create_/update_/delete_/add_/remove_/assign_/execute_/install_/revert_/diff_), with bulk variants using a predictable `_bulk` suffix. Minor deviations such as the `..._policy6` / `list_local_in_policies6` IPv6 suffix (instead of `_ipv6`) and add-vs-create splits for group membership slightly break the pattern but remain readable.

    Tool Count2/5

    233 tools is far beyond any reasonable agent-facing surface; even a full FortiManager API wrapper does not need to expose every CRUD permutation of every object in one server. Nearly all tools are individually meaningful and non-redundant, but the volume alone guarantees selection errors and context exhaustion.

    Completeness4/5

    Coverage is remarkably deep: CRUD across policies, local-in policies (v4/v6), addresses, services, security profiles, packages, devices, groups, templates, IPsec, SSL-VPN, wireless, revisions and firmware. Gaps are acknowledged (DLP rules, application-list entries, WAF nested sections, no create for SSL-VPN web portals, no update/delete for device sniffer definitions) but most are workaroundable via scripts/CLI.

    Maintenance

    ActivityMaintained
    ResponsivenessSyncing

    Resources