Power your agent
Install from the publisher. Not a PlugMCP endpoint.
Host a copy with our keys and logs.
No packaged release in the registry yet. Follow the repository README.
Remote URL or a command on your machine? How the two installs differ
Run on PlugMCP
A new server you create. It is not this listing's official endpoint. Use the publisher install when you want their URL and their credentials.
LaunchFrom the publisher
MCP Server for Cisco ACI
This MCP server acts as a lightweight middleware layer between Cisco ACI (Application Centric Infrastructure) and any MCP-compatible client. It allows an LLM to query the ACI fabric, inspect tenants, EPGs, bridge domains, faults, and fabric health — and to create or delete policy objects — all through structured MCP tools.
This is a community based project and is not officially supported by any Cisco Business or Technical entity.
The server communicates with the APIC REST API using cookie-based authentication and supports 50 operations covering the full ACI policy model.
.env filePython dependencies (requirements.txt):
The server in scripts/server.py runs in stdio mode. VS Code manages the process lifecycle automatically via mcp.json.
Clone the repository and run the interactive setup script:
git clone <your-repo-url>
cd aci_mcp_devnet_submission
./setup.sh
The setup.sh script will:
scripts/.envpipAlternatively, set up manually:
cd aci_mcp_devnet_submission
pip install -r requirements.txt
# Create scripts/.env manually:
cat > scripts/.env <<EOF
APIC_URL=https://<your-apic-ip>/
USERNAME=<your-username>
PASSWORD=<your-password>
EOF
The server authenticates to the APIC using cookie-based session authentication (aaaLogin). Credentials are loaded from scripts/.env at startup.
scripts/.env format:
APIC_URL=https://10.x.x.x/
USERNAME=admin
PASSWORD=yourpassword
The server automatically re-authenticates when the APIC session token expires (HTTP 403), so long-running sessions stay connected without manual intervention.
Security note: The
scripts/.envfile is listed in.gitignore— never commit real credentials to source control.
cd scripts
python3 server.py
cd aci_mcp_devnet_submission
./setup.sh
# Follow prompts, then:
cd scripts && python3 server.py
cd scripts
fastmcp dev server.py
GitHub Copilot in VS Code 2 has a built-in MCP client. Add the ACI MCP server to your VS Code mcp.json to use it directly from the Copilot chat window.
Open your VS Code user mcp.json (Cmd+Shift+P → Open MCP Servers Configuration) and add:
{
"servers": {
"my-aci-mcp-server": {
"type": "stdio",
"command": "python3",
"args": [
"/absolute/path/to/aci_mcp_devnet_submission/scripts/server.py"
]
}
}
}
Replace
/absolute/path/to/with the actual path on your machine.
VS Code starts the server automatically when you open a Copilot chat session. You can also manually start/restart it from the MCP panel in the VS Code status bar.
Open GitHub Copilot Chat (Cmd+Shift+I) and try natural language prompts:
📋 Query the fabric:
Show me all faults in the fabric
List the top 10 tenants
What is the current fabric health score?
🏗️ Provision policy:
Create a new tenant called "MyApp_Tenant"
Deploy a 3-tier application called "ECommerceApp" in tenant "Prod_Tenant"
Add a subnet 192.168.10.1/24 to bridge domain "app_bd" in tenant "Prod_Tenant"
🩺 Troubleshoot:
Show me all critical faults
Get all BGP peers in the fabric
List all endpoints currently learned in the fabric
The LLM will automatically select the right MCP tool(s), call the APIC REST API, and return structured results in the chat window.
MCP Server for Cisco ACI
Tools
No tool list yet. Remote servers get one after the first health check.
FAQ
Copy the stdio config for Cursor, Claude Desktop, Claude Code, or VS Code on this page. It uses the publisher's install, not a PlugMCP proxy.
No required environment variable is listed on this record.
MCP Server Cisco Aci Community runs locally over stdio.
Last checked 2026-10-28. MCP Server for Cisco ACI