Unofficial Fortimonitor MCP Server

Unofficial Fortimonitor MCP server exists for a simple reason — assistants are far more useful when they can act on Unofficial Fortimonitor directly instead of describing what you should do. Model Context Protocol (MCP) server for FortiMonitor/Panopta v2 API integration with Claude AI.

What you get

Built by Gregori Jenkins — originally from Chicago, a humble student of Computer Science, and a proud cat dad.

• Server Management — — CRUD, tagging, attributes, DNS flush, path monitoring, logs
• Outage Monitoring — — Query, acknowledge, escalate, broadcast, delay, historical incidents
• Metrics & Resources — — Agent resources, SNMP resources, thresholds, metric graphs
• Maintenance Windows — — Create, extend, pause, resume, terminate schedules
• Server Groups — — Group CRUD, membership, compound services, child groups, monitoring policies
• Templates — — Create, apply, reapply monitoring templates to servers and groups

Setting it up

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.

What the assistant can call

Once Unofficial Fortimonitor is connected, these are the calls the assistant has available:

• Category — Module(s)
• Servers — servers, server_enhanced
• Outages — outages, outage_management, outage_enhanced
• Metrics — metrics, agent_resources
• Maintenance — server_management, maintenance_enhanced
• Templates — templates, templates_enhanced
• Notifications — notifications, notifications_enhanced
• Contacts — contacts_enhanced, rotating_contacts
• Cloud — cloud
• DEM — dem
• Dashboards — dashboards
• Reporting — reporting

Configuration and credentials

You will need 5 environment variables: FORTIMONITOR_API_KEY, FORTIMONITOR_BASE_URL, PYTHONPATH, ENABLE_SCHEMA_CACHE, YOUR_KEY. The server will not start without them, which is usually why the tools fail to appear on a first run. Keep credentials in your client's env block or a secrets manager rather than in a file you might commit.

Before you rely on it

• It runs with your machine's permissions. That is convenient and also the reason to think about what you point it at before you approve a tool call.
• With 14 tools registered it takes up a noticeable share of the context window; turn it off in projects that never touch Unofficial Fortimonitor.
• Missing credentials fail quietly in some clients — if no tools show up, check the environment block first.
• MCP clients confirm each tool call by default. Leave that on until you have watched what the unofficial fortimonitor mcp server does with a few real requests.

Choosing this one

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. Unofficial Fortimonitor's toolset — Category, Servers, Outages and 11 more — is a fair guide to whether it matches your workflow. It is maintained by gjenkins20; worth a glance at recent repository activity before you build anything load-bearing on it.

This entry was verified against Unofficial Fortimonitor's own documentation before publication; SyncDev keeps the directory reviewed rather than auto-generated.