Skip to content
Back to search

hypequery

hypequery - The analytics layer for ClickHouse

Safety scan

A static text scan, not a guarantee. Select the badge to see what was scanned and every finding.

Checked today

Check it deeper on your machine

It has changed since its scan on 17 Nov 2026.

As a Claude Code plugin, install it and then ask Claude Code:

/plugin marketplace add keithmackay/mackayi/plugin install scanskillsafety@mackayiDo a deep scan of https://github.com/hypequery/hypequery with scanskillsafety

Or from a terminal, clone it and run it:

git clone https://github.com/keithmackay/scanskillsafety-skill ~/.claude/skills/scanskillsafetynode ~/.claude/skills/scanskillsafety/cli.cjs --deep 'https://github.com/hypequery/hypequery'

It checks the exact commit: every file, its packages against OSV (api.osv.dev), how it compares with this page's scan (findsafeskills.com receives the repository's address), and, if you agree, Claude reading every file with your own Claude subscription. It never runs the code.

Badge for your README
findsafeskills safety rating

Markdown

[![findsafeskills safety rating](/api/listings/hypequery--hypequery/badge.svg)](/listings/hypequery--hypequery)

HTML

<a href="/listings/hypequery--hypequery"><img src="/api/listings/hypequery--hypequery/badge.svg" alt="findsafeskills safety rating" /></a>

Install

i

What was scanned

The files the safety scan read, as written by the repository's author and shown as plain text. Lines with a finding are marked.

.claude-plugin/marketplace.json · Manifest · 16 lines
  1. {
  2. "name": "hypequery",
  3. "description": "hypequery's Claude Code plugins: agent skills for ClickHouse semantic layers and the hypequery app connector.",
  4. "owner": {
  5. "name": "hypequery",
  6. "url": "https://hypequery.com"
  7. },
  8. "plugins": [
  9. {
  10. "name": "hypequery",
  11. "source": "./plugins/claude-code/hypequery",
  12. "description": "Onboard ClickHouse onto hypequery and query hypequery Cloud datasets: three agent skills and the hypequery app's MCP connector.",
  13. "category": "data"
  14. }
  15. ]
  16. }
