This release adds 2 notable features for engineering teams evaluating rollout.
✓ No known CVEs patched in this version
Summary
AI summaryAdded TrafficPeak‑branded PyPI distribution with dual‑namespace environment variables and updated config documentation.
Full changelog
v0.3.5
Added
- mcp-trafficpeak: a second, fully TrafficPeak-branded PyPI distribution built from this single source tree, so TrafficPeak customers get an MCP server with no Hydrolix branding on customer-facing surfaces. Both brands ship from the same commit at the same version, selected at build time by
MCP_BRAND={hydrolix|trafficpeak}(defaulthydrolix). (#136, HDX-11476) - Dual-namespace environment variables: every
HYDROLIX_<x>setting can also be given asTRAFFICPEAK_<x>, resolved per-variable at read time with the TrafficPeak name taking precedence and silent fallback to the Hydrolix name. (#136, HDX-11476)
Changed
- Consolidated environment-variable documentation into
docs/CONFIG.md: documented previously-undocumented variables, moved less-common settings out of the README to improve its legibility, and fixed a staleHYDROLIX_MCP_WORKER_CONNECTIONSdefault (200 → 100) in the docs. (#134, HDX-11826)
Fixed
- Corrected the documented semantics of
HYDROLIX_QUERY_HEAD_POOL: the value names a query-head pool preconfigured on the cluster, and requests fail if the named pool does not exist. Earlier text wrongly framed it as a database-name routing key whose unmatched values were harmless. No behavior change. (#135, HDX-11826)
Full Changelog: https://github.com/hydrolix/mcp-hydrolix/compare/v0.3.4...v0.3.5
Weekly OSS security release digest.
The CVE patches and breaking changes that affected production tools this week. One email, every Sunday.
No spam, unsubscribe anytime.
Share this release
About hydrolix/mcp-hydrolix
Hydrolix time-series datalake integration providing schema exploration and query capabilities to LLM-based workflows.
Related context
Beta — feedback welcome: [email protected]