MCP C7ea2cfe

MCP数据服务

提供方 未标注

数据服务 stdio · 本地进程 OAuth 授权 社区 / 第三方

全面解析MCP HydrolixMCP Server的核心功能、安装配置和实用案例。作为顶级Model Context Protocol服务器,MCP Hydrolix能让AI助手访问实时数据、执行操作,为您提供更智能的工作体验和自动化解决方案。

一句话选型结论

按资料字段整理

MCP C7ea2cfe 属于数据服务类 MCP 服务器,stdio · 本地进程,OAuth 授权,没有现成安装命令,需按官方文档接入。接入前先确认权限范围;涉及写入、删除或付款的操作,建议先在测试环境验证。

分类数据服务 传输方式stdio · 本地进程 鉴权OAuth 授权 部署方式本地部署
GitHub 星标 未标注 仓库热度,无公开仓库时显示未标注
工具数 未标注 暴露给模型的工具数量
资源 / 提示词 0 / 0 资源与提示词模板数量
维护方 社区 / 第三方 核验等级 仅资料核对

工具与能力

数据服务
数量来自来源目录的标注,具体工具清单以官方文档为准
工具数量未标注暴露给模型可调用的工具个数
资源数量0可读取的资源条目
提示词数量0内置提示词模板数量

能力标签

安装与配置

stdio · 本地进程 OAuth 授权
客户端在本机拉起子进程,数据不出本机
  1. 1
    准备运行环境

    stdio 服务在本地起进程,需要先装好 Node.js 等运行时,再按安装命令拉取依赖。

  2. 2
    安装服务

    复制上面的安装命令执行;命令里带占位符的位置,换成自己的密钥或路径。

  3. 3
    写入客户端配置

    在客户端的 MCP 配置里填好启动命令和参数,保存后完全退出客户端再打开,让新配置生效。

  4. 4
    验证是否可用

    连接成功后随便调一个只读工具,确认能返回结果,再接入正式流程。

典型使用场景

3 类
按分类与标签整理的常见用法,具体以官方文档为准
数据库查询

用自然语言查库、取数,不用手写 SQL。

数据同步与清洗

把多来源数据拉到一处做整理。

报表取数

按口径快速拉出统计结果。

选择建议

选之前先看这几条
按条目字段给出的判断,不替你决定用不用

值得选的地方

  • 基础信息齐全,可以先按官方文档接入试跑。

先想清楚的地方

  • stdio 方式要求本地装好运行时(如 Node.js),换机器要重新装一遍。
  • 没有现成安装命令,需要按官方文档自己填启动命令和参数。
  • 使用前要准备好OAuth 授权对应的凭据,并按最小权限配置。
  • 资料没标注工具数量,实际能力要装好后确认。
  • 版本更新与行为细节以官方仓库为准。

更适合

  • 需要在数据服务场景里让模型直接调用外部能力的人。
  • 想先快速试一下、能接受在本地或自有环境跑服务的人。

不太适合

  • 完全不想在本地装环境的人。
  • 不方便管理密钥或第三方授权的人。
  • 需要厂商级 SLA 和技术支持的生产环境。

同类对比

6 个同类
同分类里挑最接近的几条,字段以各自详情页为准
MCP 服务器工具数传输方式部署方式安装命令最后核验
MCP C7ea2cfe当前 未标注 stdio · 本地进程 本地部署 无 2026-05-17
Memory 9d25f64e 9 未标注 未标注 无 2026-05-17
Getzep MCP 9 stdio · 本地进程 本地部署 有 2026-05-17
anything-llm 未标注 stdio · 本地进程 本地部署 有 2026-04-11
Prisma MCP Server 未标注 stdio · 本地进程 本地部署 有 2026-05-17
Astr Bot 未标注 stdio · 本地进程 本地部署 有 2026-05-17

服务器档案

