Auvik MCP Server

Auvik is an MCP integration. MCP server for the Auvik network monitoring API — devices, alerts, statistics, billing.

Packages and local setup

The published oci package is ghcr.io/wyre-technology/auvik-mcp:v1.4.2. Its declared MCP transport is stdio.

The package declares AUVIK_USERNAME (required): Auvik username (email) used as HTTP Basic auth user; AUVIK_API_KEY (required): Auvik API key (generated in the Auvik portal under Integrations -> APIs); AUVIK_REGION: Auvik regional API host (us1, us2, us3, us4, eu1, eu2, au1, ca1). Omit to auto-detect via /authentication/verify probe.; MCP_TRANSPORT: Transport mode for the server. Set to 'stdio' for local CLI use; the image defaults to 'http' for gateway hosting.; AUTH_MODE: Credential source: 'env' reads vars locally, 'gateway' expects header injection from the WYRE MCP Gateway.; LOG_LEVEL: Log verbosity: debug, info, warn, error.

Before connecting

Check the maintainer’s instructions for account access, authentication and the supported client configuration. Once connected, inspect the tools your client receives and try a small task that matches the server’s stated purpose. The registry description does not include a verified, complete tool list.

Project and source

View the publisher’s registry entry · Project repository · Project website. This profile uses version 1.4.2 from the registry. Registration identifies the publisher namespace; it does not establish that this is a first-party integration for every service it connects.

Browse related payments & commerce MCP servers for tools that cover the same kind of work.