Skip to main content
Glama
VISTA Data MCP Server

VISTA Data MCP Server

by Percona-Lab

VISTA Data MCP Server

Read-only MCP server for querying ClickHouse (product telemetry) and Elasticsearch (download analytics). Built for Percona VISTA.

Install

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

The installer will:

  1. Install uv if needed

  2. Ask you to choose Remote (default) or Local mode

  3. Configure Claude Desktop and Claude Code automatically

  4. Install the VISTA plugin

Remote mode — connects to the shared Percona server over VPN. No credentials, no clone, no local install. Most users choose this.

Local mode — for users with their own ClickHouse or Elasticsearch credentials who want to run off-VPN (development, custom data sources).

Re-run the same command to update or change mode.


Related MCP server: db-connect-mcp

Tools

ClickHouse (telemetry)

Tool

Description

query_clickhouse

Run any read-only SQL (SELECT, SHOW, DESCRIBE, EXPLAIN)

ch_list_databases

Show all accessible databases

ch_list_tables

Show tables in a database

ch_describe_table

Show column names, types, and comments

ch_sample_data

Get sample rows from a table

Elasticsearch (downloads)

Tool

Description

search_elasticsearch

Run an Elasticsearch query (JSON DSL)

es_list_indices

Show all indices with doc counts and sizes

es_get_mapping

Show field mapping (schema) for an index

es_sample_data

Get sample documents from an index

All results are returned as Markdown tables. Only read-only queries are allowed.


Manual Install (alternative)

If you prefer not to use the installer:

Claude Code (CLI)

claude mcp add vista-data \
  -e CLICKHOUSE_HOST=your-ch-host \
  -e CLICKHOUSE_PORT=8443 \
  -e CLICKHOUSE_USER=default \
  -e CLICKHOUSE_PASSWORD=your-ch-password \
  -e CLICKHOUSE_DATABASE=default \
  -e CLICKHOUSE_SECURE=true \
  -e ES_HOST=your-es-host \
  -e ES_PORT=9200 \
  -e ES_USER=your-es-user \
  -e ES_PASSWORD=your-es-password \
  -e ES_SECURE=true \
  -- uvx --from git+https://github.com/Percona-Lab/vista-data-mcp vista-data-mcp

Development

git clone https://github.com/Percona-Lab/vista-data-mcp.git
cd vista-data-mcp
cp .env.example .env
# Edit .env with your credentials
uv run mcp_server.py

Safety

  • Read-only: ClickHouse allows only SELECT, SHOW, DESCRIBE, EXPLAIN. Elasticsearch uses search API only (no indexing).

  • Mutation blocking: INSERT, UPDATE, DELETE, DROP, ALTER, CREATE, TRUNCATE are rejected

  • Row/hit limits: Results capped at 500 (configurable via CLICKHOUSE_MAX_ROWS / ES_MAX_HITS)

  • Query timeout: 30 seconds default (configurable via CLICKHOUSE_QUERY_TIMEOUT / ES_QUERY_TIMEOUT)

  • Identifier sanitization: Database and table names validated against injection

Environment Variables

ClickHouse

Variable

Required

Default

Description

CLICKHOUSE_HOST

Yes*

—

ClickHouse server hostname

CLICKHOUSE_PORT

No

8443

HTTP(S) port

CLICKHOUSE_USER

No

default

Username

CLICKHOUSE_PASSWORD

No

""

Password

CLICKHOUSE_DATABASE

No

default

Default database

CLICKHOUSE_SECURE

No

true

Use HTTPS

CLICKHOUSE_QUERY_TIMEOUT

No

30

Timeout in seconds

CLICKHOUSE_MAX_ROWS

No

500

Max rows per query

Elasticsearch

Variable

Required

Default

Description

ES_HOST

Yes*

—

Elasticsearch hostname

ES_PORT

No

9200

Port

ES_USER

No

""

Username (for basic auth)

ES_PASSWORD

No

""

Password

ES_SECURE

No

true

Use HTTPS

ES_VERIFY_CERTS

No

true

Verify SSL certificates

ES_QUERY_TIMEOUT

No

30

Timeout in seconds

ES_MAX_HITS

No

500

Max hits per search

*Only required if you want to use that data source. Tools for unconfigured sources return a helpful message.


Part of the Alpine Toolkit

Built with CAIRN for VISTA.

License

Apache 2.0

Available Tools

9 tools
ch_describe_tableA

Show the schema (columns, types, comments) of a ClickHouse table.

