casper-network-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| MIST_HOST | No | Juniper Mist host if your cloud is not api.mist.com. | api.mist.com |
| MIST_API_TOKEN | No | Juniper Mist API token. | |
| CENTRAL_BASE_URL | No | HPE Aruba Networking Central base URL. | |
| CENTRAL_CLIENT_ID | No | HPE Aruba Networking Central client ID. | |
| CLEARPASS_BASE_URL | No | HPE Aruba Networking ClearPass base URL. | |
| CLEARPASS_API_TOKEN | No | HPE Aruba Networking ClearPass API token. | |
| CENTRAL_CLIENT_SECRET | No | HPE Aruba Networking Central client secret. |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
Network tools for HPE Aruba Central, Juniper Mist, HPE Aruba ClearPass, HPE Aruba UXI and HPE OpsRamp. Call find_tool with what you want to do, then invoke_read_tool for reads and checks, or invoke_tool for changes. access_check says what each login can do, and lists any extra named Central logins; pass login= to invoke_read_tool or invoke_tool to use one.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| find_toolA | Find the tool for a task. Call this first. |
| invoke_read_toolA | Run a tool that only reads, or a non-disruptive troubleshooting check (ping, show). Names come from find_tool. |
| invoke_toolB | Run any tool from find_tool, including ones that change the network. |
| access_checkB | What each product login can do, and whether this server is read-only. |
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 4 tools
The workflow is clearly staged: find_tool discovers, access_check reports permissions, and the two invoke tools execute. The only fuzzy boundary is invoke_read_tool vs invoke_tool, since invoke_tool claims to run 'any tool from find_tool', including reads, but the read variant's extra pagination/field/group_by options make the intended split understandable.
All names are snake_case and readable, with two clear verb_verb_noun pairs (invoke_read_tool, invoke_tool) and find_tool. access_check breaks the verb_noun pattern by being noun-first, a minor deviation rather than a real inconsistency.
Four tools is a sensible fixed facade for a gateway that multiplexes six products via dynamic discovery. There is slight redundancy in having invoke_tool capable of doing everything invoke_read_tool does, but the extra read-only conveniences justify keeping both.
Discovery, permission inspection, schema retrieval (include_schema), pagination, and both safe and destructive execution are all covered, which is solid for a meta-server. Gaps are minor: there is no way to enumerate all available tools or list by product without a free-text query, and no login/credential management beyond naming a login.