Arista CloudVision Portal (CVP) Automation
MCP Server
| Field |
Value |
| Repository |
noredistribution/mcp-cvp-fun |
| Transport |
stdio (FastMCP) |
| Python |
3.12+ |
| Protocol |
HTTPS REST → CloudVision Resource API |
| Dependencies |
fastmcp, httpx, python-dotenv |
| Install |
git clone + uv run (dependencies resolved at runtime) |
| Entry Point |
uv run --with fastmcp fastmcp run /path/to/mcp_server_rest.py |
| Status |
Community demo — not officially supported by Arista |
Authentication
CloudVision uses service account tokens passed as HTTP cookies:
- Log in to CloudVision Portal
- Navigate to Settings → Service Accounts
- Create a service account and generate a token
- Store the token in the
.env file as CVPTOKEN
The token is sent as an access_token cookie with every API request (not a Bearer header).
Environment Variables
| Variable |
Required |
Purpose |
CVP |
Yes |
CloudVision instance hostname (e.g., www.arista.io or cvp.example.com) |
CVPTOKEN |
Yes |
Service account token for API authentication |
Tools (4)
Device Inventory (1 tool)
| Tool |
Parameters |
Description |
get_inventory |
— |
Get inventory of all devices from CloudVision (hostname, model, serial, version, MAC, IP, streaming status) |
Event Monitoring (1 tool)
| Tool |
Parameters |
Description |
get_events |
— |
Get all events from CloudVision (alerts, warnings, informational events with severity, timestamps, device associations) |
Connectivity Monitoring (1 tool)
| Tool |
Parameters |
Description |
get_connectivity_monitor |
— |
Get Connectivity Monitor probe statistics (jitter, latency, packet loss, HTTP response time across all probes) |
Tag Management (1 tool)
| Tool |
Parameters |
Description |
create_tag |
tag_name, tag_value |
Create a device-level tag in CloudVision via workspace workflow (create workspace → create tag → build → submit) |
create_tag Workflow Detail
The create_tag tool follows CloudVision's workspace model — a 5-step process:
- Create Workspace — POST to
/api/resources/workspace/v1/WorkspaceConfig with a UUID-based workspace
- Create Tag — POST to
/api/resources/tag/v2/TagConfig with ELEMENT_TYPE_DEVICE, workspace ID, tag name/value
- Build Workspace — POST with
REQUEST_START_BUILD to validate changes
- Wait for Build — 10-second wait for build completion
- Submit Workspace — POST with
REQUEST_SUBMIT to apply the tag
CloudVision Resource API Endpoints
| Method |
Endpoint |
Tool |
| GET |
/api/resources/inventory/v1/Device/all |
get_inventory |
| GET |
/api/resources/event/v1/Event/all |
get_events |
| GET |
/api/resources/connectivitymonitor/v1/ProbeStats/all |
get_connectivity_monitor |
| POST |
/api/resources/workspace/v1/WorkspaceConfig |
create_tag (workspace create/build/submit) |
| POST |
/api/resources/tag/v2/TagConfig |
create_tag (tag creation) |
Responses use newline-delimited JSON (NDJSON) format, consistent with CloudVision's streaming resource API.
Workflows
1. Arista Device Discovery
get_inventory → list all Arista devices (hostname, model, serial, version, MAC, IP)
→ Cross-reference with NetBox/Nautobot → flag discrepancies
→ GAIT
2. Arista Event Monitoring
get_events → retrieve all CloudVision events
→ Filter by severity (critical, warning, info)
→ Correlate events with device inventory
→ Severity-sort findings → GAIT
3. Arista Network Health Check
get_inventory → identify all managed devices
→ get_events → check for active alarms and warnings
→ get_connectivity_monitor → analyze jitter, latency, packet loss
→ Correlate connectivity issues with events → severity-sort → GAIT
4. Arista Device Tagging
ServiceNow CR must be in Implement state
→ get_inventory → verify target devices exist
→ create_tag(tag_name, tag_value) → apply device-level tag via workspace workflow
→ get_inventory → verify tag applied
→ GAIT
5. Arista Connectivity Baseline
get_connectivity_monitor → capture current probe statistics
→ Record jitter, latency, packet loss baselines per probe
→ Compare against thresholds → flag degradation
→ GAIT
Integration with Other Skills
| Skill |
Integration |
| pyats-network |
CVP MCP for Arista fleet visibility, pyATS MCP for Cisco devices — unified multi-vendor monitoring |
| junos-network |
CVP MCP for Arista, JunOS MCP for Juniper — multi-vendor device inventory and health |
| netbox-reconcile |
Cross-reference CVP device inventory (model, serial, version) against NetBox source of truth |
| nautobot-sot |
Same as NetBox — validate Arista device IPAM data in Nautobot |
| infrahub-sot |
Cross-reference Infrahub node data with Arista device inventory from CVP |
| servicenow-change-workflow |
Gate all create_tag operations behind ServiceNow Change Requests |
| gait-session-tracking |
Every CVP inventory query, event pull, and tag creation logged in GAIT |
| te-network-monitoring |
Correlate ThousandEyes path data with CVP connectivity monitor probes |
| nvd-cve |
Scan EOS versions from get_inventory against NVD vulnerability database |
| markmap-viz |
Generate topology mind maps from CVP device inventory data |
CVP MCP vs pyATS MCP vs JunOS MCP
| Capability |
CVP MCP |
pyATS MCP |
JunOS MCP |
| Vendor |
Arista (via CVP) |
Cisco (IOS-XE, NX-OS, IOS-XR) |
Juniper |
| Protocol |
HTTPS REST → CVP Resource API |
SSH + Genie parsers |
NETCONF → PyEZ |
| Device Inventory |
get_inventory (fleet-wide) |
pyats_learn("platform") per device |
gather_device_facts per device |
| Event Monitoring |
get_events (fleet-wide) |
Per-device show commands |
Per-device show commands |
| Connectivity Metrics |
get_connectivity_monitor (probes) |
Per-device show commands |
Per-device show commands |
| Config Push |
Via CVP Change Control (not in MCP) |
pyats_configure_device |
load_and_commit_config |
| Tag/Label Mgmt |
create_tag (workspace workflow) |
N/A |
N/A |
| Batch Operations |
All tools are fleet-wide by default |
pyats_pcall (parallel pCall) |
execute_junos_command_batch |
| MCP Tools |
4 |
8 |
10 |
Guardrails
- Always call
get_inventory first — verify CloudVision is reachable and devices are streaming before deeper queries
- Check events before changes — call
get_events to identify active issues before any tag operations
- Gate tag creation — all
create_tag calls must have a ServiceNow CR in Implement state
- Validate tag names — ensure tag names follow organizational naming conventions before creation
- Monitor connectivity baselines — use
get_connectivity_monitor to establish baselines before and after network changes
- Cross-reference inventory — compare CVP device data with NetBox/Nautobot to detect SoT drift
- Record in GAIT — every inventory query, event pull, connectivity check, and tag creation must be logged
- Community project — this is an unofficial demo; evaluate security implications (TLS verification disabled in source) before production use
1---2name: arista-cvp3description: Arista CloudVision Portal (CVP) automation via REST API — device inventory, events, connectivity monitoring, tag management (4 tools). Use when managing Arista devices, checking CloudVision events, monitoring network connectivity probes, or tagging devices in CVP.4license: Apache-2.05---6
7# Arista CloudVision Portal (CVP) Automation
8
9## MCP Server
10
11| Field | Value |
12|-------|-------|
13| **Repository** | [noredistribution/mcp-cvp-fun](https://github.com/noredistribution/mcp-cvp-fun) |
14| **Transport** | stdio (FastMCP) |
15| **Python** | 3.12+ |
16| **Protocol** | HTTPS REST → CloudVision Resource API |
17| **Dependencies** | `fastmcp`, `httpx`, `python-dotenv` |
18| **Install** | `git clone` + `uv run` (dependencies resolved at runtime) |
19| **Entry Point** | `uv run --with fastmcp fastmcp run /path/to/mcp_server_rest.py` |
20| **Status** | Community demo — not officially supported by Arista |
21
22## Authentication
23
24CloudVision uses service account tokens passed as HTTP cookies:
25
261. Log in to CloudVision Portal
272. Navigate to **Settings → Service Accounts**
283. Create a service account and generate a token
294. Store the token in the `.env` file as `CVPTOKEN`
30
31The token is sent as an `access_token` cookie with every API request (not a Bearer header).
32
33## Environment Variables
34
35| Variable | Required | Purpose |
36|----------|----------|---------|
37| `CVP` | Yes | CloudVision instance hostname (e.g., `www.arista.io` or `cvp.example.com`) |
38| `CVPTOKEN` | Yes | Service account token for API authentication |
39
40---
41
42## Tools (4)
43
44### Device Inventory (1 tool)
45
46| Tool | Parameters | Description |
47|------|-----------|-------------|
48| `get_inventory` | — | Get inventory of all devices from CloudVision (hostname, model, serial, version, MAC, IP, streaming status) |
49
50### Event Monitoring (1 tool)
51
52| Tool | Parameters | Description |
53|------|-----------|-------------|
54| `get_events` | — | Get all events from CloudVision (alerts, warnings, informational events with severity, timestamps, device associations) |
55
56### Connectivity Monitoring (1 tool)
57
58| Tool | Parameters | Description |
59|------|-----------|-------------|
60| `get_connectivity_monitor` | — | Get Connectivity Monitor probe statistics (jitter, latency, packet loss, HTTP response time across all probes) |
61
62### Tag Management (1 tool)
63
64| Tool | Parameters | Description |
65|------|-----------|-------------|
66| `create_tag` | `tag_name`, `tag_value` | Create a device-level tag in CloudVision via workspace workflow (create workspace → create tag → build → submit) |
67
68### `create_tag` Workflow Detail
69
70The `create_tag` tool follows CloudVision's workspace model — a 5-step process:
71
721. **Create Workspace** — POST to `/api/resources/workspace/v1/WorkspaceConfig` with a UUID-based workspace
732. **Create Tag** — POST to `/api/resources/tag/v2/TagConfig` with `ELEMENT_TYPE_DEVICE`, workspace ID, tag name/value
743. **Build Workspace** — POST with `REQUEST_START_BUILD` to validate changes
754. **Wait for Build** — 10-second wait for build completion
765. **Submit Workspace** — POST with `REQUEST_SUBMIT` to apply the tag
77
78---
79
80## CloudVision Resource API Endpoints
81
82| Method | Endpoint | Tool |
83|--------|----------|------|
84| GET | `/api/resources/inventory/v1/Device/all` | `get_inventory` |
85| GET | `/api/resources/event/v1/Event/all` | `get_events` |
86| GET | `/api/resources/connectivitymonitor/v1/ProbeStats/all` | `get_connectivity_monitor` |
87| POST | `/api/resources/workspace/v1/WorkspaceConfig` | `create_tag` (workspace create/build/submit) |
88| POST | `/api/resources/tag/v2/TagConfig` | `create_tag` (tag creation) |
89
90Responses use newline-delimited JSON (NDJSON) format, consistent with CloudVision's streaming resource API.
91
92---
93
94## Workflows
95
96### 1. Arista Device Discovery
97```
98get_inventory → list all Arista devices (hostname, model, serial, version, MAC, IP)
99→ Cross-reference with NetBox/Nautobot → flag discrepancies
100→ GAIT
101```
102
103### 2. Arista Event Monitoring
104```
105get_events → retrieve all CloudVision events
106→ Filter by severity (critical, warning, info)
107→ Correlate events with device inventory
108→ Severity-sort findings → GAIT
109```
110
111### 3. Arista Network Health Check
112```
113get_inventory → identify all managed devices
114→ get_events → check for active alarms and warnings
115→ get_connectivity_monitor → analyze jitter, latency, packet loss
116→ Correlate connectivity issues with events → severity-sort → GAIT
117```
118
119### 4. Arista Device Tagging
120```
121ServiceNow CR must be in Implement state
122→ get_inventory → verify target devices exist
123→ create_tag(tag_name, tag_value) → apply device-level tag via workspace workflow
124→ get_inventory → verify tag applied
125→ GAIT
126```
127
128### 5. Arista Connectivity Baseline
129```
130get_connectivity_monitor → capture current probe statistics
131→ Record jitter, latency, packet loss baselines per probe
132→ Compare against thresholds → flag degradation
133→ GAIT
134```
135
136---
137
138## Integration with Other Skills
139
140| Skill | Integration |
141|-------|-------------|
142| **pyats-network** | CVP MCP for Arista fleet visibility, pyATS MCP for Cisco devices — unified multi-vendor monitoring |
143| **junos-network** | CVP MCP for Arista, JunOS MCP for Juniper — multi-vendor device inventory and health |
144| **netbox-reconcile** | Cross-reference CVP device inventory (model, serial, version) against NetBox source of truth |
145| **nautobot-sot** | Same as NetBox — validate Arista device IPAM data in Nautobot |
146| **infrahub-sot** | Cross-reference Infrahub node data with Arista device inventory from CVP |
147| **servicenow-change-workflow** | Gate all `create_tag` operations behind ServiceNow Change Requests |
148| **gait-session-tracking** | Every CVP inventory query, event pull, and tag creation logged in GAIT |
149| **te-network-monitoring** | Correlate ThousandEyes path data with CVP connectivity monitor probes |
150| **nvd-cve** | Scan EOS versions from `get_inventory` against NVD vulnerability database |
151| **markmap-viz** | Generate topology mind maps from CVP device inventory data |
152
153---
154
155## CVP MCP vs pyATS MCP vs JunOS MCP
156
157| Capability | CVP MCP | pyATS MCP | JunOS MCP |
158|-----------|---------|-----------|-----------|
159| **Vendor** | Arista (via CVP) | Cisco (IOS-XE, NX-OS, IOS-XR) | Juniper |
160| **Protocol** | HTTPS REST → CVP Resource API | SSH + Genie parsers | NETCONF → PyEZ |
161| **Device Inventory** | `get_inventory` (fleet-wide) | `pyats_learn("platform")` per device | `gather_device_facts` per device |
162| **Event Monitoring** | `get_events` (fleet-wide) | Per-device show commands | Per-device show commands |
163| **Connectivity Metrics** | `get_connectivity_monitor` (probes) | Per-device show commands | Per-device show commands |
164| **Config Push** | Via CVP Change Control (not in MCP) | `pyats_configure_device` | `load_and_commit_config` |
165| **Tag/Label Mgmt** | `create_tag` (workspace workflow) | N/A | N/A |
166| **Batch Operations** | All tools are fleet-wide by default | `pyats_pcall` (parallel pCall) | `execute_junos_command_batch` |
167| **MCP Tools** | 4 | 8 | 10 |
168
169---
170
171## Guardrails
172
173- **Always call `get_inventory` first** — verify CloudVision is reachable and devices are streaming before deeper queries
174- **Check events before changes** — call `get_events` to identify active issues before any tag operations
175- **Gate tag creation** — all `create_tag` calls must have a ServiceNow CR in `Implement` state
176- **Validate tag names** — ensure tag names follow organizational naming conventions before creation
177- **Monitor connectivity baselines** — use `get_connectivity_monitor` to establish baselines before and after network changes
178- **Cross-reference inventory** — compare CVP device data with NetBox/Nautobot to detect SoT drift
179- **Record in GAIT** — every inventory query, event pull, connectivity check, and tag creation must be logged
180- **Community project** — this is an unofficial demo; evaluate security implications (TLS verification disabled in source) before production use
automateyournetwork