Managing a pfSense firewall means clicking through web UI tabs, remembering field names, and hoping you don't fat-finger a rule that locks you out.
Connect Pfsense to Claude, Cursor or any other MCP client and it stops being a tab you switch to. Managing a pfSense firewall means clicking through web UI tabs, remembering field names, and hoping you don't fat-finger a rule that locks you out. With this MCP server, you describe what you want in plain English and the AI handles the. The pfsense mcp server is what makes that connection.
The toolset is worth reading before you wire it up, because it tells you what the integration is really for:
tvlc — WebGUI port type-mismatch report (#7)Domain — ToolsAliases — 5NAT — 16VPN — 51Routing — 16DNS — 24DHCP — 17Certificates — 15Users — 12Interfaces — 14System — 44Configuration is passed through the environment: PFSENSE_URL, AUTH_METHOD, PFSENSE_USERNAME, PFSENSE_PASSWORD, PFSENSE_VERSION, VERIFY_SSL, PFSENSE_API_KEY, MCP_API_KEY. Treat anything key-shaped as a real credential — scope it to the minimum the server needs, and rotate it if it ever lands in a shared config.
Setup follows the usual MCP pattern — install or clone the server, register it in your client's configuration file, restart the client. The configuration blocks on this page cover the common clients.
This sits in the monitoring and observability group, where several servers overlap in what they claim to do but differ sharply once you actually set them up. Pfsense's toolset — tvlc, Domain, Aliases and 11 more — is a fair guide to whether it matches your workflow. It is maintained by gensecaihq; worth a glance at recent repository activity before you build anything load-bearing on it.
This entry was verified against Pfsense's own documentation before publication; SyncDev keeps the directory reviewed rather than auto-generated.
| Tool | What it does |
|---|---|
| tvlc | WebGUI port type-mismatch report (#7) |
| Domain | Tools |
| Aliases | 5 |
| NAT | 16 |
| VPN | 51 |
| Routing | 16 |
| DNS | 24 |
| DHCP | 17 |
| Certificates | 15 |
| Users | 12 |
| Interfaces | 14 |
| System | 44 |
| Services | 14 |
| Logs | 3 |
{
"mcpServers": {
"pfsense": {
"command": "uvx",
"args": ["--from", "git+https://github.com/gensecaihq/pfsense-mcp-server", "pfsense-mcp-server"],
"env": {
"PFSENSE_URL": "https://192.168.1.1",
"AUTH_METHOD": "basic",
"PFSENSE_USERNAME": "admin",
"PFSENSE_PASSWORD": "your-password",
"PFSENSE_VERSION": "CE_2_8_0",
"VERIFY_SSL": "false"
}
}
}
}Configuration as documented by the project. Restart the client after saving.
| Variable | Description | Required |
|---|---|---|
| PFSENSE_URL | Endpoint or connection string the server talks to. | Yes |
| AUTH_METHOD | Configuration value read at startup. | Optional |
| PFSENSE_USERNAME | Configuration value read at startup. | Optional |
| PFSENSE_PASSWORD | Configuration value read at startup. | Optional |
| PFSENSE_VERSION | Configuration value read at startup. | Optional |
| VERIFY_SSL | Configuration value read at startup. | Optional |
| PFSENSE_API_KEY | Credential the server authenticates with. | Yes |
| MCP_API_KEY | Credential the server authenticates with. | Yes |
Give your coding agent the full DevTools toolbox: traces, network, console, heap snapshots and Lighthouse.
Dashboards, Prometheus and Loki queries, incidents and alerts — observability by conversation.
Errors with full context — stack traces, issue triage and AI-powered root-cause analysis from Sentry's server.
Enables enhanced web research capabilities for large language models through intelligent search queuing and advanced content extraction.
Automates browser interactions and enables Large Language Models (LLMs) to interact with web pages through Playwright and Chrome DevTools Protocol
Guides tool usage by providing recommendations for MCP tools at each problem-solving stage.