How do I use Auvik MCP Server?

1. Click on "Deploy Server". 2. Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state. 3. In the chat, type @ followed by the MCP server name and your instructions, e.g., "@Auvik MCP Server list all offline devices across my tenants" That's it! The server will respond to your query, and you can continue using it as needed. Here is a step-by-step guide with screenshots.

Auvik MCP Server

by MSPbotsAIFramework

Overview Schema Source Related Servers Discussions Admin

Python

Remote

Auvik MCP Server

An MCP server for the Auvik network monitoring API. It lets an AI agent read an MSP's Auvik data: tenants, discovered devices, networks, interfaces, configuration backups, alerts, performance statistics and billing usage.

Transport: MCP Streamable HTTP at POST /mcp, health probe at GET /health
Stateless and multi-tenant: credentials arrive on every request as HTTP headers and are never stored
Python 3.12, uv, FastMCP, httpx
License: Apache-2.0, Copyright 2026 MSPbots.ai

Authentication headers

Header	Required	Type	Default	Allowed values	Description	Example
`X-Auvik-Username`	Yes	string	none	-	Auvik user name (login e-mail) that owns the API key	`user@example.com`
`X-Auvik-Api-Key`	Yes	string	none	-	API key of that user	`YOUR_API_KEY`
`X-Auvik-Region`	No	string	`us1`	`us1`, `us2`, `us3`, `us4`, `us5`, `us6`, `lnx`, `eu1`, `eu2`, `au1`, `ca1`	Auvik cluster of the account; the API host is `auvikapi.<region>.my.auvik.com`	`eu1`

Where to get them:

API key: generated per Auvik user from the user's profile in the Auvik web UI. See Auvik's article Generating an API key.
Region: the Auvik cluster your account is hosted on (for example us1 or eu1). If you are unsure, run auvik_status with each candidate region; only the right one should authenticate.
Permissions: the user's role decides what the API can read. A read-only role covers every tool except auvik_alerts_dismiss, which needs a role allowed to manage alerts. See Auvik role permissions.

A request to /mcp without the required headers gets HTTP 401 with the list of required headers; an unknown region gets HTTP 400.

Related MCP server: Meraki Monitor MCP

Tools

All tools return a JSON string. List tools return {items, count, has_more, next_cursor}; pass next_cursor as pageAfter to get the next page. pageSize defaults to 50 (max 200). Most tools take an optional tenants (comma-separated tenant IDs from auvik_tenants_list); without it they cover every tenant the API user can access.

Tool	Purpose	Parameters (required in bold)
`auvik_status`	Check that the credentials are valid	-
`auvik_navigate`	API docs, support and status links for the region	-
`auvik_tenants_list`	List the MSP account and its client tenants	-
`auvik_tenants_get`	One tenant's basic record	tenantId
`auvik_tenants_detail`	One tenant's detail, incl. API availability	tenantId, tenantDomainPrefix
`auvik_devices_list`	List devices	pageSize, pageAfter, tenants, filter_deviceType, filter_modifiedAfter, filter_vendorName, filter_onlineStatus, filter_makeModel, filter_networks
`auvik_devices_get`	One device's info	deviceId
`auvik_devices_get_details`	One device's discovery/manage status	deviceId
`auvik_devices_get_warranty`	One device's warranty coverage	deviceId
`auvik_devices_get_lifecycle`	One device's lifecycle / end-of-support	deviceId
`auvik_networks_list`	List networks (subnets, VLANs, Wi-Fi)	pageSize, pageAfter, tenants, filter_networkType, filter_modifiedAfter, filter_devices
`auvik_networks_get`	One network with its detail	networkId
`auvik_interfaces_list`	List interfaces	pageSize, pageAfter, tenants, filter_parentDevice, filter_interfaceType, filter_operationalStatus, filter_adminStatus
`auvik_configurations_list`	List configuration backups	pageSize, pageAfter, tenants, filter_devices, filter_backupTimeAfter, filter_backupTimeBefore, filter_isRunning
`auvik_configurations_get`	One configuration backup	configId
`auvik_entities_list_notes`	Notes on devices/networks/interfaces	pageSize, pageAfter, tenants, filter_entityId, filter_entityType, filter_entityName, filter_modifiedAfter
`auvik_entities_list_audits`	Remote-access session audit records	pageSize, pageAfter, tenants, filter_user, filter_category, filter_status, filter_modifiedAfter
`auvik_alerts_list`	List alert history	filter_detectedTimeAfter, filter_detectedTimeBefore, filter_status, filter_severity, filter_dismissed, filter_entityId, pageSize, pageAfter, tenants
`auvik_alerts_get`	One alert	alertId
`auvik_alerts_dismiss`	Dismiss one alert (changes data)	alertId
`auvik_statistics_device`	Device metrics over time	statId, fromTime, interval, thruTime, filter_devices, pageSize, pageAfter, tenants
`auvik_statistics_interface`	Interface metrics over time	statId, fromTime, interval, thruTime, filter_interfaces, filter_parentDevice, pageSize, pageAfter, tenants
`auvik_statistics_service`	Ping time / packet loss of monitored services	statId, fromTime, interval, thruTime, filter_services, pageSize, pageAfter, tenants
`auvik_statistics_snmp_poller`	Custom SNMP poller value history	statId (`int`/`string`), filter_pollers, filter_deviceId, fromTime, thruTime, interval, pageSize, pageAfter, tenants
`auvik_billing_client_usage`	Billable usage per client	fromDate, thruDate, tenants
`auvik_billing_device_usage`	Billable usage of one device	deviceId, fromDate, thruDate
`auvik_raw_request`	Any other documented `/v1` endpoint (POST changes data)	path, method, query, body

