Model Context Protocol

Isvara, in your agent.

Add one URL and any MCP client can ask iO, run the health check on live counters and read the guide.

Add as a custom connector in Claude, or in any MCP client

https://isvara.io/api/mcp

Client without remote servers?

Bridge it locally with mcp-remote:

$npx mcp-remote https://isvara.io/api/mcp

claude_desktop_config.json

{
  "mcpServers": {
    "isvara": {
      "command": "npx",
      "args": ["-y", "mcp-remote", "https://isvara.io/api/mcp"]
    }
  }
}

Four tools.

ask_isvara(question, chapter?)

Ask iO a question. It answers from the guide and links the sections it used.

ops_score(metric, value)

Turn one reading (CPU ready, memory latency, disk latency or dropped packets) into a 0 to 100 score. Plain maths, no model.

health_check(vms, period?, source?)

Give it the four counters for each VM and every cluster is scored, with a link to the full report.

fleet_view(vms, hosts?, clusters?, datastores?)

Give it the estate from VCF Operations and it opens in Fleet Console, every vCenter as if from RVTools, with the checks and contention scored.

Connect VCF Operations.

Add Isvara to your agent with the URL above.

Add a VCF Operations MCP server to the same agent, such as the community VMware-Aria (not a Broadcom product).

Ask it: “Read CPU ready, memory contention, disk latency and transmit dropped packets for every VM over the last 30 days from VCF Operations, take the 99th percentile of each VM's 5-minute values, and run the Isvara health check on them.”

Step-by-step setup

1
Install the VCF Operations connector
On a machine that can reach VCF Operations. It needs uv.
```
uv tool install vmware-aria
```
2
Give it your login
Save this as ~/.vmware-aria/config.yaml, with your VCF Operations address and a read-only user:
```
targets:
  prod:
    host: vcf-ops.example.com
    username: readonly-user
    port: 443
    verify_ssl: true
    auth_source: LOCAL
default_target: prod
```
Put the password in ~/.vmware-aria/.env:
```
VMWARE_ARIA_PROD_PASSWORD=your-password
```
Then run vmware-aria doctor to check it connects.
3
Add both servers to your agent
In Claude Code, run:
```
claude mcp add --transport http isvara https://isvara.io/api/mcp
claude mcp add vmware-aria -- vmware-aria mcp
```
In Claude Desktop, put both in claude_desktop_config.json instead
Restart the agent.

Ask it

Paste this, then open the link it returns to see every cluster scored:

Read CPU ready, memory contention, disk latency and transmit dropped packets for every VM over the last 30 days from VCF Operations, take the 99th percentile of each VM's 5-minute values, and run the Isvara health check on them.

Or, for the whole estate in Fleet Console, every vCenter as if from RVTools:

Read every vCenter, cluster, host, VM and datastore from VCF Operations, with the four counters for each VM (the 99th percentile of its 5-minute values over the last 30 days), and open them in the Isvara fleet view.

No agent? Export the four counters per VM (each one’s 99th percentile over the last month) from a VCF Operations list view as CSV and drop it on the health check.

Your credentials stay with your agent. Isvara only sees the counters and stores nothing.

Three resources.

isvara://indexEvery chapter, with its link.

isvara://thresholdsThe four indicators, their thresholds and how the score works.

isvara://book/{id}A whole book as Markdown: exec-summary, part-1 to part-4.