Fortianalyzer MCP logo

Fortianalyzer MCP

Unclaimed

by rstierli

MCP server for FortiAnalyzer JSON-RPC API. Query logs, alerts, incidents, FortiView analytics, and PCAPs from AI assistants.

Install

$pip install -e .

Set up this server

This server needs project-specific setup. Follow the project instructions; no reusable public launch command is available yet.

Project instructions

More in AI & ML

Browse the full directory

Unclaimed listing

Is this your MCP server?

This listing was auto-indexed from the public record. Claim it to edit the page, set compatibility and unlock growth tools. Takes under two minutes.

Claim this server

Security profile

Claimed and verified servers get a weekly static scan that shows what the code can reach: external services, environment variables, shell commands, agent configuration folders, plus any dependencies with known advisories. Claim this listing to get one. How the security profile works

40 of 40 tools

Documented tools (40)

From project documentation. A server handshake does not verify each tool’s description or behavior.

add_device

Add a new device to FortiAnalyzer

add_devices_bulk

Add multiple devices at once

cancel_log_search

Release a pagination handle

delete_device

Remove a device from FortiAnalyzer

delete_devices_bulk

Remove multiple devices at once

fetch_fortiview

Fetch FortiView query results

fetch_more_logs

Fetch another page for a querylogs handle (re-runs the query at a new offset)

fetch_report

Check report generation status

get_adom

Get specific ADOM details

get_alerts

Get security alerts

get_api_ratelimit

Get API rate limiting configuration (FAZ 7.6.5+)

get_device

Get specific device information

get_device_info

Get detailed device information

get_fortiview_data

Run FortiView and get results (auto-wait)

get_ha_status

Get High Availability cluster status

get_log_fields

Get available log fields for a log type

get_log_search_progress

Check log search progress

get_log_stats

Get log statistics

get_logfiles_state

Get log file state information

get_pcap_file

Download PCAP file for an IPS event

get_report_data

Download completed report data

get_report_history

Get report generation history

get_running_reports

List currently running reports

get_system_status

Get FortiAnalyzer system status and version info

get_task

Get task details by ID

list_adoms

List all Administrative Domains

list_device_groups

List device groups in an ADOM

list_device_vdoms

List VDOMs for a device

list_devices

List devices in an ADOM

list_report_layouts

List available report layouts

list_report_templates

List available report templates

list_tasks

List background tasks

query_logs

Query logs, or aggregate them: rows plus a reusable pagination handle, or groupby / sampleby / countonly (see below)

run_and_wait_report

Run report and wait for completion

run_fortiview

Start a FortiView analytics query

run_report

Start a report generation

save_report

Download and save report to disk

search_devices

Search devices with filters

update_api_ratelimit

Update API rate limits (FAZ 7.6.5+)

wait_for_task

Wait for a task to complete

Tool change history

Compared across complete checks of the same configuration. Tools were listed, not invoked. Input-schema changes are not measured here.

No complete tool checks yet.

FAQ

Questions about Fortianalyzer MCP Server

How do I connect Fortianalyzer MCP Server to Claude?
The listing records `pip install -e .` as its setup step. Run it, then follow the repository's instructions for the client configuration; the listing names Claude Desktop, Claude Code as compatible clients.
Is Fortianalyzer MCP Server free?
The listed licence is MIT. Check the upstream terms for permitted use and commercial requirements; a public repository does not by itself mean the software is free or open source. Connected APIs and hosted services may have separate charges.
What can Fortianalyzer MCP Server do?
Fortianalyzer MCP Server documents 40 tools to the agent, including add_device, add_devices_bulk, cancel_log_search. The descriptions above come from project documentation. A live handshake does not test individual tool behavior.