auvik-api-patterns

# Auvik MCP Tools and API Patterns ## Overview The Auvik MCP server wraps the Auvik REST API (`https://auvikapi.{region}.my.auvik.com/v1` and `/v2`) and exposes tools across tenants, devices, networks, interfaces, configurations, alerts, statistics, and billing. Two quirks to know up front: Auvik uses HTTP Basic auth with `username:apiKey` (not a bearer token), and the API base URL is region-pinned - your credentials only work against the cluster your tenant lives in. ## Authentication Auvik authenticates with HTTP Basic - the username is the Auvik user's email and the password is the API key. | Field | Value | |-------|-------| | Auth scheme | HTTP Basic | | Username | `AUVIK_USERNAME` (your Auvik login email) | | Password | `AUVIK_API_KEY` | The MCP server handles the basic-auth encoding. Set the env vars; do not pre-encode. ## Region Routing Auvik tenants live in one of several regional clusters: | Region | Base host | |--------|-----------| | `us1` | `auvikapi.us1.my.auvik.com` | | `us2` | `auvikapi.us2.my.auvik.com` | | `us3` | `auvikapi.us3.my.auvik.com` | | `us4` | `auvikapi.us4.my.auvik.com` | | `eu1` | `auvikapi.eu1.my.auvik.com` | | `eu2` | `auvikapi.eu2.my.auvik.com` | | `au1` | `auvikapi.au1.my.auvik.com` | | `ca1` | `auvikapi.ca1.my.auvik.com` | Set `AUVIK_REGION` to pin the region. If omitted, the server attempts to detect the region from the credentials. Misroutes typically surface as 404 or redirect loops on calls that should obviously succeed. ## J...