arista-cvp

Arista CloudVision Portal (CVP) Automation

MCP Server

Authentication

CloudVision uses service account tokens passed as HTTP cookies:

1. Log in to CloudVision Portal
2. Navigate to Settings → Service Accounts
3. Create a service account and generate a token
4. 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

---

Tools (4)

Device Inventory (1 tool)

Event Monitoring (1 tool)

Connectivity Monitoring (1 tool)

Tag Management (1 tool)

create_tag Workflow Detail

The create_tag tool follows CloudVision's workspace model — a 5-step process:

1. Create Workspace — POST to /api/resources/workspace/v1/WorkspaceConfig with a UUID-based workspace
2. Create Tag — POST to /api/resources/tag/v2/TagConfig with ELEMENT_TYPE_DEVICE, workspace ID, tag name/value
3. Build Workspace — POST with REQUEST_START_BUILD to validate changes
4. Wait for Build — 10-second wait for build completion
5. Submit Workspace — POST with REQUEST_SUBMIT to apply the tag

---

CloudVision Resource API Endpoints

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

---

CVP MCP vs pyATS MCP vs JunOS MCP

---

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