数据服务
字段来自项目仓库与公开索引,中文说明由本站标注
提供方未标注上游标注的维护方 未标注
分类数据服务本站按上游分类展示
连接方式stdio · 本地进程客户端在本机拉起子进程,数据不出本机
鉴权方式OAuth 授权远程服务建议用最小权限凭据
维护方社区 / 第三方核验等级 仅资料核对
包名 / 运行时未标注 · 未标注本地安装时用到的包标识与运行时
部署类型本地部署上游给出的部署形态
最近核验2026-05-17上游最后核验时间

详细介绍

14.3 KB
来自项目仓库与上游目录的原文,未做删改

Hydrolix MCP Server

An MCP server for Hydrolix.

Quickstart

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

Step 1 — Prerequisites

Before you begin, make sure you have:

  • Hydrolix credentials — your cluster hostname plus either a username/password or a service account token. If you don't have these, ask your Hydrolix administrator.
  • Claude Desktop — download from claude.ai/download.

Step 2 — Install the MCP server

Choose the method that matches your setup:

Option A: Using uv (recommended)

uv manages Python automatically and downloads mcp-hydrolix on demand, so no separate install step is needed. If you don't have uv, install it:

macOS / Linux:```bash
curl -LsSf https://astral.sh/uv/install.sh | sh


Windows (PowerShell):```powershell
powershell -ExecutionPolicy ByPass -c "irm https://astral.sh/uv/install.ps1 | iex"

Option B: Using pip

Requires Python 3.13+. If you need to install Python, download it from python.org.```bash
pip install mcp-hydrolix


### Step 3 — Configure Claude Desktop

1. Open the Claude Desktop configuration file:
   - **macOS:** `~/Library/Application Support/Claude/claude_desktop_config.json`
   - **Windows:** `%APPDATA%\Claude\claude_desktop_config.json`
   - **Linux:** `~/.config/Claude/claude_desktop_config.json`

2. Add the following entry to the `"mcpServers"` object (create the file with this content if it doesn't exist yet):```json
{
  "mcpServers": {
    "mcp-hydrolix": {
      "command": "uvx",
      "args": [
        "--python",
        "3.13",
        "--refresh-package",
        "mcp-hydrolix",
        "mcp-hydrolix"
      ],
      "env": {
        "HYDROLIX_URL": "https://<your-hydrolix-hostname>",
        "HYDROLIX_USER": "<your-username>",
        "HYDROLIX_PASSWORD": "<your-password>"
      }
    }
  }
}

Replace ,, and `` with your actual credentials.

> [!NOTE]
> If you used Option B (pip), use "command": "mcp-hydrolix" with no "args" field instead.

> [!TIP]
> If the file already has other entries, add the "mcp-hydrolix" block inside the existing "mcpServers" object rather than replacing the whole file.

> [!NOTE]
> If you authenticate with a service account token instead of username/password, see Authentication.

Command not found?

Claude Desktop launches without your shell's PATH, so it may not locate the binary even if it is installed. Find the full path and use it as the "command" value in the config.

Option A (uv): find uvx:

  • macOS / Linux: which uvx
  • Windows: where.exe uvx

Option B (pip): find mcp-hydrolix:

  • macOS / Linux: which mcp-hydrolix
  • Windows: where.exe mcp-hydrolix

If which/where.exe returns nothing, the binary isn't on your PATH. The cleanest fix is to switch to Option A (uv), which manages the Python environment and PATH for you.

Step 4 — Restart Claude Desktop

Restart the app to apply the configuration.

> macOS / Windows users: Make sure to fully quit Claude before restarting. On macOS, press Cmd+Q or right-click the Dock icon and choose Quit. On Windows, use the system tray icon.

Step 5 — Verify it's working

  1. Open a new conversation in Claude Desktop. Look for a tools/hammer icon near the text input — this confirms the MCP server connected successfully.

  2. Try this prompt to confirm everything is working:

> Using your Hydrolix MCP tools, list the available databases.

Claude should call the list_databases tool and return a list of databases from your cluster.


Using Claude Code instead?

