Skip to main content
Glama
gensecaihq

pfSense MCP Server

by gensecaihq

Related Servers

Alternatives to pfSense MCP Server

No user-submitted related servers found.

    Related Servers

    • A
      license
      C
      quality
      C
      maintenance
      A server that enables managing OPNSense firewalls through natural language interactions with Claude Desktop, supporting VLAN management, firewall rules configuration, and network interface queries.
      64
      118 npm
      83
      MIT
    • A
      license
      Not graded
      quality
      D
      maintenance
      Enables natural language interaction and management of pfSense firewalls through Claude and other GenAI applications using the Model Context Protocol. It provides advanced tools for firewall rule configuration, interface management, and intelligent log analysis via a REST API integration.
      1
      MIT
    • -
      license
      Not graded
      quality
      Not graded
      maintenance
      A production-ready server that connects Claude Desktop to Firewalla network management capabilities, allowing users to monitor devices, analyze network traffic, manage security alerts, and configure firewall rules through natural language.
      -
    • A
      license
      C
      quality
      C
      maintenance
      An AI-powered penetration testing server that integrates over 30 security tools with Groq LLM analysis for automated vulnerability scanning, triage, and reporting. It enables users to perform comprehensive security assessments through natural language natively within Claude Desktop.
      29
      MIT
    • A
      license
      Not graded
      quality
      C
      maintenance
      An MCP server for comprehensive OPNsense firewall management, enabling AI assistants to manage firewall rules, NAT, VLANs, and network diagnostics, plus execute SSH/CLI commands. Supports safety modes like read-only and dry-run for safe operation.
      118 npm
      MIT

    TDQS

    A3.5/5.0

    Scored across 333 tools

    Disambiguation4/5

    Tools are grouped by domain (certificates, DHCP, VPN, WireGuard, etc.) and each has a clear purpose. Some potential overlap exists between individual diagnostic tools like 'diagnose_dns_resolution' and the combined 'get_system_health_report', but overall the separation between search/get/update/apply operations is clear, making mis-selection unlikely for an agent.

    Naming Consistency4/5

    The naming pattern is largely consistent with verb_noun prefixes (get_, search_, create_, update_, delete_, apply_, manage_, diagnose_). Minor inconsistencies exist, such as 'run_ping_diagnostic' vs. 'diagnose_*' toolsainer, and some tools use 'get' vs 'search' for similar actions, but the overall convention is regular and predictable.

    Tool Count4/5

    333 tools is very large, but pfSense covers many subsystems (firewall, DHCP, DNS, VPN, certificates, HAProxy, WireGuard, system status). Each resource has CRUD plus search and apply operations, which explains the high count. However, the sheer number may be overwhelming for an LLM, so a slightly lower score seems warranted.

    Completeness5/5

    The tool set appears to cover the full pfSense feature surface: firewall, routing, DHCP, DNS, certificates, aliases, VPN (OpenVPN, IPsec, WireGuard), HAProxy, system status, diagnostics, and configuration rollback. Specialized tools like health reports and guardrails complete the picture. Missing only some uncommon packages, but core functionality is thoroughly addressed.

    Maintenance

    ActivityActive
    ResponsivenessUnresponsive