Hydrolix MCP Server

Hydrolix time-series datalake integration providing schema exploration and query capabilities to LLM-based workflows.

Local serverstdioPython

What is the Hydrolix MCP server?

Hydrolix mcp server lets Claude, Cursor and other MCP clients work with Hydrolix directly. Hydrolix time-series datalake integration providing schema exploration and query capabilities to LLM-based workflows.

What Hydrolix does

Get up and running in a few minutes. This section covers Claude Desktop and Claude Code.

Tools it exposes

Once connected, the assistant can call these 2 tools directly:

  • Input — sql (string): The SQL query to execute
  • Authentication — The server supports multiple authentication methods with the following precedence (highest to lowest):

Installing the hydrolix mcp server

The server is distributed via PyPI as args, so most clients can run it without a manual build step. Add it to your MCP client's configuration and restart the client to pick it up — the copy-paste configs for Claude Desktop, Claude Code and Cursor are on this page.

Configuration

Before the server will start you need to supply 5 environment variables: HYDROLIX_URL, HYDROLIX_USER, HYDROLIX_PASSWORD, HYDROLIX_TOKEN, HYDROLIX_HOST. Keep credentials in your client's env block or a secrets manager rather than committing them.

Where it fits

Database servers turn schema archaeology and ad-hoc reporting into conversation, which is why they tend to be the second or third server people install. Hydrolix sits in that group, and the shape of its toolset — Input, Authentication — tells you what it is really for. Worth comparing against the other databases servers in this directory before you commit to one, since several overlap in scope but differ sharply in setup cost and permissions.

Practical notes

  • This server runs locally, so it operates with whatever access your machine and its credentials already have. Scope that deliberately rather than by default.
  • It will not start until its required credentials are present, so set those before wondering why the tools never appear.
  • Written in Python.
  • MCP clients ask for confirmation before each tool call by default. Keep that on while you learn what the hydrolix mcp server actually does with your data.
  • Every entry in this directory is reviewed by hand before it goes live, and details are checked against the project's own documentation.

Available tools

ToolWhat it does
Inputsql (string): The SQL query to execute.
AuthenticationThe server supports multiple authentication methods with the following precedence (highest to lowest):

How to install the Hydrolix MCP server

{
  "mcpServers": {
    "mcp-hydrolix-remote": {
      "url": "https://my-hydrolix-mcp.example.com/mcp?token=<service-account-token>"
    }
  }
}

Configuration as documented by the project. Restart the client after saving.

Configuration

VariableDescriptionRequired
HYDROLIX_URLEndpoint or connection string the server talks to.Yes
HYDROLIX_USERConfiguration value read at startup.Optional
HYDROLIX_PASSWORDConfiguration value read at startup.Optional
HYDROLIX_TOKENCredential the server authenticates with.Yes
HYDROLIX_HOSTEndpoint or connection string the server talks to.Optional

Example prompts to try

  • Use Hydrolix to Input.
  • Use Hydrolix to Authentication.

Frequently asked questions

It connects Hydrolix to MCP-compatible AI assistants such as Claude and Cursor, exposing 2 tools (Input, Authentication) that the assistant can call on your behalf. Instead of copying data back and forth by hand, the assistant works with Hydrolix directly.