MCP.so
ログイン
C

Cisco ACI MCP Server

@jim-coyne

基本情報

カテゴリ

その他

トランスポート

stdio

作者

jim-coyne

投稿者

Jim-Coyne

Cisco ACI MCP Server について

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

Cisco ACI MCP Server の設定

以下の設定を使って、このサーバーを MCP 対応クライアントに追加してください。

{
  "mcpServers": {
    "aci": {
      "command": "node",
      "args": [
        "dist/index.js"
      ],
      "cwd": "/path/to/aci-mcp-server"
    }
  }
}

Cisco ACI MCP Server のツール

ツール一覧はまだありません

この掲載には表示できるツール一覧がまだありません。サーバーにツールがないという意味ではありません。対応機能はプロジェクトのドキュメントをご確認ください。

ツールは README から自動的に抽出されます。メンテナーは ## Tools という見出しの下に記載することで、このタブに反映できます。

概要

What is Cisco ACI MCP Server?

A comprehensive MCP server for configuring and managing Cisco ACI (Application Centric Infrastructure) fabrics through the APIC REST API. It provides 35+ tools for tenant, application profile, endpoint group, bridge domain, VRF, contract, health monitoring, and node management, aimed at network engineers and administrators.

How to use Cisco ACI MCP Server?

Install Node.js 18+ and npm, clone the repository, run npm install, configure authentication via environment variables or a configuration file (using username/password or X.509 certificate), build with npm run build, then start with npm start. Additional configuration for tool mode and tenant focus can be done through a aci-mcp-config.json file or environment variables.

Key features of Cisco ACI MCP Server

  • 35+ tools for complete ACI fabric management
  • Tenant lifecycle management (create, read, update, delete)
  • Application profile and endpoint group (EPG) management
  • Bridge domain and VRF configuration
  • Contract and filter definition for security policies
  • Fabric health monitoring, fault listing, and node/interfaces management

Use cases of Cisco ACI MCP Server

  • Automating tenant and application profile provisioning across ACI fabrics
  • Configuring endpoint groups, bridge domains, and VRFs programmatically
  • Defining and applying security contracts and filters
  • Monitoring fabric health, faults, and interface statistics
  • Managing fabric nodes and their interfaces

よくある質問

1

What authentication methods are supported?

Two methods: username/password (standard APIC login) and X.509 certificate-based authentication (recommended for production).

2

What are the required dependencies?

Node.js 18+, npm, access to a Cisco APIC controller, and valid APIC credentials (username/password or certificate).

3

How can I control which tools are available?

Set the tool selection mode in `aci-mcp-config.json` (whitelist, enableAllTools) or use environment variables `ACI_TOOL_MODE` (core for 35 tools, all for 50+ tools) and `ACI_TENANT_FOCUS`.

4

Where does the server get its data?

All data is retrieved from and sent to the Cisco APIC REST API. The server connects to the APIC controller using the configured URL and credentials.

5

How do I set authentication credentials?

Use environment variables (`ACI_APIC_URL`, `ACI_USERNAME`, `ACI_PASSWORD`, or `ACI_CERT_NAME` and `ACI_PRIVATE_KEY_PATH`) or edit the `aci-config.json` configuration file with your APIC details.

コメント

「その他」の他のコンテンツ