unofficial-fortimonitor-mcp-server

Unofficial FortiMonitor MCP Server is a community-developed Model Context Protocol (MCP) server for integrating the FortiMonitor/Panopta v2 API with Claude AI. According to the project description, it provides 241 tools across 33 modules, achieving near-complete coverage of the FortiMonitor v2 API.

Intended Use

This project is used to expose FortiMonitor's server monitoring capabilities to AI assistants (such as Claude AI) through MCP, enabling AI to call relevant tools to query and manage monitoring data. It states that it is an unofficial community project and is not affiliated with, endorsed by, or supported by Fortinet, Inc. or the FortiMonitor/Panopta team; "FortiMonitor" and "Fortinet" are trademarks of Fortinet, Inc., and use is at your own risk.

Main Capabilities (by Module)

The tool modules listed by the project include:

• Server management: CRUD, tags, attributes, DNS refresh, path monitoring, logs
• Outage monitoring: query, acknowledge, escalate, broadcast, delay, historical events
• Metrics and resources: agent resources, SNMP resources, thresholds, metric graphs
• Maintenance windows: create, extend, pause, resume, terminate schedules
• Server groups: group CRUD, member management, compound services, subgroups, monitoring policies
• Templates: create templates, apply monitoring templates to servers and groups and reapply
• Notifications: schedules, contacts, contact groups, on-call contacts for rotations
• Cloud monitoring: providers, credentials, discovery, regions, services
• DEM: applications, instances, locations for digital experience monitoring
• Compound services: aggregate service CRUD, thresholds, availability, response time
• Dashboards and status pages: CRUD for monitoring dashboards and public status pages
• Reports: system health summary, outage statistics, availability reports, CSV export
• SNMP: credentials, discovery, resource CRUD, metrics
• OnSight: on-premises monitoring instances and groups
• Fabric connections: integration management
• Countermeasures: automated remediation for network services and thresholds
• User management: user CRUD, roles, add-ons
• Reference data: contact types, time zones, roles, account history, server attribute types It also states that it provides Docker support and Windows support.

Usage

The project provides three deployment methods:

• Method A: Docker (recommended), with detailed instructions in DOCKER_DEPLOYMENT.md
• Method B: Local installation, with steps including configuring the environment, testing connectivity, and running the server
• Method C: Windows (Claude Desktop / Claude Code), with steps in docs/WINDOWS_DEPLOYMENT.md

When integrating with Claude Desktop, you can edit claude_desktop_config.json and add the corresponding configuration:

• When using Docker, first ensure the container is running, then add the configuration
• When using local Python, the project notes that Claude Desktop cannot reliably set cwd, so you need to use the full path to the installed entry script and explicitly set PYTHONPATH; you can set ENABLE_SCHEMA_CACHE=false to avoid the [Errno 30] Read-only file system error when the server cannot write to the default cache/ directory, or set SCHEMA_CACHE_DIR to a writable absolute path to preserve the cache.

The server automatically discovers and caches the FortiMonitor API schema for validation and documentation, cached by default in cache/schemas/. Schema endpoints include /schema/resources (lists all available API resources) and /schema/resources/{resource_name} (gets the schema for a specific resource). The project also includes test running methods with coverage and a description of the project structure.

Troubleshooting (provided by the project)

• Authentication errors: check the API key in .env; confirm the base URL is correct (https://api2.panopta.com/v2）；可用 curl test API key: curl "https://api2.panopta.com/v2/server?api_key=YOUR_KEY&limit=1"
• Architecture discovery failed: Check network connectivity; confirm that the cache/schemas/ directory exists and is writable; clear the cache and retry (rm -rf cache/schemas/*)
• MCP server does not appear in Claude: Check the Claude Desktop configuration syntax; confirm that the file path is an absolute path; fully restart Claude Desktop; check the server logs for startup errors

Limitations and Notes

The project explicitly states that it is an independent community project, has no official relationship with Fortinet, is authored by Gregori Jenkins, and uses the MIT License. More details about specific feature effects, fees or pricing, and actual usage steps are not currently provided in the materials.