Auvik

io.github.WYRE-AI/auvik-mcp · v1.4.6

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

Website Source code Set it up

Connect Runs on your machine

Terminal

claude mcp add auvik-mcp -e AUVIK_USERNAME=<AUVIK_USERNAME> -e AUVIK_API_KEY=<AUVIK_API_KEY> -e AUVIK_REGION=<AUVIK_REGION> -e MCP_TRANSPORT=<MCP_TRANSPORT> -e AUTH_MODE=<AUTH_MODE> -e LOG_LEVEL=<LOG_LEVEL> -- docker run -i --rm ghcr.io/wyre-ai/auvik-mcp:v1.4.6

claude_desktop_config.json

{
  "mcpServers": {
    "auvik-mcp": {
      "command": "docker",
      "args": [
        "run",
        "-i",
        "--rm",
        "ghcr.io/wyre-ai/auvik-mcp:v1.4.6"
      ],
      "env": {
        "AUVIK_USERNAME": "<AUVIK_USERNAME>",
        "AUVIK_API_KEY": "<AUVIK_API_KEY>",
        "AUVIK_REGION": "<AUVIK_REGION>",
        "MCP_TRANSPORT": "<MCP_TRANSPORT>",
        "AUTH_MODE": "<AUTH_MODE>",
        "LOG_LEVEL": "<LOG_LEVEL>"
      }
    }
  }
}

~/.cursor/mcp.json

{
  "mcpServers": {
    "auvik-mcp": {
      "command": "docker",
      "args": [
        "run",
        "-i",
        "--rm",
        "ghcr.io/wyre-ai/auvik-mcp:v1.4.6"
      ],
      "env": {
        "AUVIK_USERNAME": "<AUVIK_USERNAME>",
        "AUVIK_API_KEY": "<AUVIK_API_KEY>",
        "AUVIK_REGION": "<AUVIK_REGION>",
        "MCP_TRANSPORT": "<MCP_TRANSPORT>",
        "AUTH_MODE": "<AUTH_MODE>",
        "LOG_LEVEL": "<LOG_LEVEL>"
      }
    }
  }
}

.vscode/mcp.json

{
  "servers": {
    "auvik-mcp": {
      "type": "stdio",
      "command": "docker",
      "args": [
        "run",
        "-i",
        "--rm",
        "ghcr.io/wyre-ai/auvik-mcp:v1.4.6"
      ],
      "env": {
        "AUVIK_USERNAME": "<AUVIK_USERNAME>",
        "AUVIK_API_KEY": "<AUVIK_API_KEY>",
        "AUVIK_REGION": "<AUVIK_REGION>",
        "MCP_TRANSPORT": "<MCP_TRANSPORT>",
        "AUTH_MODE": "<AUTH_MODE>",
        "LOG_LEVEL": "<LOG_LEVEL>"
      }
    }
  }
}

Replace the values in angle brackets with your own. Keys stay on your machine; we never see them.

Tools

This server runs locally, so its tools are listed by your MCP client once it starts.

Environment variables

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

Details

Package	`ghcr.io/wyre-ai/auvik-mcp:v1.4.6` (OCI, stdio)
First published	10 Oct 2026
Last updated	10 Oct 2026
Registry name	`io.github.WYRE-AI/auvik-mcp`

More data and analytics servers See all

Live status

Local install

Installed and run on your own machine, so there is no public endpoint to check.

Pair it with live search

Agents that use Auvik often also need current facts. NestDaddy MCP gives your AI today's internet: web search, real-time breaking news and full page reading in one connector.

See NestDaddy MCP

For maintainers

[![NestDaddy MCP](https://nestdaddy.com/mcp/servers/io-github-wyre-ai-auvik-mcp/badge.svg)](https://nestdaddy.com/mcp/servers/io-github-wyre-ai-auvik-mcp)

Add the badge to your README. It turns green while your server passes our daily check. Listing details come from the official MCP registry; update them there.

Listing data from the official MCP registry. Status and tools from NestDaddy's daily check. Browse all MCP servers.