Mcp Pfsense
Let your coding agent adjust pfSense firewall rules, DHCP, DNS, and related settings through MCP instead of clicking through the web UI.
Overview
mcp-pfsense is a MCP server for the Operate phase that lets AI assistants manage pfSense firewall rules, DHCP, DNS, and related settings over stdio.
What is this MCP server?
- PyPI package mcp-pfsense at catalog version 0.1.1 with stdio MCP transport
- Manage pfSense firewall rules, DHCP, DNS, and related controls via natural-language agent tools
- stdio server pairs with Claude Code or Cursor for homelab and SMB edge networks
- Reduces context switching between repo work and pfSense webConfigurator
- Open-source GitHub repo antonio-mello-ai/mcp-pfsense for self-hosted appliance admin
- PyPI package mcp-pfsense version 0.1.1
- Transport: stdio
- Source repository: github.com/antonio-mello-ai/mcp-pfsense
What problem does it solve?
Toggling pfSense settings through the web UI breaks your agent coding flow and makes it easy to mis-document what changed on the edge network.
Who is it for?
Indie operators with a pfSense homelab or office gateway who already drive changes via Claude Code or Cursor.
Skip if: Cloud-only builders on managed Vercel or Fly networking, or teams that forbid agent-driven firewall edits.
What do I get? / Deliverables
After you connect mcp-pfsense, your assistant can apply and describe network changes from the same MCP session as your infra code.
- Agent-executed pfSense configuration changes with conversational audit trail
- Faster iteration on rules, DHCP reservations, and DNS entries
- Reduced manual webConfigurator navigation during deploy weeks
Recommended MCP Servers
Journey fit
Operate infra is where homelab and small-team edge networks live after the product ships—firewall and DNS changes are production-adjacent ops, not greenfield app coding. Infra subphase fits dedicated network appliances you administer alongside app hosting, especially pfSense at the edge.
How it compares
MCP appliance admin for pfSense, not a cloud firewall SaaS integration or generic Terraform skill.
Common Questions / FAQ
Who is mcp-pfsense for?
Self-hosters and small-team operators who run pfSense and want MCP-driven help for rules, DHCP, and DNS without living in the web UI.
When should I use mcp-pfsense?
Use it in Operate infra when you are changing edge network policy, debugging connectivity, or aligning DNS with a new deploy.
How do I add mcp-pfsense to my agent?
Install mcp-pfsense from PyPI, configure stdio in your MCP host, and supply pfSense API or management credentials per the GitHub README.