mcp-hydrolix

<!-- mcp-name: io.github.hydrolix/mcp-hydrolix -->

[](https://pypi.org/project/mcp-hydrolix)

An MCP server for Hydrolix.

• run_select_query
• Execute SQL queries on your Hydrolix cluster.
• Input: sql (string): The SQL query to execute.

• list_databases
• List all databases on your Hydrolix cluster.

• list_tables
• List all tables in a database.
• Input: database (string): The name of the database.

• get_table_info
• Get table metadata such as schema
• Input: database (string): The name of the database.
• Input: table (string): The name of the table.

Due to the wide variety in LLM architectures, not all models will proactively use the tools above, and few will use them effectively without guidance, even with the carefully-constructed tool descriptions provided to the model. To get the best results out of your model while using the Hydrolix MCP server, we recommend the following:

• Refer to your Hydrolix database by name and request tool usage in your prompts (e.g., "Using MCP tools to access my Hydrolix database, please ...")
• This encourages the model to use the MCP tools available and minimizes hallucinations.
• Include time ranges in your prompts (e.g., "Between December 5 2023 and January 18 2024, ...") and specifically request that the output be ordered by timestamp.
• This prompts the model to write more efficient queries that take advantage of primary key optimizations

When running with HTTP or SSE transport, a health check endpoint is available at /health. This endpoint:

• Returns 200 OK with the Hydrolix query-head's Clickhouse version if the server is healthy and can connect to Hydrolix
• Returns 503 Service Unavailable if the server cannot connect to the Hydrolix query-head

Example:

curl http://lo