Skip to main content
Glama
rstierli

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.
      15
      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
      B
      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

    • fortimail-mcp-server

      Lynsoft
      A
      license
      C
      quality
      D
      maintenance
      Enables AI agents to manage FortiMail email security through the FortiMail Engine API, providing tools for domains, users, queues, reports, logs, and SMTP configuration.
      56
      1
      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 103 tools

    Disambiguation4/5

    Most tools have clearly distinct purposes, with detailed descriptions that differentiate similar actions (e.g., add_device vs add_model_device vs add_devices_bulk). However, the presence of multiple assign_* and execute_script_on_* tools, though distinguishable by resource and target, introduces slight ambiguity that could cause misselection in an agent.

    Naming Consistency4/5

    The majority of tools follow a consistent verb_noun pattern (e.g., create_address_host, delete_firewall_policy, list_devices). Minor inconsistencies exist, such as mixing 'add' and 'create' for device vs. object operations, and outliers like 'health_check' and 'reload_device_list' that deviate from the pattern.

    Tool Count2/5

    With 103 tools, the server heavily exceeds the typical well-scoped range of 3-15 tools for an MCP server. While the domain is complex, this number is likely overwhelming for an agent to navigate effectively, resulting in a score of 2 for being too many.

    Completeness3/5

    The tool set covers core FortiManager operations comprehensively, including device lifecycle, policy management, address/service objects, templates, scripts, and tasks. However, notable gaps exist: no create/update for system or template groups, no VPN management, and limited interface manipulation. Given the high tool count, these omissions are significant.

    Maintenance

    ActivitySlowing
    ResponsivenessWithin a week

    Resources