Warning
🚧 Under construction — not operational. rustfortimcp has no working code yet; it is on hold until a FortiGate lab device is available. Nothing here is ready for use.
Enterprise MCP server for Fortinet FortiGate — curated tools, scoped access, audited change control
a mechub project — sovereign network-security automation
Unofficial / community project. This is an independent community project and does not claim affiliation with or endorsement by Fortinet, Inc. Product names and trademarks are used only to identify the systems with which the software interoperates.
rustfortimcp will be the Fortinet member of the mechub MCP server family: a
curated, scoped, audited MCP surface over FortiOS (and later FortiManager),
built mecmcp-native on mecmcp
like rustjunosmcp and
rustpanosmcp.
Planned — on hold until a FortiGate lab device is available. No code yet.
- Phase 1: FortiOS REST v2 (
/api/v2/cmdb,/api/v2/monitor) with API tokens only. Reads for system status, policies, address and service objects, routes and sessions; writes limited to firewall policy and address objects through mecmcp change sets (plan, digest, human approval, apply). - Phase 2: FortiManager JSON-RPC — ADOMs, policy packages, install-to-device.
Design and scope: mecmcp#423.
When implemented, this server must route all device and API output, including error text, through mecmcp-redact via redact_json_value_with_profile, using a FortiOS Profile hook declared in this crate. The generic value-shape scan already catches ENC-prefixed ciphertext, PEM material and password hashes. The FortiOS profile adds wholesale withholding for vendor-rendered bodies and any key exemptions. No tool may return raw device config or API payloads.
Redaction must be applied at the boundary between the vendor read API and the tool result, not in the tool logic itself.
See mecmcp-redact for the complete redaction policy, denylist, and value-shape catch-alls.
Licensed under MIT.