VISTA Data MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| ES_HOST | No | Elasticsearch hostname (required if using Elasticsearch) | |
| ES_PORT | No | Port for Elasticsearch | 9200 |
| ES_USER | No | Username for Elasticsearch basic auth | |
| ES_SECURE | No | Use HTTPS for Elasticsearch | true |
| ES_MAX_HITS | No | Max hits per Elasticsearch search | 500 |
| ES_PASSWORD | No | Password for Elasticsearch basic auth | |
| CLICKHOUSE_HOST | No | ClickHouse server hostname (required if using ClickHouse) | |
| CLICKHOUSE_PORT | No | HTTP(S) port for ClickHouse | 8443 |
| CLICKHOUSE_USER | No | ClickHouse username | default |
| ES_VERIFY_CERTS | No | Verify SSL certificates for Elasticsearch | true |
| ES_QUERY_TIMEOUT | No | Elasticsearch query timeout in seconds | 30 |
| CLICKHOUSE_SECURE | No | Use HTTPS for ClickHouse | true |
| CLICKHOUSE_DATABASE | No | Default ClickHouse database | default |
| CLICKHOUSE_MAX_ROWS | No | Max rows per ClickHouse query | 500 |
| CLICKHOUSE_PASSWORD | No | ClickHouse password | |
| CLICKHOUSE_QUERY_TIMEOUT | No | ClickHouse query timeout in seconds | 30 |
Capabilities
Features and capabilities supported by this server
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| 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 |
| ch_list_databasesA | List all databases accessible in the ClickHouse instance. |
| ch_list_tablesA | List all tables in a ClickHouse database. Args: database: Database name. If omitted, lists tables in the default database. |
| 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. |
| 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). |
| 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"}}}} |
| es_list_indicesA | List all Elasticsearch indices with document counts and sizes. Use this to discover available download/package data indices. |
| es_get_mappingA | Show the field mapping (schema) for an Elasticsearch index. Args: index: The index name to inspect. |
| 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). |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
Latest Blog Posts
- Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)By Om-Shree-0709 on .mcpAgent IdentityOAuth 2.1
- Your AI Chatbot Just Exposed Your CEO's Salary to an InternBy Om-Shree-0709 on .Agent IdentityMCP SecurityOAuth Delegation
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/Percona-Lab/vista-data-mcp'
If you have feedback or need assistance with the MCP directory API, please join our Discord server