Auvik Mcp

Please install the `auvik-mcp` MCP server into my current AI client (that's you).

Required prerequisites (do these first if not already done):
- **Obtain Auvik API credentials** — Create or obtain your Auvik username and API key. These are required for direct stdio usage and are also required as request headers when using HTTP gateway mode. (https://api.auvik.com/documentation)

Optional prerequisites:
- Install Docker — Required if you choose to run the server as a container for HTTP transport. (https://www.docker.com/)
- Pull the Auvik MCP container image — Download the published container image before running the server over HTTP with Docker. Run: `docker pull ghcr.io/wyre-technology/auvik-mcp:latest`

Canonical MCP server config (stdio transport):
- command: `docker`
- args: ["run","-i","--rm","-e","AUVIK_USERNAME","-e","AUVIK_API_KEY","-e","AUVIK_REGION","ghcr.io/wyre-technology/auvik-mcp:latest"]
- required environment variables:
  - `AUVIK_USERNAME`: Your Auvik username for API authentication. (example: `<your-auvik-username>`)
  - `AUVIK_API_KEY`: Your Auvik API key for API authentication. (example: `<your-auvik-api-key>`)
- optional environment variables:
  - `AUVIK_REGION`: Auvik API region. Optional; defaults to us1. Valid examples include us1, us2, us3, us4, us5, us6, lnx, eu1, eu2, au1, ca1. (example: `<your-auvik-region>`)

Note: The README supports both stdio and HTTP transports. For direct stdio use, credentials are supplied via environment variables. For HTTP gateway mode, credentials are supplied per request using x-auvik-username and x-auvik-api-key headers; x-auvik-region is optional. The most portable published install path shown is the Docker image.

Add this MCP server to my current client's config in the correct format for you. If you need secrets or credentials I haven't provided, ASK me — do not invent values or leave raw placeholders. After adding it, tell me how to verify the server is connected.