If you prefer the command line, make sure uv is installed (Option A from Step 2), then run:```bash
claude mcp add --transport stdio hydrolix \
--env HYDROLIX_URL=https://<your-hydrolix-hostname> \
--env HYDROLIX_USER=<your-username> \
--env HYDROLIX_PASSWORD=<your-password> \
--env HYDROLIX_MCP_SERVER_TRANSPORT=stdio \
-- uvx --python 3.13 --refresh-package mcp-hydrolix mcp-hydrolix


Then open Claude Code and test with the same prompt:

&gt; Using your Hydrolix MCP tools, list the available databases.

### Using VS Code instead?

Click the **Install in VS Code** badge at the top of this README for a one-click install. If you prefer the UI flow, open the Command Palette (**Cmd+Shift+P** / **Ctrl+Shift+P**), run **MCP: Add Server**, choose **Command (stdio)**, and reuse the `uvx ...` command and `env` block from Step 3.

## Tools

* `run_select_query`
  * Execute SQL queries on your Hydrolix cluster.
  * Input: `query` (string): The SQL query to execute.
  * Input: `max_cells` (integer, optional): Result cell budget (rows × columns); when the server sets a cap, a caller can only lower it.
  * Input: `purpose` (string, required): Why the query is being run; recorded with the query as `hdx_query_comment`.
  * A trailing `FORMAT` clause is removed; the server selects the wire format.

* `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.

## Effective Usage

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., &quot;Using MCP tools to access my Hydrolix database, please ...&quot;)
  - This encourages the model to use the MCP tools available and minimizes hallucinations.
* Include time ranges in your prompts (e.g., &quot;Between December 5 2023 and January 18 2024, ...&quot;) 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

### Health Check Endpoint

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&#x27;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:```bash
curl http://localhost:8000/health
# Response: OK - Connected to Hydrolix compatible with ClickHouse 24.3.1

Configuration

The Hydrolix MCP server is configured using a standard MCP server entry. Consult your client's documentation for specific instructions on where to find or declare MCP servers. An example setup using Claude Desktop is documented below.

The recommended way to launch the Hydrolix MCP server is via the uv project manager, which will manage installing all other dependencies in an isolated environment.

Authentication

The server supports multiple authentication methods with the following precedence (highest to lowest):

  1. Per-request Bearer token: Service account token provided via Authorization: Bearer header
  2. Per-request GET parameter: Service account token provided via ?token= query parameter
  3. Environment-based credentials: Credentials configured via environment variables
    - Service account token (HYDROLIX_TOKEN), or
    - Username and password (HYDROLIX_USER and HYDROLIX_PASSWORD)

When multiple authentication methods are configured, the server will use the first available method in the precedence order above. Per-request authentication is only available when using HTTP or SSE transport modes. The ?token= form exists for clients that cannot send headers; set HYDROLIX_ALLOW_TOKEN_QUERY_PARAM=false on deployments where every client sends the Authorization header (see Per-request credentials).

Note: Using a service account token with a readonly role is recommended.

MCP Server definition using username and password (JSON):```json
{
"command": "uvx",
"args": [
"--python",
"3.13",
"--refresh-package",
"mcp-hydrolix",
"mcp-hydrolix"
],
"env": {
"HYDROLIX_URL": "https://<hydrolix-host>",
"HYDROLIX_USER": "<hydrolix-user>",
"HYDROLIX_PASSWORD": "<hydrolix-password>"
}
}


MCP Server definition using service account token (JSON):```json
{
  &quot;command&quot;: &quot;uvx&quot;,
  &quot;args&quot;: [
    &quot;--python&quot;,
    &quot;3.13&quot;,
    &quot;--refresh-package&quot;,
    &quot;mcp-hydrolix&quot;,
    &quot;mcp-hydrolix&quot;
  ],
  &quot;env&quot;: {
    &quot;HYDROLIX_URL&quot;: &quot;https://&lt;hydrolix-host&gt;&quot;,
    &quot;HYDROLIX_TOKEN&quot;: &quot;&lt;hydrolix-service-account-token&gt;&quot;
  }
}

