Nexus Dashboard MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| NEXUS_PASSWORD | No | Local password; requires NEXUS_USERNAME | |
| NEXUS_USERNAME | No | Local Nexus Dashboard username; requires NEXUS_PASSWORD | |
| NEXUS_API_TOKEN | No | Bearer JWT for authentication | |
| NEXUS_ALLOW_HTTP | No | Permit unencrypted HTTP in a controlled test environment | |
| NEXUS_AUTH_COOKIE | No | Value of the Nexus Dashboard AuthCookie | |
| NEXUS_INSECURE_TLS | No | Disable certificate verification for a trusted lab using a self-signed certificate | |
| NEXUS_DASHBOARD_URL | Yes | Nexus Dashboard base URL, including https:// | |
| NEXUS_WRITE_ENABLED | No | Enable application of prepared changes | |
| NEXUS_ALLOW_DISRUPTIVE | No | Allow operations classified as disruptive | |
| NEXUS_OPENAPI_SPECS_DIR | No | Override the directory containing the two expected OpenAPI JSON filenames | |
| NEXUS_WRITE_CONFIRMATION | No | Private approval value required by nexus_apply_change |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| nexus_list_operationsA | Find documented Nexus Dashboard Infrastructure or Manage API operations. Use this before an unfamiliar read or change. |
| nexus_describe_operationA | Show the exact documented path parameters, query parameters, and JSON request body schema for a Nexus Dashboard operation. |
| nexus_readA | Call a documented read-only (GET) Nexus Dashboard API operation. It never changes configuration. |
| nexus_troubleshoot_switchA | Collect a focused troubleshooting bundle for one switch: fabric status, switch detail, config diff, pending config, deployment history, and interfaces. This is read-only. |
| nexus_prepare_changeA | Validate and preview a non-GET Nexus Dashboard API change without sending it. Returns a one-time change_id required to apply exactly this request. |
| nexus_apply_changeA | Apply a previously previewed change. Requires server-side write enablement and a user-controlled approval code. Disruptive actions have an additional server-side gate. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 6 tools
Each tool has a unique role: generic read, specialized troubleshooting, change preparation, change application, operation discovery, and schema description. No two tools compete for the same action.
All tools follow the pattern `nexus_<verb>_<target>`, with `nexus_read` being a slight exception but still consistent in verb-first style. Uniform snake_case throughout.
Six tools is well-scoped for the server's purpose: two read paths, two change management steps, and two discovery/description tools. Each earns its place with no redundancy.
The server covers the essential workflow: discover operations, understand schemas, perform read-only calls, and safely prepare/apply changes. Minor gap is the lack of a dedicated change-status or history tool, but that is often achievable via read operations.