You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: README.md
+38-1Lines changed: 38 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -27,6 +27,18 @@ Due to the wide variety in LLM architectures, not all models will proactively us
27
27
* 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.
28
28
- This prompts the model to write more efficient queries that take advantage of [primary key optimizations](https://hydrolix.io/blog/optimizing-latest-n-row-queries/)
29
29
30
+
### Health Check Endpoint
31
+
32
+
When running with HTTP or SSE transport, a health check endpoint is available at `/health`. This endpoint:
33
+
- Returns `200 OK` with the ClickHouse version if the server is healthy and can connect to ClickHouse
34
+
- Returns `503 Service Unavailable` if the server cannot connect to ClickHouse
35
+
36
+
Example:
37
+
```bash
38
+
curl http://localhost:8000/health
39
+
# Response: OK - Connected to ClickHouse 24.3.1
40
+
```
41
+
30
42
## Configuration
31
43
32
44
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.
@@ -129,4 +141,29 @@ The following variables are used to configure the Hydrolix connection. These var
129
141
* Set this to automatically connect to a specific database
130
142
* `HYDROLIX_MCP_SERVER_TRANSPORT`: Sets the transport method for the MCP server.
131
143
* Default: `"stdio"`
132
-
* Valid options: `"stdio"`, `"http"`, `"streamable-http"`, `"sse"`. This is useful for local development with tools like MCP Inspector.
144
+
* Valid options: `"stdio"`, `"http"`, `"sse"`. This is useful for local development with tools like MCP Inspector.
145
+
* `HYDROLIX_MCP_BIND_HOST`: Host to bind the MCP server to when using HTTP or SSE transport
146
+
* Default: `"127.0.0.1"`
147
+
* Set to `"0.0.0.0"` to bind to all network interfaces (useful for Docker or remote access)
148
+
* Only used when transport is `"http"` or `"sse"`
149
+
* `HYDROLIX_MCP_BIND_PORT`: Port to bind the MCP server to when using HTTP or SSE transport
150
+
* Default: `"8000"`
151
+
* Only used when transport is `"http"` or `"sse"`
152
+
153
+
154
+
For MCP Inspector or remote access with HTTP transport:
155
+
156
+
```env
157
+
HYDROLIX_HOST=localhost
158
+
HYDROLIX_USER=default
159
+
HYDROLIX_PASSWORD=myPassword
160
+
HYDROLIX_MCP_SERVER_TRANSPORT=http
161
+
HYDROLIX_MCP_BIND_HOST=0.0.0.0 # Bind to all interfaces
162
+
HYDROLIX_MCP_BIND_PORT=4200 # Custom port (default: 8000)
163
+
```
164
+
165
+
When using HTTP transport, the server will run on the configured port (default 8000). For example, with the above configuration:
166
+
- MCP endpoint: `http://localhost:4200/mcp`
167
+
- Health check: `http://localhost:4200/health`
168
+
169
+
Note: The bind host and port settings are only used when transport is set to "http" or "sse".
0 commit comments