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 a non-disruptive troubleshooting check (ping, show). Names come from find_tool.

    Cable tests can interrupt a link and require invoke_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.
    login: a named Central login from access_check (default: the main one).
    all_pages: fetch every page of a list here (up to 50 pages / 10,000 items) instead of one.
    fields: keep only these keys of each item ("radio.channel" reaches inside); cuts big replies.
    group_by: return a count per value of this field instead of the items ("firmwareVersion").
    Together they answer site-wide questions in one call: all_pages + group_by="status".
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.
    login: a named Central login from access_check (default: the main one).
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

The four tools have largely distinct roles: discovery (find_tool), authentication/status (access_check), safe execution (invoke_read_tool), and full execution (invoke_tool). The read/write split between the two invoke tools is clear and enforced, though agents must first discover a tool's kind before choosing the right invoker.

Naming Consistency4/5

Three tools follow a verb_noun pattern (find_tool, invoke_tool, invoke_read_tool), while access_check uses noun_verb ordering. This is a minor deviation and all names remain readable and semantically clear.

Tool Count5/5

Four meta-tools are exactly right for a gateway that fronts a large external API surface via discovery rather than exposing every endpoint directly. Each tool has a distinct, necessary role.

Completeness4/5

The surface covers discovery with schema lookup, authentication inspection, read-only execution, and mutating execution, with pagination and field filtering handled in the read path. A direct way to list all available tool kinds without a query is absent but workable through find_tool.

Maintenance

ActivityMaintained
ResponsivenessNo issues

Resources