Zetaris MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| ZETARIS_ORG_ID | Yes | Numeric organisation ID | |
| ZETARIS_API_KEY | No | API key used to sign in (alternative to ZETARIS_USERNAME and ZETARIS_PASSWORD) | |
| ZETARIS_CATALOG | No | JSON file describing ready-made views, shown by list_tables | |
| ZETARIS_MCP_LOG | No | Where tool calls are logged | |
| ZETARIS_TIMEOUT | No | Seconds each call may take before the agent is told to make the query lighter | 50 |
| ZETARIS_BASE_URL | No | Your Zetaris UI address | http://localhost:3000 |
| ZETARIS_COOLDOWN | No | Longest wait, in seconds, before a query that ran past the time limit is assumed finished | 180 |
| ZETARIS_ENV_FILE | No | File to read these environment variables from (the bundled .cursor/mcp.json uses .env.local) | |
| ZETARIS_MAX_ROWS | No | Most rows returned per query | 200 |
| ZETARIS_PASSWORD | No | Password used to sign in (requires ZETARIS_USERNAME; alternative to ZETARIS_API_KEY) | |
| ZETARIS_SPARK_UI | No | Spark status address (for example http://127.0.0.1:4040); turns on the busy check | |
| ZETARIS_USERNAME | No | Username used to sign in (requires ZETARIS_PASSWORD; alternative to ZETARIS_API_KEY) |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_databasesA | List the databases registered in Zetaris. Start here to see what data is already available. |
| list_tablesC | List the tables in one Zetaris database. |
| describe_tableB | Show the columns and types of a Zetaris table, given as DATABASE.table. |
| run_queryA | Run a read-only SQL query in Zetaris (SELECT, WITH, SHOW, DESCRIBE, EXPLAIN). Zetaris SQL is Spark SQL; tables are DATABASE.table and one query can join tables from different sources. Returns up to 200 rows, the time taken and the exact SQL run. |
| register_sourceB | Register a new data source in Zetaris with a CREATE LIGHTNING ... statement (REST, FILESTORE or DATABASE), or cache a table with CACHE TABLE. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 5 tools
The tools mostly target distinct operations: listing databases, listing tables, describing a table, querying, and registering a source. There is some overlap between describe_table and run_query because run_query also accepts DESCRIBE, but the descriptions make the intended use cases reasonably clear.
All tool names use a consistent snake_case verb_noun pattern: list_databases, list_tables, describe_table, run_query, register_source. The convention is predictable and easy to infer.
Five tools is well-scoped for a Zetaris data exploration and query server. Each tool covers a distinct step in the discovery-to-query workflow, with no obviously redundant tools.
The server covers the core lifecycle of discovering databases, inspecting tables, querying data, and registering sources. Minor gaps remain around removing or updating registered sources and inspecting source metadata, but agents can handle most core workflows.