imply-druid-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| LOG_LEVEL | No | Logging level | INFO |
| IMPLY_REGION | Yes | Region (e.g., us-east-1) | |
| IMPLY_API_KEY | No | Imply API key | |
| IMPLY_PROJECT_ID | Yes | Imply project ID | |
| MAX_QUERY_LENGTH | No | Maximum SQL query length | 10000 |
| IMPLY_ACCESS_TOKEN | No | OAuth access token (alternative) | |
| IMPLY_ORGANIZATION | Yes | Imply Cloud organization name | |
| IMPLY_CLOUD_PROVIDER | Yes | Cloud provider: aws, gcp, or azure | |
| DEFAULT_QUERY_TIMEOUT_MS | No | Default query timeout (ms) | 30000 |
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 | {
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| execute_sql_queryA | Execute a SQL query against Druid and return results. Use this for synchronous queries on small datasets. |
| execute_async_queryA | Execute an asynchronous SQL query for large datasets or long-running queries. Returns a query ID. |
| get_query_resultsB | Get results from an asynchronous query using its query ID. |
| get_query_statusC | Check the status of an asynchronous query. |
| cancel_queryB | Cancel a running query. |
| list_tablesA | List all tables in the Druid project with their metadata. |
| get_table_schemaC | Get detailed schema information for a specific table. |
| list_dashboardsA | List all dashboards in the Imply project with their metadata. |
| get_dashboardB | Get detailed information about a specific dashboard including its configuration. |
| list_data_cubesA | List all data cubes in the Imply project with their metadata. |
| get_data_cubeA | Get detailed information about a specific data cube including dimensions and measures. |
| query_data_cubeA | Execute SQL query against a data cube (Pivot). Use 'source' from list_data_cubes. Syntax: FROM "datacube"."SOURCE", "DIM:dimension_name", MEASURE_BY_ID('measure_id') |
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 12 tools
Each tool has a clear, distinct purpose. Sync and async queries are separated, and the data cube query uses a different syntax. No two tools appear to do the same thing.
All tool names follow a consistent verb_noun pattern (e.g., list_*, get_*, execute_*, cancel_*, query_*). No mixing of conventions or vague verbs.
12 tools appropriately cover the core functionalities of querying Druid, managing dashboards, data cubes, and tables. Not too few nor too many.
The tool set provides full lifecycle coverage for querying (sync, async, cancellation, status, results) and browsing resources (list, get details, schema). No obvious gaps for a query-oriented server.