CC

ciscodevnet/ciscofmc-mcp-server-community

Developer toolsОфициальный

Эта страница переведена автоматически. Технические детали смотрите в оригинале. Открыть оригинал

7 stars 9 forks Качество 79 Тренд 19MIT

MCP server that exposes high-level tooling for Cisco Secure Firewall Management Center (FMC). Core tools:

Обзор

MCP server that exposes high-level tooling for Cisco Secure Firewall Management Center (FMC). Core tools: - list_fmc_profiles – discover configured FMC instances. - find_rules_by_ip_or_fqdn – search a specific access policy. - find_rules_for_target – resolve an FTD device/HA/cluster to its assigned policies and search them. - search_access_rules – FMC-wide searches with indicator + policy filters, including identity indicators (SGT, realm user/group). Copy .env.example to .env (or export env vars) and fill in at least: Define one env file per FMC under profiles/. Copy profiles/.env.example to a new filename (e.g., profiles/fmc-north-south.env) and fill it: When FMC_PROFILES_DIR is set, the server auto-loads every *.env file in that folder and exposes them via list_fmc_profiles. If it’s unset, the single-FMC env variables are used. Logging levels can be set in the active profile file (profile mode) or in the root .env (single-FMC mode or Docker env).

README

Показан фрагмент оригинального README. Открыть оригинал.

Cisco Secure Firewall FMC MCP Connector

MCP server that exposes high-level tooling for Cisco Secure Firewall Management Center (FMC). Core tools:

  • list_fmc_profiles – discover configured FMC instances.
  • find_rules_by_ip_or_fqdn – search a specific access policy.
  • find_rules_for_target – resolve an FTD device/HA/cluster to its assigned policies and search them.
  • search_access_rules – FMC-wide searches with indicator + policy filters, including identity indicators (SGT, realm user/group).

1. Configure FMC access

Single FMC (env mode)

Copy .env.example to .env (or export env vars) and fill in at least:

FMC_BASE_URL=https://
FMC_USERNAME=
FMC_PASSWORD=
FMC_VERIFY_SSL=false

Multiple FMCs (profile mode)

Define one env file per FMC under profiles/. Copy profiles/.env.example to a new filename (e.g., profiles/fmc-north-south.env) and fill it:

FMC_PROFILE_ID=fmc-north-south
FMC_PROFILE_DISPLAY_NAME=FMC North-South
FMC_PROFILE_ALIASES=north,north-south,10.0.0.5
FMC_BASE_URL=https://10.0.0.5
FMC_USERNAME=adminapi
FMC_PASSWORD=***
FMC_VERIFY_SSL=false

Point the server at this directory:

FMC_PROFILES_DIR=profiles
FMC_PROFILE_DEFAULT=fmc-north-south

When FMC_PROFILES_DIR is set, the server auto-loads every *.env file in that folder and exposes them via list_fmc_profiles. If it’s unset, the single-FMC env variables are used.

Logging and HTTP tracing

Logging levels can be set in the active profile file (profile mode) or in the root .env (single-FMC mode or Docker env). The default profile’s logging values are applied at startup.

LOG_LEVEL=DEBUG           # overall app logging
HTTPX_TRACE=1             # log FMC request URLs and status codes
HTTPX_LOG_LEVEL=WARNING   # httpx/httpcore verbosity (default WARNING)

Notes:

  • In profile mode, put these in the default profile file (the one named by FMC_PROFILE_DEFAULT).
  • In Docker, the root .env (or docker-compose.yml environment) must still provide server-level settings like FMC_PROFILES_DIR, FMC_PROFILE_DEFAULT, MCP_HOST, and MCP_PORT.

2. Run the MCP server

Transport selection

The transport is chosen with the MCP_TRANSPORT environment variable:

MCP_TRANSPORT Behavior Typical use
stdio (default) Server speaks MCP over stdin/stdout. No network port is opened. Desktop MCP clients that spawn the server as a subprocess (Claude Desktop, VS Code, Cursor, etc.).
http Server listens on MCP_HOST:MCP_PORT and serves /mcp. Shared/remote deployments, Docker, multiple concurrent agents.

If MCP_TRANSPORT is unset, the server starts in stdio mode.

Docker

docker compose up -d --build
Открыть полный README на GitHub

Установка

This server does not publish a one-line install command.

Open the repository installation guide Новичок в MCP? Начните с руководства на mcpskill.org →

Конфигурация

{ "mcpServers": { "cisco-fmc": { "command": "python", "args": ["-m", "sfw_mcp_fmc.server"], "cwd": "/absolute/path/to/CiscoFMC-MCP-server-community", "env": { "MCP_TRANSPORT": "stdio", "FMC_PROFILES_DIR": "profiles", "FMC_PROFILE_DEFAULT": "fmc-north-south" } } } }