Args: table: Table name. database: Database name. If omitted, uses the default database.

Inputs: table (required), database. Returns: result

ch_list_databasesA

List all databases accessible in the ClickHouse instance.

Inputs: no named parameters. Returns: result

ch_list_tablesA

List all tables in a ClickHouse database.

Args: database: Database name. If omitted, lists tables in the default database.

Inputs: database. Returns: result

ch_sample_dataA

Get sample rows from a ClickHouse table (up to 100 rows).

Useful for understanding telemetry data structure before writing queries.

Args: table: Table name. database: Database name. If omitted, uses the default database. limit: Number of rows to return (1-100, default 10).

Inputs: table (required), limit, database. Returns: result

es_get_mappingA

Show the field mapping (schema) for an Elasticsearch index.

Args: index: The index name to inspect.

Inputs: index (required). Returns: result

es_list_indicesA

List all Elasticsearch indices with document counts and sizes.

Use this to discover available download/package data indices.

Inputs: no named parameters. Returns: result

es_sample_dataA

Get sample documents from an Elasticsearch index (up to 100).

Useful for understanding download data structure before writing queries.

Args: index: The index name. size: Number of documents to return (1-100, default 10).

Inputs: index (required), size. Returns: result

query_clickhouseA

Run a read-only SQL query against ClickHouse (telemetry data).

Only SELECT, SHOW, DESCRIBE, and EXPLAIN statements are allowed. Results are capped at 500 rows by default.

Use this for product telemetry: active instances, version distribution, storage engines, deployment types, CPU architecture, cluster metrics.

Args: sql: A read-only SQL statement.

Examples: - SELECT count() FROM telemetry WHERE product = 'MySQL' - SELECT version, count() as n FROM telemetry GROUP BY version ORDER BY n DESC - SHOW TABLES

Inputs: sql (required). Returns: result

search_elasticsearchA

Run an Elasticsearch query (JSON DSL) against download/package data.

Use this for product download data: downloads by product, package type, OS, components, growth rates, EOL packages, Pro-builds.

Args: index: The Elasticsearch index to search. query_body: A JSON string containing the Elasticsearch query DSL. Supports match, term, range, bool, aggregations, etc. size: Max documents to return (default 500).

Examples: - {"query": {"match": {"product": "postgresql"}}, "size": 20} - {"size": 0, "aggs": {"by_package": {"terms": {"field": "package_type"}}}} - {"query": {"range": {"date": {"gte": "2025-01-01"}}}}

Inputs: index (required), query_body (required), size. Returns: result

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    TDQS

    A4.2/5.0

    Scored across 9 tools

    Disambiguation5/5

    Each tool is clearly scoped to either ClickHouse or Elasticsearch via distinct prefixes (ch_/es_) and a distinct action (list, describe, sample, query). Within each backend, there is no overlap between listing resources, inspecting schema, sampling data, and executing queries.

    Naming Consistency4/5

    The ch_ and es_ prefixes provide a consistent pattern for most tools, but the generic query tools (query_clickhouse, search_elasticsearch) break the pattern by placing the verb first and omitting the prefix. Additionally, 'describe' vs 'get' are used inconsistently across backends, but the overall system remains readable.

    Tool Count5/5

    Nine tools is a well-scoped set for a dual-backend data exploration server. Each tool serves a distinct purpose, covering discovery, schema inspection, sampling, and querying for both ClickHouse and Elasticsearch without excess.

    Completeness5/5

    The server provides a complete read-only workflow for both data sources: listing available resources (databases/indices/tables), inspecting schemas/mappings, previewing data, and running arbitrary queries. No critical operations are missing for its stated purpose.

    Related MCP Connectors

    Related MCP Servers

    • A
      license
      B
      quality
      D
      maintenance
      A read-only MCP server for OpenObserve Community Edition that works over the REST API. Provides tools for searching logs, traces, stream schemas, and dashboards - no Enterprise license required.
      8
      73 PyPI
      16
      GPL 3.0
    • A
      license
      A
      quality
      B
      maintenance
      A read-only MCP server for exploratory data analysis across PostgreSQL, MySQL, and ClickHouse databases, providing safe, read-only access with comprehensive analysis capabilities.
      10
      84 PyPI
      6
      MIT
    • A
      license
      Not graded
      quality
      C
      maintenance
      A read-only MCP server for querying telemetry data from configurable backends. Provides tools to list sources, describe schemas, run bounded queries, and compute aggregates.
      MIT