# Overview

> Query your Visual One Intelligence environment in natural language from any MCP-compatible AI assistant.

The **VisualOne MCP** (server name: `VisualOneMCP`) is a [Model Context Protocol](https://modelcontextprotocol.io) server that exposes the Visual One Intelligence (VOI) reporting engine to AI assistants such as Claude. Ask questions about your infrastructure in plain language — “show me storage capacity trends,” “which clusters are running out of headroom?” — and the assistant discovers the right VOI report, runs it against *your* environment, and returns the data.

Under the hood the MCP is a thin, read-only wrapper over the VOI **Arbiter API**. It does not replace the VOI web application; it makes the same report catalog reachable programmatically through an AI client.

## What you can do with it

- **Discover** which reports exist for a topic and how to run them.
- **Run** any VOI report and get results as clean Markdown tables or raw JSON.
- **Resolve** the exact names of environment entities (storage arrays, vCenters, clusters, ESX hosts, VMs, switches, database instances) needed to drill into detail reports.
- **Inspect** your session, client context, and API health.

## Domains it covers

| Domain | Examples of what you can ask for |
| --- | --- |
| Storage | Capacity plans, free space, disk types, snap/replication, health alerts, trends |
| SAN / Switch | Switch summaries, topology, port connectivity, port-error trends |
| Virtualization | vCenter → cluster → ESX host → datastore → VM drilldowns, cluster capacity plans |
| Database (SQL Server) | Instances, versions, health, missing/unused indexes, query performance, fragmentation |
| Kubernetes | Capacity & trends by business unit, cluster, node, pod, container |
| Cloud | Summaries, cost, growth, budget/spend trends, resource-group modeling |
| FinOps | Year-to-date cost, tag-based cost inventory and trends |
| Backup | Status, runtime, gap analysis, pool/host occupancy, VM audit |
| Rollups | Enterprise, Business Unit, and Data Center summaries |

## What it is not

- It is **read-only**. The MCP retrieves and formats data; it does not create, edit, or delete anything in VOI.
- It is **scoped to your client (tenant)**. Every call runs in the context of the client tied to your session. (Super users can target another client.)
- It is **not a configuration or administration interface**. Onboarding, data collection, user management, and integrations are handled in the VOI application, not through the MCP.

## The five tools at a glance

| Tool | What it does |
| --- | --- |
| `visualone_discover_reports` | Search the report registry to find the right report and how to run it |
| `visualone_get_reports` | Execute a report and return the data |
| `visualone_list_units` | Look up exact entity names for drilldown reports |
| `visualone_get_session` | Show the authenticated user, client ID, and token expiry |
| `visualone_health_check` | Confirm the Arbiter API is reachable |

Continue to [Getting Started](https://visualoneintelligence.com/docs/voi-mcp-getting-started/) to connect, or jump to the [Tool Reference](https://visualoneintelligence.com/docs/voi-mcp-tool-reference/).

---

Source: https://visualoneintelligence.com/docs/voi-mcp-overview/