Fortigate MCP Server
A comprehensive Model Context Protocol (MCP) server for managing FortiGate devices.
Ask AI about Fortigate MCP Server
Powered by Claude Β· Grounded in docs
I know everything about Fortigate MCP Server. Ask me about installation, configuration, usage, or troubleshooting.
0/500
Reviews
Documentation
FortiGate MCP Server
A production-ready Model Context Protocol (MCP) server for managing FortiGate firewalls
Features β’ Quick Start β’ Configuration β’ Tools β’ Architecture β’ Security β’ Testing
Overview
FortiGate MCP Server exposes FortiGate firewall management capabilities through the Model Context Protocol, enabling AI assistants and MCP-compatible tools to programmatically manage firewall policies, network objects, routing, and device configurations.
Built with fully async Python, persistent HTTP connection pooling, and security-first defaults.
Features
Device Management
- Multi-device support with concurrent management
- API token and basic authentication
- Connection testing and health monitoring
- VDOM discovery and per-VDOM operations
Firewall Policy Management
- Full CRUD for firewall policies
- Policy detail with address/service object resolution
- VDOM-scoped operations
Network Object Management
- Address objects (subnet, IP range, FQDN)
- Service objects (TCP/UDP/SCTP with port ranges)
Virtual IP Management
- NAT/DNAT virtual IPs
- Port forwarding configuration
- Protocol-specific VIP rules
Routing
- Static route CRUD operations
- Routing table inspection
- Interface listing and status monitoring
Infrastructure
- Fully async API client with
httpx.AsyncClientconnection pooling - STDIO and HTTP transport modes
- Pydantic configuration models with validation
- Structured logging with API call tracing
- Rate limiting support
Quick Start
Prerequisites
- Python 3.11+
- Access to a FortiGate device with API enabled
- API token (recommended) or admin credentials
Installation
git clone https://github.com/Aprazor/fortigate-mcp-server.git
cd fortigate-mcp-server
python -m venv .venv
source .venv/bin/activate # Linux/macOS
# .venv\Scripts\activate # Windows
pip install -e .
Configuration
Create a configuration file (e.g., config/config.json):
{
"fortigate": {
"devices": {
"fw-primary": {
"host": "192.168.1.1",
"port": 443,
"api_token": "your-api-token-here",
"vdom": "root",
"verify_ssl": true,
"timeout": 30
}
}
},
"server": {
"name": "fortigate-mcp-server",
"host": "0.0.0.0",
"port": 8814
},
"auth": {
"require_auth": false,
"allowed_origins": []
},
"logging": {
"level": "INFO",
"console": true
}
}
Run the Server
STDIO mode (for direct MCP client integration):
export FORTIGATE_MCP_CONFIG=config/config.json
python -m src.fortigate_mcp.server
HTTP mode (for web-based access):
python -m src.fortigate_mcp.server_http \
--host 0.0.0.0 \
--port 8814 \
--config config/config.json
MCP Client Integration
Claude Desktop / Claude Code (~/.claude/mcp_servers.json):
{
"mcpServers": {
"fortigate": {
"command": "python",
"args": ["-m", "src.fortigate_mcp.server"],
"env": {
"FORTIGATE_MCP_CONFIG": "/path/to/config.json"
}
}
}
}
Cursor IDE (~/.cursor/mcp_servers.json):
{
"mcpServers": {
"FortiGateMCP": {
"url": "http://localhost:8814/fortigate-mcp/",
"transport": "http"
}
}
}
Available Tools
Device Management (6 tools)
| Tool | Description |
|---|---|
list_devices | List all registered FortiGate devices |
get_device_status | Get system status for a device |
test_device_connection | Test connectivity to a device |
add_device | Register a new FortiGate device |
remove_device | Remove a registered device |
discover_vdoms | Discover Virtual Domains on a device |
Firewall Policy Management (5 tools)
| Tool | Description |
|---|---|
list_firewall_policies | List all firewall policies |
create_firewall_policy | Create a new firewall policy |
update_firewall_policy | Update an existing policy |
get_firewall_policy_detail | Get policy with resolved objects |
delete_firewall_policy | Delete a firewall policy |
Network Object Management (4 tools)
| Tool | Description |
|---|---|
list_address_objects | List firewall address objects |
create_address_object | Create address object (subnet/range/FQDN) |
list_service_objects | List firewall service objects |
create_service_object | Create service object (TCP/UDP/SCTP) |
Virtual IP Management (5 tools)
| Tool | Description |
|---|---|
list_virtual_ips | List virtual IP configurations |
create_virtual_ip | Create VIP with optional port forwarding |
update_virtual_ip | Update virtual IP configuration |
get_virtual_ip_detail | Get detailed VIP information |
delete_virtual_ip | Delete a virtual IP |
Routing Management (8 tools)
| Tool | Description |
|---|---|
list_static_routes | List configured static routes |
create_static_route | Create a new static route |
update_static_route | Update an existing static route |
delete_static_route | Delete a static route |
get_static_route_detail | Get detailed route information |
get_routing_table | Get the active routing table |
list_interfaces | List network interfaces |
get_interface_status | Get interface operational status |
System Tools (2 tools)
| Tool | Description |
|---|---|
health_check | Server health and device connectivity status |
get_server_info | Server version and configuration info |
Architecture
fortigate-mcp-server/
βββ src/fortigate_mcp/
β βββ server.py # STDIO MCP server (FastMCP)
β βββ server_http.py # HTTP MCP server (FastMCP)
β βββ config/
β β βββ loader.py # Configuration file loading
β β βββ models.py # Pydantic config models
β βββ core/
β β βββ fortigate.py # Async API client + device manager
β β βββ logging.py # Structured logging setup
β βββ tools/
β β βββ base.py # Base tool class (error handling, formatting)
β β βββ definitions.py # Tool description constants
β β βββ device.py # Device management tools
β β βββ firewall.py # Firewall policy tools
β β βββ network.py # Address/service object tools
β β βββ routing.py # Routing and interface tools
β β βββ virtual_ip.py # Virtual IP tools
β βββ formatting/
β βββ formatters.py # MCP content formatters
β βββ templates.py # Response templates
βββ tests/
βββ conftest.py # Shared fixtures (AsyncMock)
βββ test_config.py # Configuration model tests
βββ test_device_manager.py # Device manager lifecycle tests
βββ test_fortigate_api.py # Async API client tests
βββ test_formatting.py # Response formatting tests
βββ test_tools.py # Tool integration tests
Design Principles
- Fully async: All API calls use
httpx.AsyncClientwith persistent connection pooling per device - Security by default: SSL verification enabled, empty CORS origins, no wildcard defaults
- Clean separation: Config models, API client, tool logic, and formatting are independent layers
- Error categorization: FortiGate API errors are mapped to user-friendly messages with HTTP status awareness
Security
This server is designed with security-first defaults:
| Setting | Default | Description |
|---|---|---|
verify_ssl | true | SSL certificate verification enabled |
allowed_origins | [] | No CORS origins allowed (explicit opt-in) |
require_auth | false | MCP server authentication (enable for production) |
Recommendations for production:
- Use API tokens instead of username/password authentication
- Keep
verify_ssl: trueunless testing with self-signed certificates - Set explicit
allowed_originswhen using HTTP transport - Enable
require_authwith configured API tokens for the MCP server itself - Run the server on a trusted network or behind a reverse proxy
- Use environment variables for sensitive configuration values
Testing
The project includes 117 tests covering the full async stack:
# Run all tests
python -m pytest
# Run with verbose output
python -m pytest -v
# Run specific test module
python -m pytest tests/test_tools.py
# Run with coverage report
python -m pytest --cov=src --cov-report=html
Test Coverage
| Module | Coverage |
|---|---|
| Config models | Security defaults, validation, Pydantic models |
| API client | Async HTTP, connection pooling, error handling |
| Device manager | Lifecycle (add/remove/list), async operations |
| Tool classes | All CRUD operations, VDOM support, error paths |
| Formatting | Templates, content rendering, edge cases |
Troubleshooting
Connection refused
- Verify the FortiGate device is reachable and the API is enabled
- Check that the port (default 443) is not blocked by network firewalls
Authentication failed (401)
- Verify your API token is valid and has appropriate permissions
- For basic auth, confirm the username/password are correct
SSL certificate error
- For self-signed certificates in lab environments, set
verify_ssl: false - For production, install a valid certificate on the FortiGate device
VDOM not found
- Use
discover_vdomsto list available VDOMs on the device - Ensure the VDOM name matches exactly (case-sensitive)
Contributing
- Fork the repository
- Create a feature branch (
git checkout -b feature/my-feature) - Write tests for new functionality
- Ensure all tests pass (
python -m pytest) - Commit your changes (
git commit -m 'Add my feature') - Push to your branch (
git push origin feature/my-feature) - Open a Pull Request
License
This project is licensed under the MIT License. See the LICENSE file for details.
Acknowledgments
- Model Context Protocol - The protocol specification
- FastMCP - Python MCP server framework
- FortiGate REST API - FortiGate API documentation
- httpx - Async HTTP client
