Skip to main content
Glama
Choaterboater

casper-network-mcp

by Choaterboater
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
MIST_HOSTNoJuniper Mist host if your cloud is not api.mist.com.api.mist.com
MIST_API_TOKENNoJuniper Mist API token.
CENTRAL_BASE_URLNoHPE Aruba Networking Central base URL.
CENTRAL_CLIENT_IDNoHPE Aruba Networking Central client ID.
CLEARPASS_BASE_URLNoHPE Aruba Networking ClearPass base URL.
CLEARPASS_API_TOKENNoHPE Aruba Networking ClearPass API token.
CENTRAL_CLIENT_SECRETNoHPE 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.

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

CapabilityDetails
tools
{
  "listChanged": false
}
prompts
{
  "listChanged": false
}
resources
{
  "subscribe": false,
  "listChanged": false
}

Tools

Functions exposed to the LLM to take actions

NameDescription
find_toolA

Find the tool for a task. Call this first.

    query: what you want to do, in plain words ("bounce port 7 on the
    closet switch") or an exact API call ("GET /api/v1/sites/{site_id}").
    product: central, mist, clearpass or specs (the API document lookup).
    Each hit has name, product, summary, kind (read, troubleshoot, config,
    disruptive, firmware, delete or admin) and label. Pass include_schema
    to get the arguments a tool takes. Then call invoke_read_tool (kind
    read or troubleshoot) or invoke_tool.
invoke_read_toolA

Run a tool that only reads, or runs a check that changes nothing (from find_tool).

    A tool that can change something is refused with "not_a_read_tool".
    cursor: the next_cursor from a reply that was cut short, to get the rest.
invoke_toolB

Run any tool from find_tool, including ones that change the network.

    The tool's own kind (from find_tool) says what it changes.
access_checkB

What each product login can do, and whether this server is read-only.

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

Deploy Server
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

TDQS

A3.7/5.0

Scored across 4 tools

Disambiguation4/5

find_tool is clearly the discovery step, and access_check is distinct. invoke_read_tool and invoke_tool overlap because invoke_tool can also perform reads, but the descriptions clearly distinguish read-only vs. any operation, so an agent can select based on safety intent.

Naming Consistency4/5

Three of four tools follow a verb_noun pattern (find_tool, invoke_read_tool, invoke_tool), and all use snake_case. access_check breaks the verb-first convention but remains readable and semantically clear.

Tool Count5/5

Four tools is well-scoped for a gateway server that proxies many underlying network APIs. Each tool has a distinct role: discovery, read-only invocation, general invocation, and access inspection.

Completeness4/5

The surface covers discovery, read-only execution, general execution, and permission checking, which are the core operations for this meta-server. Minor gaps include no explicit list-all-tools or describe-by-name operation, though find_tool with a query likely covers these use cases.

Maintenance

ActivityMaintained
ResponsivenessNo issues

Resources