Cisco FMC

Provides read-only access to FMC 7.4.x data sources and common actions via MCP.

python

0

GitHub Stars

python

Language

6 months ago

First Indexed

3 months ago

Catalog Refreshed

Documentation & install

Readme and setup notes from the catalogue, plus a client-ready config you can copy for your MCP host.

Installation

Add the following to your MCP client configuration file.

Configuration

View docs

{
  "mcpServers": {
    "zoemdoef-cisco-fmc-mcp": {
      "command": "uv",
      "args": [
        "run",
        "python",
        "-m",
        "fmc_mcp"
      ],
      "env": {
        "FMC_HOST": "fmc.example.com",
        "FMC_TIMEOUT": "60",
        "FMC_PASSWORD": "YOUR_PASSWORD",
        "FMC_USERNAME": "api_user",
        "FMC_VERIFY_SSL": "false",
        "FMC_DOMAIN_UUID": "auto"
      }
    }
  }
}

This MCP server lets you query Cisco FMC 7.4.x configurations in read-only mode using natural language. You can look up system information, list firewalls, inspect network objects, and check deployment status without making changes. It handles FMC authentication, paginated data, and enforces rate limits to protect your appliance.

How to use

You interact with the FMC MCP server through an MCP client. Start the server locally, then connect your client to the local runtime. You can ask questions like what version your FMC is running, list all managed devices, find a network object by IP, or check if there are pending deployments. Use the client’s query features to browse data, and rely on the built-in rate limiter to stay within FMC limits.

Typical usage patterns include starting the server on your development machine, validating the connection, and then issuing natural-language requests such as:

What is the FMC version?
List all firewall devices
Find the network object for IP 10.10.10.5
Are there any pending deployments?

How to install

Prerequisites you need on your system before running the server:

Python 3.10+
uvx runtime recommended or pip
Access to a Cisco FMC 7.4.x instance

Install options you can choose from to run the MCP server locally.

# Option 1: Using uvx (recommended)
# Clone the MCP server repository
git clone https://github.com/your-org/fmc-mcp.git
cd fmc-mcp

# Install dependencies (uvx handles Python environments)
uv sync

# Start the server
uv run python -m fmc_mcp

Additional content

Configuration and security notes help you keep your FMC data safe while using the MCP server.

Environment variables you need to configure in a local environment file (for FMC access):

FMC_HOST: FMC hostname or IP
FMC_USERNAME: API username
FMC_PASSWORD: API password
FMC_VERIFY_SSL: SSL verification (default false)
FMC_DOMAIN_UUID: Domain UUID (auto if not provided)
FMC_TIMEOUT: Request timeout in seconds (default 60)

Running the server with explicit FMC credentials is done via an environment file (for example, a .env file). Do not commit credentials to version control.
Security considerations:

Read-only access ensures no configuration changes are made.
SSL verification can be disabled in lab environments but should be enabled in production.
Use a dedicated read-only FMC API user to minimize risk.

Data sources and tools exposed by this MCP server:

FMC system info
List of devices
All network objects
Deployment status
Search object by IP
Check deployment status

Available tools

search_object_by_ip

Find network objects containing a specific IP address across FMC network objects.

get_deployment_status

Check if devices have pending or in-sync deployments.