Nexus Dashboard MCP Server

A comprehensive Model Context Protocol (MCP) server for Cisco Nexus Dashboard, enabling AI agents like Claude to interact with Nexus Dashboard APIs

Local serverstdioPython

What is the Nexus Dashboard MCP MCP server?

A comprehensive Model Context Protocol (MCP) server for Cisco Nexus Dashboard, enabling AI agents like Claude to interact with Nexus Dashboard APIs for intelligent network automation and management. That is what the nexus dashboard mcp mcp server brings to an AI assistant: the same capability, reachable through the Model Context Protocol rather than a separate app or dashboard.

Getting it running

Installation goes through your MCP client rather than a global install: point it at npm on npm and it is fetched when the client starts. The copy-paste blocks for Claude Desktop, Claude Code and Cursor are further down this page.

The tools it exposes

The server publishes 1 tool. What each one is for:

  • Prerequisites — The Prerequisites tool exposed by this server

What it needs from you

Configuration is passed through the environment: ENCRYPTION_KEY, SESSION_SECRET_KEY, NEXUS_CLUSTER_URL, MCP_API_TOKEN. Treat anything key-shaped as a real credential — scope it to the minimum the server needs, and rotate it if it ever lands in a shared config.

  • Docker 20.10+ and Docker Compose 2.0+ - Cisco Nexus Dashboard 4.1+ with NDFC 12.x - Node.js 18+ (for remote MCP access via mcp-remote)

Things to watch

  • 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.
  • Missing credentials fail quietly in some clients — if no tools show up, check the environment block first.
  • Keep per-call confirmation enabled while you learn its behaviour; it is the cheapest safeguard you have.

How it compares

Plenty of developer tooling servers cover similar ground. The differences that matter in practice are scope of access and how much setup stands between you and a working tool call. Nexus Dashboard MCP's toolset — Prerequisites — is a fair guide to whether it matches your workflow. It is maintained by beye91; worth a glance at recent repository activity before you build anything load-bearing on it.

SyncDev reviews every entry in this directory against the project's own documentation before publishing, and revisits them as servers change.

Available tools

ToolWhat it does
PrerequisitesThe Prerequisites tool exposed by this server.

How to install the Nexus Dashboard MCP MCP server

{
  "mcpServers": {
    "nexus-dashboard": {
      "command": "npx",
      "args": ["-y", "npm"],
      "env": {
        "ENCRYPTION_KEY": "your-value",
        "SESSION_SECRET_KEY": "your-value",
        "NEXUS_CLUSTER_URL": "your-value",
        "MCP_API_TOKEN": "your-value"
      }
    }
  }
}

Add to claude_desktop_config.json, then restart Claude Desktop.

Configuration

  • Docker 20.10+ and Docker Compose 2.0+ - Cisco Nexus Dashboard 4.1+ with NDFC 12.x - Node.js 18+ (for remote MCP access via mcp-remote)
VariableDescriptionRequired
ENCRYPTION_KEYCredential the server authenticates with.Yes
SESSION_SECRET_KEYCredential the server authenticates with.Yes
NEXUS_CLUSTER_URLEndpoint or connection string the server talks to.Yes
MCP_API_TOKENCredential the server authenticates with.Yes

Example prompts to try

  • Use Nexus Dashboard MCP to Prerequisites.

Frequently asked questions

It connects Nexus Dashboard MCP to MCP-compatible AI assistants such as Claude and Cursor, exposing 1 tool (Prerequisites) that the assistant can call on your behalf. Instead of copying data back and forth by hand, the assistant works with Nexus Dashboard MCP directly.