MCP Server definition using username and password (YAML):```yaml
command: uvx
args:
- --python
- "3.13"
- --refresh-package
- mcp-hydrolix
- mcp-hydrolix
env:
HYDROLIX_URL: https://<hydrolix-host>
HYDROLIX_USER: <hydrolix-user>
HYDROLIX_PASSWORD: <hydrolix-password>


MCP Server definition using service account token (YAML):```yaml
command: uvx
args:
- --python
- &quot;3.13&quot;
- --refresh-package
- mcp-hydrolix
- mcp-hydrolix
env:
  HYDROLIX_URL: https://&lt;hydrolix-host&gt;
  HYDROLIX_TOKEN: &lt;hydrolix-service-account-token&gt;

Configuration Example (Claude Desktop)

  1. Open the Claude Desktop configuration file located at:
    - On macOS: ~/Library/Application Support/Claude/claude_desktop_config.json
    - On Windows: %APPDATA%/Claude/claude_desktop_config.json

  2. Add a mcp-hydrolix server entry to the mcpServers config block to use username and password:```json
    {
    "mcpServers": {
    "mcp-hydrolix": {
    "command": "uvx",
    "args": [
    "--python",
    "3.13",
    "--refresh-package",
    "mcp-hydrolix",
    "mcp-hydrolix"
    ],
    "env": {
    "HYDROLIX_URL": "https://<hydrolix-host>",
    "HYDROLIX_USER": "<hydrolix-user>",
    "HYDROLIX_PASSWORD": "<hydrolix-password>"
    }
    }
    }
    }


To leverage service account use the following config block:```json
{
  &quot;mcpServers&quot;: {
    &quot;mcp-hydrolix&quot;: {
      &quot;command&quot;: &quot;uvx&quot;,
      &quot;args&quot;: [
        &quot;--python&quot;,
        &quot;3.13&quot;,
        &quot;--refresh-package&quot;,
        &quot;mcp-hydrolix&quot;,
        &quot;mcp-hydrolix&quot;
      ],
      &quot;env&quot;: {
        &quot;HYDROLIX_URL&quot;: &quot;https://&lt;hydrolix-host&gt;&quot;,
        &quot;HYDROLIX_TOKEN&quot;: &quot;&lt;hydrolix-service-account-token&gt;&quot;
      }
    }
  }
}
  1. Update the environment variable definitions to point to your Hydrolix cluster.

  2. (Recommended) Locate the command entry for uvx and replace it with the absolute path to the uvx executable. This ensures that the correct version of uvx is used when starting the server. You can find this path using which uvx or where.exe uvx.

  3. Restart Claude Desktop to apply the changes. If you are using Windows, ensure Claude is stopped completely by closing the client using the system tray icon.

Configuration Example (Claude Code)

To configure the Hydrolix MCP server for Claude Code, run the following command:```bash
claude mcp add --transport stdio hydrolix \
--env HYDROLIX_USER=<hydrolix-user> \
--env HYDROLIX_PASSWORD=<hydrolix-password> \
--env HYDROLIX_URL=https://<hydrolix-host> \
--env HYDROLIX_MCP_SERVER_TRANSPORT=stdio \
-- uvx --python 3.13 --refresh-package mcp-hydrolix mcp-hydrolix


### Environment Variables

The following variables are used to configure the Hydrolix connection. These variables may be provided via the MCP config block (as shown above), a `.env` file, or traditional environment variables.

#### Required Variables

You MUST set one of the following to identify the cluster:

* `HYDROLIX_URL` *(recommended)*: The canonical public URL of your Hydrolix cluster, e.g. `https://mycluster.hydrolix.live`. For typical out-of-cluster deployments this single variable is sufficient — it supplies the host, port (scheme-default 443/80), and TLS settings for both the HTTP query endpoint and the REST `/version` probe.
* `HYDROLIX_HOST` *(deprecated)*: The hostname of your Hydrolix server. Still honored for backwards compatibility but should be replaced by `HYDROLIX_URL`.

