Loading...

The Hydrolix MCP server enables LLMs to query and manage Hydrolix data through SQL, with authentication via tokens or credentials.
Boost this tool
Subscribe to listing upgrades or segmented pushes.
The Hydrolix MCP server enables LLMs to query and manage Hydrolix data through SQL, with authentication via tokens or credentials.
The Hydrolix MCP server offers a balance of functionality and security. Using a read-only service account token and keeping SSL verification enabled minimizes risks. However, the ability to execute arbitrary SQL queries means that a compromised service account could still be used to access sensitive data.
Performance depends on the complexity of the SQL queries and the size of the data. Optimize queries for best results.
Cost is primarily related to Hydrolix resource consumption based on query complexity and data volume.
{
"command": "uv",
"args": [
"run",
"--with",
"mcp-hydrolix",
"--python",
"3.13",
"mcp-hydrolix"
],
"env": {
"HYDROLIX_HOST": "<hydrolix-host>",
"HYDROLIX_USER": "<hydrolix-user>",
"HYDROLIX_PASSWORD": "<hydrolix-password>"
}
}HYDROLIX_HOSTHYDROLIX_USERHYDROLIX_PASSWORDrun_select_queryExecutes a SQL query against the Hydrolix database.
Allows execution of arbitrary SQL, potentially leading to data modification or leakage.
list_databasesLists all databases available on the Hydrolix cluster.
Read-only operation that does not modify data.
list_tablesLists all tables within a specified database.
Read-only operation that does not modify data.
get_table_infoRetrieves metadata, such as schema, for a specified table.
Read-only operation that does not modify data.
Token|Environment Variable
hybrid
The Hydrolix MCP server offers a balance of functionality and security. Using a read-only service account token and keeping SSL verification enabled minimizes risks. However, the ability to execute arbitrary SQL queries means that a compromised service account could still be used to access sensitive data.
Autonomy is limited by the permissions of the Hydrolix user or service account. Exercise caution when granting full access.
Production Tip
Use a dedicated service account with read-only permissions for production environments.
Service account token or username/password via environment variables, or per-request token via HTTP/SSE.
Set the `HYDROLIX_DATABASE` environment variable.
Yes, `HYDROLIX_VERIFY` defaults to `true`.
Yes, by setting `HYDROLIX_MCP_SERVER_TRANSPORT` to `http` or `sse` and configuring the bind host and port.
When using HTTP or SSE transport, the health check endpoint is available at `/health`.
Via the `HYDROLIX_TOKEN` environment variable, or the `Authorization` header or `token` query parameter when using HTTP/SSE.
A read-only role is recommended for most use cases.