Metric values for statId:

device: bandwidth, cpuUtilization, memoryUtilization, storageUtilization, packetUnicast, packetMulticast, packetBroadcast
interface: bandwidth, utilization, packetLoss, packetDiscard, packetMulticast, packetUnicast, packetBroadcast
service: pingTime, pingPacket

Times are ISO 8601 (2026-01-31T00:00:00.000Z); billing dates are YYYY-MM-DD.

Errors come back as a JSON envelope instead of an exception:

{"error": {"code": "unauthorized", "message": "Auvik returned HTTP 401: ...", "retryable": false}}

code is one of not_configured, unauthorized, not_found, invalid_argument, rate_limited, upstream_error.

Run locally

uv sync
uv run python -m auvik_mcp          # listens on 0.0.0.0:8080

or with Docker:

docker build --platform linux/amd64 -t auvik-mcp:dev .
docker run --rm -p 8080:8080 auvik-mcp:dev

Configuration (environment variables, all optional): MCP_HTTP_HOST (default 0.0.0.0), MCP_HTTP_PORT (default 8080), LOG_LEVEL (default INFO). Credentials are never read from the environment.

Testing example

# list tools
curl -s http://localhost:8080/mcp \
  -H "Content-Type: application/json" \
  -H "Accept: application/json, text/event-stream" \
  -H "X-Auvik-Username: user@example.com" \
  -H "X-Auvik-Api-Key: YOUR_API_KEY" \
  -H "X-Auvik-Region: us1" \
  -d '{"jsonrpc":"2.0","id":1,"method":"tools/list","params":{}}'

# call a tool
curl -s http://localhost:8080/mcp \
  -H "Content-Type: application/json" \
  -H "Accept: application/json, text/event-stream" \
  -H "X-Auvik-Username: user@example.com" \
  -H "X-Auvik-Api-Key: YOUR_API_KEY" \
  -d '{"jsonrpc":"2.0","id":2,"method":"tools/call","params":{"name":"auvik_devices_list","arguments":{"filter_onlineStatus":"offline","pageSize":10}}}'

Unit tests (no network access needed):

uv run pytest

Delivery notes

Tool count (27). This is above the suggested 20 because the tool names are an existing contract: agents and tenant connections already use them, so none were merged or removed.
Write tools. auvik_alerts_dismiss (one alert by ID) and auvik_raw_request with method=POST change data; both are annotated destructiveHint=true and their descriptions tell the agent to use them only on explicit request. auvik_raw_request only reaches /v1/... paths on the caller's own Auvik API host.
Legacy arguments. Arguments that the Auvik API never honoured (for example a numeric page on list tools; Auvik pagination is cursor-based) are not declared any more. Callers that still send them are not rejected; the values are ignored.

License

Apache License 2.0 - see LICENSE and NOTICE.

This server cannot be deployed

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

Maintenance

ActivityMaintained

ResponsivenessNo issues

Resources

GitHub Repository

Need Help?

Related Servers

Related MCP Connectors

API.market MCP GatewayOAuth
io.github.Noveum
Connect AI agents to 580+ APIs with OAuth or API-key auth. Hosted gateway; API pricing varies.
Agent Orchestration
1
ScrollportOAuth
com.scrollport
Verified, pay-per-use API tools for AI agents through one authenticated connection.
Agent Orchestration Developer Tools
1
QueryBearOAuth
io.github.spencerpauly
Safe, read-only Postgres and MySQL access for AI agents. Audit log + column-level controls.
Databases RAG Systems
2
FullmaktOAuth
ai.fullmakt
Credential broker for AI agents: scoped, revocable API access with policy enforcement and audit.
Security Autonomous Agents Agent Orchestration
1

Related MCP Servers

LogicMonitor MCP Serverofficial
Monitoring Observability
logicmonitor
A
license
Not graded
quality
B
maintenance
Provides secure access to the LogicMonitor API, enabling AI assistants to manage monitoring infrastructure through natural language commands.
Updated 3 months ago (2026-07-27 19:50 UTC)
15 npm
6
Mozilla Public 2.0
Meraki Monitor MCP
Networking & Infrastructure Monitoring
coozgan
A
license
Not graded
quality
D
maintenance
Enables secure, read-only monitoring of Cisco Meraki networks, allowing AI agents to query real-time information on organizations, networks, devices, clients, and traffic without risk of configuration changes.
Updated a year ago (2025-07-23 05:04 UTC)
MIT
Cisco Secure Access MCP Server
Security Monitoring
ACSmith1337
F
license
Not graded
quality
D
maintenance
Enables AI agents to investigate threats, pull reports, manage security policies, and administer deployment infrastructure through the Cisco Secure Access REST API.
Updated 4 months ago (2026-06-23 21:09 UTC)
-
proofpoint-essentials-mcp
Security Monitoring
WYRE-AI
A
license
Not graded
quality
B
maintenance
Enables AI assistants to manage MSP-multi-tenant email security: organizations, domains, users, licensing, features, subscription packages, and email flow reporting.
Updated 2 days ago (2026-10-14 16:08 UTC)
Apache 2.0

Auvik MCP Server

Authentication headers

Tools

Run locally

Testing example

Delivery notes

License

Maintenance

Resources

Related MCP Connectors

Related MCP Servers

LogicMonitor MCP Serverofficial

Meraki Monitor MCP

Cisco Secure Access MCP Server

proofpoint-essentials-mcp