When `HYDROLIX_MCP_SERVER_TRANSPORT` is `http` or `sse`, `HYDROLIX_URL` *specifically* is required (a forthcoming OAuth metadata endpoint would advertise it). `HYDROLIX_HOST` alone is not sufficient for these transports.

#### Authentication Variables
At least one authentication method must be configured when using the stdio transport:

* `HYDROLIX_TOKEN`: Service account token for environment-based authentication
* `HYDROLIX_USER` and `HYDROLIX_PASSWORD`: Username and password for environment-based authentication (both must be provided together)

In summary:
- For stdio, you MUST use HYDROLIX_TOKEN or HYDROLIX_USER+HYDROLIX_PASS (environmental credentials)
- For http/sse, you MAY use HYDROLIX_TOKEN or HYDROLIX_USER+HYDROLIX_PASS (environmental credentials), but you may instead use per-request credentials.

If no credentials are provided via the environment or the request, the request will fail.

#### Using Per-Request Authentication with HTTP Transport

When using HTTP or SSE transport, you can omit environment-based credentials and instead provide authentication per-request. This is useful for multi-user scenarios or with clients that don&#x27;t support running MCP servers locally.

Example `mcpServers` configuration connecting to a remote HTTP server with per-request authentication:```json
{
  &quot;mcpServers&quot;: {
    &quot;mcp-hydrolix-remote&quot;: {
      &quot;url&quot;: &quot;https://my-hydrolix-mcp.example.com/mcp?token=&lt;service-account-token&gt;&quot;
    }
  }
}

Example minimal .env configuration for running your own HTTP server without environment credentials:env HYDROLIX_URL=https://my-cluster.hydrolix.net HYDROLIX_MCP_SERVER_TRANSPORT=http

Though not part of the MCP specification, many MCP clients allow adding headers to MCP-issued requests. When this is possible, we recommend configuring the MCP client to pass a service account token via the Authorization: Bearer header instead of as a query parameter for greater security.

Note: The bind host and port settings are only used when transport is set to "http" or "sse".

Optional Variables

See docs/CONFIG.md for endpoint overrides, deprecated variable aliases, and the full set of optional tuning variables (timeouts, query SETTINGS overrides, result truncation, HTTP/SSE worker tuning, proxy, metrics, and escape hatches).

Maintainers

Tasks that need operational privileges — running the end-to-end suite against a
live Hydrolix cluster, and cutting a release — are documented separately in
MAINTAINERS.md.

常见问题

7 问
答案由本站依据条目字段整理,不引用上游原文
MCP C7ea2cfe 怎么安装?

资料没有给出安装命令,请到官方仓库或文档按说明接入;这类条目多数是生态应用,或尚未发布可安装包。

MCP C7ea2cfe 怎么在客户端里配置?

它的传输方式未标注,在客户端 MCP 配置里按官方文档填写启动命令和参数,保存后重启客户端生效。

MCP C7ea2cfe 收费吗?

本站不代收费用,也没有标注具体价格。是否收费取决于服务本身和背后的接口额度,正式使用前按官方说明确认。

MCP C7ea2cfe 需要 API Key 吗?

资料标注需要OAuth 授权认证,使用前准备好对应凭据,并按最小权限配置。

MCP C7ea2cfe 能提供哪些能力?

资料显示能力标签包括 集群管理、数据分析、OAuth认证。具体工具清单以官方文档为准。

MCP C7ea2cfe 需要什么运行环境?

属于本地进程,需要在本机装好运行环境。

MCP C7ea2cfe 是本地还是远程?

它是本地进程(stdio),由客户端在本机拉起。传输方式为stdio · 本地进程。

热门专题

按标签挑服务器
全部专题 →

服务器信息以作者仓库与官方文档为准;分类、传输方式与鉴权方式的中文说明为中文整理,最近核验 2026-05-17。