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.2/5.0

    Scored across 233 tools

    Disambiguation2/5

    The set has many large familes with overlapping boundaries: list_templates/list_system_templates/list_sdwan_templates/list_cli_template_groups/list_template_groups, get_device_interfaces vs get_device_interface_config, device sniffer vs on-demand sniffer vs FortiManager packet capture, and several revision/diff tools. Descriptions usually explain the difference, but with 233 tools an agent will frequently face plausible near-matches.

    Naming Consistency4/5

    Names are consistently snake_case and mostly follow a verb_noun pattern (list_*, get_*, create_*, update_*, delete_*). Minor deviations exist where add_* is used instead of create_* for devices/groups/templates, and IPv6/local-in variants introduce suffixes like local_in_policies6, but the overall convention remains readable.

    Tool Count1/5

    233 tools is far beyond a practical MCP tool surface; even for a broad platform like FortiManager, the set is too large to select from reliably and should be consolidated into fewer domain-level tools. The count alone creates a severe context and misselection burden.

    Completeness4/5

    Coverage is extensive across ADOMs, devices, device-DB objects, firewall policies, local-in policies, security profiles, templates, SD-WAN, revisions, scripts, firmware, and tasks. There are still lifecycle gaps, such as limited create/update/delete coverage for some template families and missing single-object getters or deletes for a few device-DB objects, but core workflows are well covered.

    Maintenance

    ActivityMaintained
    ResponsivenessUsually handled

    Resources