Cisco Secure Firewall FMC MCP Connector
Officialby CiscoDevNet
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| LOG_LEVEL | No | Overall app logging level | DEBUG |
| HTTPX_TRACE | No | Set to 1 to log FMC request URLs and status codes | |
| FMC_BASE_URL | No | Base URL of the FMC instance (e.g., https://<fmc-host>) | |
| FMC_PASSWORD | No | API password for FMC | |
| FMC_USERNAME | No | API username for FMC | |
| FMC_VERIFY_SSL | No | Whether to verify SSL certificate (true/false) | false |
| HTTPX_LOG_LEVEL | No | httpx/httpcore verbosity | WARNING |
| FMC_PROFILES_DIR | No | Directory containing per-FMC profile .env files | |
| FMC_PROFILE_DEFAULT | No | Default profile ID to use when none specified |
Capabilities
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
No tools | |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
Latest Blog Posts
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/CiscoDevNet/CiscoFMC-MCP-server-community'
If you have feedback or need assistance with the MCP directory API, please join our Discord server