Aci MCP Server

Aci MCP MCP server exists for a simple reason — assistants are far more useful when they can act on Aci MCP directly instead of describing what you should do. MCP server for Cisco ACI (Application Centric Infrastructure) management.

What you get

A comprehensive MCP server for configuring and managing Cisco ACI (Application Centric Infrastructure) fabrics through the APIC REST API.

This MCP server provides 35+ tools for complete ACI fabric management, including:

What the assistant can call

Once Aci MCP is connected, these are the calls the assistant has available:

• list_tenants — List all tenants
• get_tenant — Get specific tenant details
• create_tenant — Create new tenant
• update_tenant — Update tenant configuration
• delete_tenant — Delete tenant
• list_application_profiles — List application profiles
• get_application_profile — Get specific application profile
• create_application_profile — Create new application profile
• update_application_profile — Update application profile
• delete_application_profile — Delete application profile
• list_endpoint_groups — List endpoint groups
• get_endpoint_group — Get specific EPG details

Setting it up

Setup follows the usual MCP pattern — install or clone the server, register it in your client's configuration file, restart the client.

Configuration and credentials

You will need 7 environment variables: ACI_APIC_URL, ACI_USERNAME, ACI_PASSWORD, ACI_CERT_NAME, ACI_PRIVATE_KEY_PATH, ACI_TOOL_MODE, ACI_TENANT_FOCUS. The server will not start without them, which is usually why the tools fail to appear on a first run. Keep credentials in your client's env block or a secrets manager rather than in a file you might commit.

• Node.js 18+ and npm - Access to a Cisco APIC controller - Valid APIC credentials (username/password or certificate)

Choosing this one

This sits in the cloud and infrastructure group, where several servers overlap in what they claim to do but differ sharply once you actually set them up. Aci MCP's toolset — list_tenants, get_tenant, create_tenant and 11 more — is a fair guide to whether it matches your workflow. It is maintained by jim-coyne; worth a glance at recent repository activity before you build anything load-bearing on it.

This entry was verified against Aci MCP's own documentation before publication; SyncDev keeps the directory reviewed rather than auto-generated.

Before you rely on it

• It runs with your machine's permissions. That is convenient and also the reason to think about what you point it at before you approve a tool call.
• With 14 tools registered it takes up a noticeable share of the context window; turn it off in projects that never touch Aci MCP.
• Missing credentials fail quietly in some clients — if no tools show up, check the environment block first.
• MCP clients confirm each tool call by default. Leave that on until you have watched what the aci mcp mcp server does with a few real requests.