Unofficial Fortimonitor MCP Server

What gjenkins20/unofficial-fortimonitor-mcp-server MCP server does

The gjenkins20/unofficial-fortimonitor-mcp-server MCP server connects an MCP client to the FortiMonitor/Panopta v2 API. It exposes 241 tools grouped across 33 modules, covering infrastructure management, monitoring data, incident handling, notifications, reporting, and account-related resources.

The available operations include creating and updating monitored servers, managing server groups and templates, querying and acknowledging outages, working with maintenance schedules, and retrieving metrics or resource details. Additional modules cover SNMP, cloud monitoring, Digital Experience Monitoring, compound services, dashboards, public status pages, OnSight, Fabric connections, countermeasures, users, and reference data.

How it works

The server runs as a local MCP process and makes synchronous HTTP requests to FortiMonitor's v2 API. Configuration is read from environment variables or a .env file. FORTIMONITOR_API_KEY supplies the API credential, while FORTIMONITOR_BASE_URL identifies the API endpoint and defaults to the documented Panopta v2 URL.

At startup and during operation, the project can discover API schemas and store them under cache/schemas/. These schemas support request validation and API documentation. Schema caching can be disabled for environments where the process cannot write to its default cache directory, or redirected to a writable location with SCHEMA_CACHE_DIR.

Setup and configuration

To run the gjenkins20/unofficial-fortimonitor-mcp-server MCP server locally, create a Python virtual environment, install the dependencies from requirements.txt, configure the API key, optionally test connectivity, and start the module with python -m src.server. Docker deployment is also documented, including a container image and Docker Compose workflow.

The documented environment settings are:

• FORTIMONITOR_API_KEY: API key used for FortiMonitor requests.
• FORTIMONITOR_BASE_URL: FortiMonitor API base URL.
• LOG_LEVEL: Application logging level.
• ENABLE_SCHEMA_CACHE: Enables or disables schema caching.
• SCHEMA_CACHE_DIR: Optional writable directory for cached schemas.

Claude Desktop can invoke the server through Docker or a local Python entrypoint. The local configuration may also set PYTHONPATH, particularly because Claude Desktop does not reliably set the process working directory. Windows deployment instructions are provided separately for Claude Desktop and Claude Code.

Tools and capabilities

The tool set supports both read and write operations where the FortiMonitor API exposes them. Representative capabilities include:

• List, inspect, create, update, and delete monitored servers, groups, contacts, users, dashboards, status pages, and SNMP resources.
• Query active or historical outages, acknowledge incidents, escalate them, broadcast updates, and apply bulk outage actions.
• Create, extend, pause, resume, and terminate maintenance windows.
• Apply monitoring templates to servers and groups and manage thresholds, metrics, network services, and compound services.
• Manage notification schedules, contact groups, rotating on-call contacts, cloud monitoring resources, DEM objects, OnSight instances, and countermeasures.
• Retrieve health summaries, outage statistics, availability reports, top-alerting information, and CSV exports.

Limitations and notes

This is an unofficial community project and is not affiliated with, endorsed by, or supported by Fortinet or the FortiMonitor/Panopta team. Use requires a FortiMonitor API key and access to the relevant API resources. The repository describes Docker and Windows deployment support, but client compatibility beyond the documented Claude integrations is not established in the supplied material. The project also depends on writable filesystem access when schema caching remains enabled.