fortigate-mcp-server
Enables engineers to programmatically manage firewall policies, routing, and VPN configuration without manual console access, reducing deployment time and co…
MCP server for managing FortiGate firewalls: policies, objects, routing, VPN, monitoring and read-only diagnostics.
- Ask Claude to retrieve current firewall policies and explain traffic rules blocking specific applications.
- Generate a new FortiGate security policy configuration for a remote office VPN tunnel setup.
- Automate quarterly audits by checking firewall objects, routing tables, and active VPN connections.
Enables engineers to programmatically manage firewall policies, routing, and VPN configuration without manual console access, reducing deployment time and configuration drift risk in network infrastructure.
Network engineers and DevOps teams automating FortiGate firewall provisioning and policy management in Infrastructure-as-Code workflows.
https://github.com/alpadalar/fortigate-mcp-server
By alpadalar
How to Get It
claude mcp add fortigate-mcp-server -- npx -y fortigate-mcp-server
Tip: Paste this into a Claude Code conversation. Verify command matches your Claude Code version.
Auto-generated from the tool's public listing — not hands-on verified. Cross-check against the source repo's README before running.
Once it’s connected, paste this into Claude:
Retrieve current firewall policies and explain traffic rules blocking specific applications
Trust Signals Auto-scanned
Data & Access
Community Pulse Quiet
No community discussions found yet. This doesn't mean the tool isn't good — it may be new or serve a niche use case.
Reviewer notes
Auto-scanned review. These are observations, not a security certification.
Scored from trust signals (evidence-eval-v1): 37 GitHub stars; contributors unknown; last commit 0d ago; license MIT.
Things to check
- Scanned, not hands-on tested — this entry was auto-scanned from public metadata (GitHub metrics, license, security flags). No reviewer has run it, and no tool-specific limitations have been documented yet.
How to evaluate tools before deploying →
Data shown here comes from public APIs and automated scanning. Reviewer notes reflect one person's experience. This is not a security certification or legal recommendation. Always evaluate tools according to your own organization's policies.
Evaluation
Scored from trust signals (evidence-eval-v1): 37 GitHub stars; contributors unknown; last commit 0d ago; license MIT.