README.md · README · 151 lines
  1. <p align="center">
  2. <picture>
  3. <source media="(prefers-color-scheme: dark)" srcset="./website-next/public/logo-on-dark.png" />
  4. <img src="./website-next/public/logo.png" alt="hypequery, embedded analytics on ClickHouse" width="300" />
  5. </picture>
  6. </p>
  7. <p align="center"><strong>Embedded analytics on ClickHouse.</strong></p>
  8. Define your metrics once, in the codebase you already have. Dashboards, APIs, and AI agents all answer from that one definition. Run it in your own backend today. A hosted option, hypequery cloud, is coming soon.
  9. hypequery is an open-source embedded analytics toolkit for ClickHouse that runs inside your own application. You define datasets in TypeScript or Python (beta), with their dimensions, measures, metrics, and tenant rules, then query them by name and serve them as authenticated HTTP endpoints with OpenAPI, typed React hooks, and MCP tools for AI agents. The TypeScript SDK also includes a type-safe ClickHouse query builder. It is for engineers building dashboards, APIs, and agent tools on their own ClickHouse. hypequery is not a hosted BI tool, not a database, and not a separate semantic-layer server: it is a set of Apache 2.0 libraries you install and deploy with your backend.
  10. <p align="center">
  11. <a href="https://hypequery.com/docs/quick-start">TypeScript quick start</a> ·
  12. <a href="https://hypequery.com/docs/python">Python quick start</a> ·
  13. <a href="https://hypequery.com/docs/capabilities">Capabilities</a> ·
  14. <a href="https://github.com/hypequery/hypequery-examples">Examples</a> ·
  15. <a href="https://hypequery.com/clickhouse-mcp">MCP</a>
  16. </p>
  17. ## One definition, every surface
  18. ```ts
  19. import { dataset, dimension, measure } from '@hypequery/datasets';
  20. export const Orders = dataset('orders', {
  21. source: 'orders',
  22. tenantKey: 'tenant_id',
  23. timeKey: 'created_at',
  24. dimensions: {
  25. region: dimension.string(),
  26. status: dimension.string(),
  27. createdAt: dimension.timestamp({ column: 'created_at' }),
  28. },
  29. measures: {
  30. revenue: measure.sum('amount'),
  31. orderCount: measure.count('id'),
  32. p95OrderValue: measure.percentile('amount', 0.95),
  33. },
  34. });
  35. export const revenue = Orders.metric('revenue', {
  36. measure: 'revenue',
  37. });
  38. ```
  39. That dataset can run in a worker, become a validated HTTP endpoint, power a typed React dashboard, or appear as a bounded MCP tool. Tenant scope and metric meaning stay in one place.
  40. ## Start in minutes (TypeScript)
  41. ```bash
  42. npm install -D @hypequery/cli
  43. npx hypequery init
  44. npx hypequery dev
  45. ```
  46. Or add only the ClickHouse query builder:
  47. ```bash
  48. npm install @hypequery/clickhouse
  49. ```
  50. ```ts
  51. const revenueByRegion = await db
  52. .table('orders')
  53. .select(['region'])
  54. .where('status', 'eq', 'completed')
  55. .sum('amount', 'revenue')
  56. .groupBy('region')
  57. .orderBy('revenue', 'DESC')
  58. .execute();
  59. ```
  60. No hand-written result interface. No `any[]`. The result is inferred from your real schema and the query itself.
  61. ## Python (beta)
  62. The Python SDK implements the same datasets and Serve protocol, checked against the same conformance fixtures. Serve it from FastAPI, Django, Flask, or any ASGI or WSGI server.
  63. ```bash
  64. pip install "hypequery[clickhouse]==0.1.0b2"
  65. ```
  66. ```python
  67. from hypequery.datasets import Dataset, DatasetQuery, ExecutionContext, create_dataset_client, dimension, measure, tenant
  68. from hypequery.execution import ClickHouseConnection, create_clickhouse_executor
  69. orders = Dataset(
  70. name="orders",
  71. source="orders",
  72. tenant_key="tenant_id",
  73. dimensions={"country": dimension("string")},
  74. measures={"revenue": measure.sum("amount")},
  75. )
  76. analytics = create_dataset_client(executor=create_clickhouse_executor(ClickHouseConnection.from_env()))
  77. result = analytics.execute(
  78. orders,
  79. DatasetQuery(dimensions=("country",), measures=("revenue",)),
  80. context=ExecutionContext(tenant=tenant("org_123")),
  81. )
  82. ```
  83. See the [Python docs](https://hypequery.com/docs/python) and [`python/hypequery`](./python/hypequery).
  84. ## ClickHouse MCP server
  85. [`@hypequery/mcp`](./packages/mcp-server) is a governed ClickHouse MCP server for Claude Code, Cursor, Codex and other agents. Agents call `list_datasets`, `get_dataset_schema`, `query_metric` and `query_dataset` against the datasets and metrics you define; there is no raw SQL tool. To try it against the public ClickHouse playground in five minutes, install the packages, save the `mcp-config.mjs` from the [quickstart](https://hypequery.com/clickhouse-mcp#quickstart), and add the server to your agent:
  86. ```bash
  87. npm install @hypequery/mcp @hypequery/datasets @hypequery/clickhouse
  88. claude mcp add clickhouse -- npx -y @hypequery/mcp --config "$PWD/mcp-config.mjs"
  89. ```
  90. ## Built for product analytics
  91. - **ClickHouse-native:** generated types plus `FINAL`, `LIMIT BY`, percentiles, `argMax`, arrays, CTEs, streaming, and window expressions.
  92. - **Governed in code:** dimensions, measures, metrics, relationships, and time grains live beside your application.
  93. - **Multi-tenant by design:** runtime tenant scope fails closed instead of relying on every query author to remember a filter.
  94. - **Frontend ready:** typed TanStack Query hooks for named queries, metrics, and datasets.
  95. - **Agent ready:** MCP tools expose approved analytics, not unrestricted SQL.
  96. - **Two languages, one contract:** TypeScript and Python produce the same semantic and deployment artifacts.
  97. - **Easy to adopt:** start with one local query and add the semantic, HTTP, React, or MCP layers only when needed.
  98. ## Packages
  99. | Package | Job |
  100. | --- | --- |
  101. | [`@hypequery/clickhouse`](./packages/clickhouse) | Type-safe ClickHouse query builder |
  102. | [`@hypequery/datasets`](./packages/datasets) | TypeScript semantic layer |
  103. | [`@hypequery/serve`](./packages/serve) | Validated analytics APIs and OpenAPI |
  104. | [`@hypequery/react`](./packages/react) | Typed React hooks |
  105. | [`@hypequery/mcp`](./packages/mcp-server) | Governed ClickHouse MCP server |
  106. | [`@hypequery/cli`](./packages/cli) | Setup, generation, local docs, and deployment |
  107. | [`hypequery`](./python/hypequery) (PyPI) | Python datasets, execution, Serve, and CLI (beta) |
  108. ## Explore
  109. - [What hypequery supports today](https://hypequery.com/docs/capabilities)
  110. - [ClickHouse semantic layer](https://hypequery.com/clickhouse-semantic-layer)
  111. - [Multi-tenant analytics](https://hypequery.com/docs/datasets/multi-tenancy)
  112. - [React hooks](https://hypequery.com/docs/react/getting-started)
  113. - [MooseStack EOL comparison](https://hypequery.com/compare/hypequery-vs-moose)
  114. - [MooseStack migration guide](https://hypequery.com/blog/migrating-moosestack-to-hypequery)
  115. If hypequery saves you from another copied SQL string or drifting metric, a GitHub star helps the next team find it.
  116. ## License
  117. Apache-2.0. See [LICENSE](./LICENSE).

Ratings and comments

Sign in to rate this skill.

Sign in

Free to use. If it’s helped, pass it on.