Skip to main content
Glama
Sign In
gensecaihq

pfSense MCP Server

by gensecaihq
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

Related Servers

Alternatives to pfSense MCP Server

No user-submitted related servers found.

    Related Servers

    • OPNSense MCP Server

      vespo92
      A
      license
      C
      quality
      A
      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
      101 npm
      94
      MIT

    • pfSense Enhanced MCP Server

      MmaxwellCB
      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

    • pfSense MCP Server

      Koehler0601
      F
      license
      Not graded
      quality
      A
      maintenance
      Enables natural-language control of a pfSense firewall through Claude Desktop, Claude Code, or any MCP client, covering firewall rules, NAT, VPNs, routing, DNS, DHCP, certificates, services, packages, and diagnostics. Every change passes through multi-layer safety guardrails with confirmation requirements, rate limiting, config revision backups for rollback, and audit logging.
      -

    • Firewalla MCP Server

      MadLlama25
      -
      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.
      -

    • pfSense MCP Server

      Hayashi05356
      F
      license
      Not graded
      quality
      A
      maintenance
      Enables natural-language management of pfSense firewalls—creating and reordering rules, NAT, VPNs, aliases, DNS, DHCP, certificates, services and diagnostics—directly from Claude Desktop, Claude Code, or any MCP client, with confirmation guardrails and rollback points on every change.
      -

    • pfSense MCP Server

      Jean89899
      F
      license
      Not graded
      quality
      A
      maintenance
      Enables natural-language management of a pfSense firewall through Claude Desktop, Claude Code, or any MCP client — creating and auditing firewall rules, NAT, VPNs, DNS, DHCP, certificates and diagnostics via the pfSense REST API. Destructive changes are gated behind confirmation, rate limits and guardrails, with config revisions captured for rollback.
      -
    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

    C2.9/5.0

    Scored across 332 tools

    Disambiguation2/5

    Despite each tool having a detailed description, the sheer number and overlapping terminology make selection risky. Near-synonyms like search_interfaces/search_interface_configs, get_openvpn_status/get_openvpn_server_status, and get_log_file/get_firewall_log/search_logs_by_ip blur boundaries, and manage_* tools inconsistently mean add/remove or full CRUD. An agent would frequently need to read descriptions to avoid choosing the wrong tool.

    Naming Consistency3/5

    Most tools follow a readable verb_noun snake_case pattern (search_, create_, update_, delete_, get_, apply_), which provides a strong baseline. However, there are many deviations: create_firewall_rule_advanced, system_status, get_openvpn_server_status vs get_openvpn_status, and inconsistent singular/plural names like search_ipsec_phase2_encryptions vs create_ipsec_phase2_encryption. The pattern is recognizable but not reliable enough for a 4.

    Tool Count1/5

    332 tools is an extreme mismatch for any tool surface, even one covering the full pfSense feature set. This many tools will overwhelm context windows and make tool selection slow and error-prone. Most CRUD families could be consolidated into parameterized resource tools or grouped sub-servers.

    Completeness3/5

    The server covers an enormous breadth of pfSense domains and most resources have full CRUD plus apply/diagnostic helpers. However, there are notable gaps: interface groups and bridges have create/search but no update/delete, cron jobs lack update, IPsec Phase 1 encryption entries lack update, ACME account keys lack delete/update, and there is no restore-config-revision tool. These are workable for some cases by delete+recreate, but will block or complicate otherwise expected workflows.

    Maintenance

    ActivitySlowing
    ResponsivenessUnresponsive

    Resources