v1.2.8 — PXC supporting panel on MySQL Cascade KPI

Features

• MySQL Cascade KPI report now includes a PXC supporting signal panel beneath the PS anchor:
  • Two KPI tiles: active instances and active clusters (trailing 12 months)
  • Monthly active instances trend line
  • Top 10 version distribution (8.0.x orange, 8.4.x green)
  • No status badge — PXC is trend-tracking only, not a Cascade target
• PS anchor section is unchanged. Scope excludes PXB, ProxySQL, and the 8.0 EOL split (already in the PS panel).

Verified values (2026-04-16)

• PXC active instances (T12M): 6,740
• PXC active clusters (T12M): 2,954

v1.2.7 — SN MCP prototype

New

• SN MCP prototype — new optional prototype-SN.mcpb install that gives VISTA read-only access to Percona's SN test instance. Download the .mcpb and open it; you'll be prompted once for your SN username and password (stored in the OS keychain).
• SKILL.md now tells the user how to install it when a support/SLA query is attempted without the tools.

Prototype caveats

• Hostname is hardcoded — no way to point it at a different SN instance.
• Tool surface is minimal: sn_query_table, sn_get_record, sn_list_common_tables.
• Basic auth by default; OAuth 2.0 password grant engages if you fill in the optional OAuth client ID / secret fields.

Assets

• vista-plugin.zip — the VISTA plugin for manual install (Cowork / Claude Code).
• prototype-SN.mcpb — the ServiceNow MCP bundle (Cowork / Claude Desktop).
• vista-data.mcpb is unchanged since v1.2.6 — re-download from that release if you haven't already.

v1.2.6 — Install docs polish

Docs

• Marketplace install is now the primary path for the VISTA plugin (Percona-Lab/claude-plugins). Manual zip upload is listed as a fallback.
• Tightened the data MCP step: "(VPN required)" is now right in the heading, and removed the extra paragraph about VPN behavior.

v1.2.5 — Install docs clarity

Docs

Reframes the install flow so it's clear which pieces are required and which are optional:

1. Required — enable your Atlassian, Notion, and Slack workspace connectors first.
2. Required — install the VISTA plugin (vista-plugin.zip).
3. Optional — install the data MCP (vista-data.mcpb) only if you want telemetry or download reports. Jira, Notion, and Slack reports work without it.

Also clarifies that Percona VPN is only needed when you run a telemetry/download query — not for installation, and not for any non-telemetry report.

v1.2.4 — Connector requirements documented

Docs

• Install instructions now clearly state that VISTA depends on your workspace connectors:
  • Atlassian (Jira) — required for engineering reports
  • Notion — required for the data catalog, Jira sync fallback, and weekly status highlights
  • Slack — required for highlights, signals, and team sentiment
  • Google Drive — optional, for linked docs
  • percona-dk — optional, for verifying feature/component names
• Notion install page updated with a prominent pre-install connector checklist.

Install

• Plugin (skill + report logic) — download vista-plugin.zip, then in Cowork: Plugins > Personal > + > Upload plugin
• Data MCP (ClickHouse + Elasticsearch access) — download vista-data.mcpb and open it. Works in both Cowork and Claude Desktop.
• Before running any report, enable the Atlassian, Notion, and Slack connectors in your workspace.

v1.2.3 — percona-dk missing warning

Fixes

• VISTA now warns at the top of any report that filters on a named feature/component/extension if the percona-dk MCP is not installed. Without percona-dk, component URNs (like component_js_lang) can't be verified against Percona docs — only against live DISTINCT queries.
• Matching callout added to the "Filtering on active_components" section in the data dictionary.

Install

• Plugin (skill + report logic) — download vista-plugin.zip, then in Cowork: Plugins > Personal > + > Upload plugin
• Data MCP (ClickHouse + Elasticsearch access) — download vista-data.mcpb and open it. Works in both Cowork and Claude Desktop.

v1.2.2 — Component-name verification rule

Fixes

• Data dictionary now includes a verification rule for active_components metric filtering. Component URNs (e.g., component_js_lang) don't follow a predictable naming pattern and must be confirmed via percona-dk docs lookup or a DISTINCT live query before use.
• New query template for component-level feature activation with JS stored programs as a worked example.
• New "Component-level feature activation" row in the North Star Metrics table.

Install

Download vista-plugin.zip, then in Cowork: Plugins > Personal > + > Upload plugin.

VISTA v1.2.1 — Cascade KPI Tracker & Dark Theme

What's new

• Cascade KPI Tracker (Layout C) — new rigid dashboard layout for tracking KPIs against targets with on-track/off-track status banner, progress bar, pace calculation, and trend chart with target line
• Dark theme — all chart templates now use mandatory dark theme (bg-gray-950)
• MySQL KPI reference — pre-built queries, GSM framework, baseline/target definitions

Install

Download vista-plugin.zip and extract into your Claude Desktop plugins directory, or install from the marketplace (Percona-Lab/claude-plugins).

VISTA v1.2.0 — Zero-Setup Data Connection

What's New in v1.2.0

Live Product Telemetry & Download Analytics

• Query ClickHouse (active instances, version distribution, deployments) and Elasticsearch (package downloads by product, OS, version) directly from VISTA
• Comprehensive data dictionary with pre-built query templates
• Complete product taxonomy mapping all Percona products across ES, CH, and Jira

Data Connection Setup

• Install the vista-data MCP for telemetry and download queries — takes 30 seconds:

  curl -fsSL https://raw.githubusercontent.com/Percona-Lab/vista-data-mcp/main/install-vista-data-mcp | bash
  

• Connect to Percona VPN when querying. No credentials needed in remote mode.
• Local mode supported for users with their own CH/ES credentials.

Dark Theme & Visual Consistency

• All report templates now use the mandatory dark theme (dark backgrounds, light text)
• Consistent visual style across engineering, telemetry, and download reports

Team Mapping & Product Updates

• Updated Jira project key mappings
• Archived MYR project
• Marked discontinued products (Everest, Pro-builds) with dedicated historical query section

Smart Tool Detection

• VISTA checks for data tools before planning queries — no wasted tokens
• Shows install command inline if vista-data MCP is missing

Error Handling

• Friendly VPN-required messages when off network
• Clear error messages for auth and connection issues

VISTA v1.1.0 — Product Telemetry & Downloads

What's New in v1.1.0

Live Product Telemetry & Download Analytics

• Query ClickHouse (active instances, version distribution, deployments) and Elasticsearch (package downloads by product, OS, version, geography) directly from VISTA
• Works on VPN — any Perconian on VPN can query telemetry and download data. VISTA auto-configures the connection on first use
• Local mode also supported for users with their own CH/ES credentials — see vista-data-mcp

Data Dictionary

• Comprehensive data dictionary with pre-built query templates — VISTA queries data directly without schema discovery overhead
• Complete product taxonomy mapping all Percona products across ES, CH, and Jira

Team Mapping & Product Updates

• Updated Jira project key mappings
• Archived MYR project
• Marked discontinued products (Everest, Pro-builds) with dedicated historical query section

Error Handling

• Clear error messages when VPN is disconnected or credentials are invalid
• VISTA offers to set up the data connection automatically if missing